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

connectivity: Display last assertion error on failure #2608

Merged
merged 1 commit into from
Jun 20, 2024

Conversation

gandro
Copy link
Member

@gandro gandro commented Jun 19, 2024

When tests have metrics expectations and those expectations are never met, we fail the test. However, the reason for the failure is never displayed unless debug logging is enabled. This commit fixes that by displaying the last assertion error when the test is failed.

@gandro gandro added the area/CI Continuous Integration testing issue or flake label Jun 19, 2024
@gandro gandro requested a review from a team as a code owner June 19, 2024 08:13
@gandro gandro requested a review from christarazi June 19, 2024 08:13
When tests have metrics expectations and those expectations are never
met, we fail the test. However, the reason for the failure is never
displayed unless debug logging is enabled. This commit fixes that by
displaying the last assertion error when the test is failed.

Signed-off-by: Sebastian Wicki <[email protected]>
@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jun 20, 2024
@christarazi christarazi merged commit 64c7206 into main Jun 20, 2024
13 of 15 checks passed
@christarazi christarazi deleted the pr/gandro/display-metrics-error-on-timeout branch June 20, 2024 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI Continuous Integration testing issue or flake ready-to-merge This PR has passed all tests and received consensus from code owners to merge.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants