connectivity: Include detailed failure messages in test report #39866
Conversation
This file contains hidden or 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
|
/test |
9dffe27 to
7d9c7e0
Compare
|
/test |
7d9c7e0 to
27a2961
Compare
|
/test |
41b4de2 to
2a8990c
Compare
Include the reason why a test action failed (e.g., "Pod flow was interrupted") in the final connectivity test report. This makes it easier to diagnose test failures by showing error messages like "flow was interrupted (restart count does not match 0 != 1)" directly in the report summary, rather than requiring users to search through detailed test logs. Signed-off-by: André Martins <andre@cilium.io>
2a8990c to
e6e6bf5
Compare
|
/test |
sayboras
approved these changes
Jun 3, 2025
viktor-kurchenko
approved these changes
Jun 4, 2025
8 tasks
8 tasks
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.
Include the reason why a test action failed (e.g., "Pod flow was interrupted") in the final connectivity test report. This makes it easier to diagnose test failures by showing error messages like "flow was interrupted (restart count does not match 0 != 1)" directly in the report summary, rather than requiring users to search through detailed test logs.
Example: https://github.com/cilium/cilium/actions/runs/15419346198/job/43390381268
Before
After
