mirror of https://github.com/k3s-io/k3s
16640d892f
Automatic merge from submit-queue (batch tested with PRs 47470, 47260, 47411, 46852, 46135) Write reports for each upgrade test Due to the way Ginkgo runs individual test cases and the level of coordination required for the upgrade tests, they were all run under a single Ginkgo test case. This PR generates and auxiliary report that break out the results of each upgrade test. This is accomplished by: 1) Wrapping `ginkgo.Fail` and `ginkgo.Skip` to get the actual failure or skip messages. 2) Recovering that info in the upgrade test to generate an auxiliary report. I suggest reviewing commit by commit. Sample report: https://storage.googleapis.com/krouseytestreports/logs/results/1/artifacts/junit_upgrades.xml Fixes: #47371 |
||
|---|---|---|
| .. | ||
| ginkgowrapper | ||
| BUILD | ||
| authorizer_util.go | ||
| cleanup.go | ||
| exec_util.go | ||
| federation_util.go | ||
| firewall_util.go | ||
| framework.go | ||
| get-kubemark-resource-usage.go | ||
| google_compute.go | ||
| ingress_utils.go | ||
| jobs_util.go | ||
| kubelet_stats.go | ||
| log_size_monitoring.go | ||
| metrics_util.go | ||
| networking_utils.go | ||
| nodes_util.go | ||
| perf_util.go | ||
| pods.go | ||
| pv_util.go | ||
| resource_usage_gatherer.go | ||
| service_util.go | ||
| size.go | ||
| statefulset_utils.go | ||
| test_context.go | ||
| upgrade_util.go | ||
| util.go | ||
| volume_util.go | ||