Assert UpdatedAtNanos in neighbor entry tests

Browse Source

Changes the neighbor_entry_test.go tests to always assert UpdatedAtNanos.

This field was historically not checked due to the lack of a deterministic,
controllable clock. This is no longer true with the tcpip.Clock interface.
While the tests have been adjusted to use Clock, asserting by the
UpdatedAtNanos was neglected.

Subsequent work is needed to assert UpdatedAtNanos in the neighbor cache tests.

Updates #4663

PiperOrigin-RevId: 359868254

...

This commit is contained in:

Sam Balana

2021-02-26 17:09:55 -08:00

committed by gVisor bot

parent 85d5958669

commit af6e6d5e7f

1 changed files with 140 additions and 119 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

pkg/tcpip/stack/neighbor_entry_test.go

+140 -119

File diff suppressed because it is too large Load Diff