mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-08-09 12:07:47 +00:00
e2e: avoid redundant labels in JUnit file
Because labels are currently typically added also to the spec texts, we don't
need to write them separately.
This redundancy got introduced in f2cfbf44b1
when registering all inline tags
also as labels.
This commit is contained in:
parent
5ce0bd95cc
commit
617f2132fe
@ -36,6 +36,10 @@ func WriteJUnitReport(report ginkgo.Report, filename string) error {
|
|||||||
// both, then tools like kettle and spyglass would concatenate
|
// both, then tools like kettle and spyglass would concatenate
|
||||||
// the two strings and thus show duplicated information.
|
// the two strings and thus show duplicated information.
|
||||||
OmitFailureMessageAttr: true,
|
OmitFailureMessageAttr: true,
|
||||||
|
|
||||||
|
// All labels are also part of the spec texts in inline [] tags,
|
||||||
|
// so we don't need to write them separately.
|
||||||
|
OmitSpecLabels: true,
|
||||||
}
|
}
|
||||||
|
|
||||||
return reporters.GenerateJUnitReportWithConfig(report, filename, config)
|
return reporters.GenerateJUnitReportWithConfig(report, filename, config)
|
||||||
|
Loading…
Reference in New Issue
Block a user