Patrick Ohly 3e2b26ce52 e2e: revise complete report creation ... The previous approach was based on the observation that some Prow jobs use the --report-dir parameter instead of the E2E_REPORT_DIR env variable. Parsing the command line was necessary to use the --json-report and --junit-report parameters. But that is complex and can be avoided by triggering the creation of complete reports in the E2E test suite. The paths are hard-coded and relative to the report directory to keep the code simple. There was a report that k8s-triage started processing more data after 6db4b741dd was merged. It's unclear whether that was because of the new <report-dir>/ginkgo_report.xml file. To avoid this potential problem, the reports are now in a "ginkgo" sub-directory. While at it, error checking gets enhanced: - Create directories at the start of the suite and bail out early if that fails. - *All* e2e suites using the framework do this, not just test/e2e. - Added missing error checking of truncated JUnit report writing.		2023-02-10 10:20:20 +01:00
..
junit.go