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

Move the k8sreporter dump into FailHandler and make dir for the reports #377

Merged
merged 2 commits into from
Sep 14, 2023

Conversation

liornoy
Copy link
Contributor

@liornoy liornoy commented Aug 24, 2023

This commit moves the reporter.Dump() call into the FailHandler. We do this because previously, having the reporter dump in the ReportAfterEach, we didn't get the desired logs because the test namesapce would be cleaned beforehand in the AfterEach/ AfterAll phase.

Also, made the reporter to create a directory named "metallb_failure_report.log" to house all the failed tests from all of the test suites.

@liornoy liornoy force-pushed the change-k8sreporter branch 5 times, most recently from 23b37cd to 97ebb14 Compare September 3, 2023 13:46
@liornoy liornoy changed the title Move the k8sreporter dump into FailHandler Move the k8sreporter dump into FailHandler and make dir for the reports Sep 4, 2023
This commit moves the reporter.Dump() call into the FailHandler.
We do this because previously, having the reporter dump in the
ReportAfterEach, we didn't get the desired logs because
the test namesapce would be cleaned beforehand in the AfterEach/
AfterAll phase. Also wee modify the skipCaller to point to the correct
line.

Signed-off-by: Lior Noy <[email protected]>
This commit makes the k8s reporter to create a dir named
"metallb_failure_report.log" to place all the failed tests in it.

We ignore the error of dir already exist to allow it to
use the same dir for the validation and funcaitonal test suites.

Signed-off-by: Lior Noy <[email protected]>
@fedepaol fedepaol merged commit 338dfa6 into metallb:main Sep 14, 2023
8 checks passed
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