Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests: Fix frequent ospfv3 basic functionality test failure #16657

Merged
merged 1 commit into from
Aug 27, 2024

Conversation

Jafaral
Copy link
Member

@Jafaral Jafaral commented Aug 26, 2024

The dead timer is set to 4 seconds, while the hello interval is set to 6535. This test will only pass if the platform is fast enough for ospfv3 to converge in 4 seconds. These timers were already tested multiple time earlier. This test should just make sure that the boundary value 65535 is configurable,

Other changes in this commit:

  • add sequence numbers to the dead intervals tests to make it easier to track test faliures.
  • swap the config order in one test to match order with all other tests.

@frrbot frrbot bot added the tests Topotests, make check, etc label Aug 26, 2024
Copy link
Collaborator

@aceelindem aceelindem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't you also change "test_ospfv3_hello_tc10_p0()" to have a larger dead-interval when the hello-interval is set to 65535?

@Jafaral
Copy link
Member Author

Jafaral commented Aug 26, 2024

Shouldn't you also change "test_ospfv3_hello_tc10_p0()" to have a larger dead-interval when the hello-interval is set to 65535?

Only if we care about neighbors. However, in that case we only need to make sure we can configure the value 65535, and the following test makes sure we can't configure 65536.

@aceelindem
Copy link
Collaborator

Shouldn't you also change "test_ospfv3_hello_tc10_p0()" to have a larger dead-interval when the hello-interval is set to 65535?

Only if we care about neighbors. However, in that case we only need to make sure we can configure the value 65535, and the following test makes sure we can't configure 65536.

Ok - I guess the test is only for successful configuration.

The dead timer is set to 4 seconds, while the hello interval is set to 6535.
This test will only pass of the platform is fast enough for ospfv3 to
converge in 4 seconds. These timers were already tested multiple time earlier.
This test should just make sure that the boundary value 65535 is configurable,

Other changes in this commit:
  - add sequence numbers to the dead intervals tests to make it easier to
    track test faliures.
  - swap the config order in one test to match order with all other tests.

Signed-off-by: Jafar Al-Gharaibeh <jafar@atcorp.com>
@Jafaral
Copy link
Member Author

Jafaral commented Aug 26, 2024

forced push style issues.

@donaldsharp donaldsharp merged commit 52f292d into FRRouting:master Aug 27, 2024
11 checks passed
Jafaral added a commit to Jafaral/frr that referenced this pull request Aug 27, 2024
Jafaral added a commit to Jafaral/frr that referenced this pull request Aug 27, 2024
Signed-off-by: Jafar Al-Gharaibeh <jafar@atcorp.com>
Jafaral added a commit to Jafaral/frr that referenced this pull request Aug 27, 2024
Signed-off-by: Jafar Al-Gharaibeh <jafar@atcorp.com>
riw777 added a commit that referenced this pull request Aug 27, 2024
tests: Fix ospfv3 basic functionality test (backport #16657)
riw777 added a commit that referenced this pull request Aug 27, 2024
tests: Fix ospfv3 basic functionality test (backport #16657)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
master size/M tests Topotests, make check, etc
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants