integration-tests: Fix nightly job failures #71
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With FreeRTOS/FreeRTOS-Plus-TCP@4471af6, a validation logic has been introduced which checks, if one of the address in an IP packet is loopback then both source and destination addresses must be loopback. For network interface tests, we run the server on the local machine and use loopback interface address in integration tests to communicate with the server. This causes validation logic to fail, as the destination address in the IP in the packet returned by the server is not a loopback address, but instead address assigned to the device. As a workaround, we use the ethernet interface address of the host machine instead of loopback to communicate with the server. In addition, add a job retry logic to nightly build jobs so that, jobs gets restarted for known failures. Signed-off-by: Devaraj Ranganna <[email protected]>
amazonKamath
approved these changes
May 7, 2024
aggarg
approved these changes
May 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
With FreeRTOS/FreeRTOS-Plus-TCP@4471af6, a validation logic has been introduced which checks, if one of the address in an IP packet is loopback then both source and destination addresses must be loopback. For network interface tests, we run the server on the local machine and use loopback interface address in integration tests to communicate with the server. This causes validation logic to fail, as the destination address in the IP in the packet returned by the server is not a loopback address, but instead address assigned to the device. As a workaround, we use the ethernet interface address of the host machine instead of loopback to communicate with the server.
In addition, add a job retry logic to nightly build jobs so that, jobs gets restarted for known failures.
Test Steps
Changes validated in the CI, no regressions observed.
Checklist:
Related Issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.