Skip to content

lag_test: Add check to verify that an initial LACP packet was received#9343

Merged
yxieca merged 1 commit intosonic-net:masterfrom
saiarcot895:hide-float-conversion-error
Aug 14, 2023
Merged

lag_test: Add check to verify that an initial LACP packet was received#9343
yxieca merged 1 commit intosonic-net:masterfrom
saiarcot895:hide-float-conversion-error

Conversation

@saiarcot895
Copy link
Contributor

Description of PR

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 201911
  • 202012
  • 202205

Approach

What is the motivation for this PR?

If, for some reason, the LAG session is down and there are no LACP PDU packets being sent back and forth, then the LacpTimingTest class will fail with a error about an invalid argument to float.

How did you do it?

In the LacpTimingTest class, when getting the initial LACP packet, first check to see that a packet was captured before trying to convert the timestamp value of the tuple to a float.

This doesn't necessarily prevent an error from being thrown, it just makes it a more graceful/expected failure.

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

In the LacpTimingTest class, when getting the initial LACP packet, first
check to see that a packet was captured before trying to convert the
timestamp value of the tuple to a float. Otherwise, there'll be an error
about an invalid argument to float.

This doesn't necessarily prevent an error from being thrown, it just
makes it a more graceful/expected failure.

Signed-off-by: Saikrishna Arcot <[email protected]>
@yxieca yxieca merged commit 85c362b into sonic-net:master Aug 14, 2023
@saiarcot895 saiarcot895 deleted the hide-float-conversion-error branch August 14, 2023 22:46
AharonMalkin pushed a commit to AharonMalkin/sonic-mgmt that referenced this pull request Jan 25, 2024
sonic-net#9343)

In the LacpTimingTest class, when getting the initial LACP packet, first
check to see that a packet was captured before trying to convert the
timestamp value of the tuple to a float. Otherwise, there'll be an error
about an invalid argument to float.

This doesn't necessarily prevent an error from being thrown, it just
makes it a more graceful/expected failure.

Signed-off-by: Saikrishna Arcot <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants