JUnitParser.validate() (ub_test_reports/junitparser.py:146, 39b73156) parses the shipped schemas/JUnit.xsd and validates the report against it — and nothing calls it: not the directives, not the converter, not the plugin. Found by #2009's mutation M6b: a wheel with the XSD deleted stayed green until two tests were added for the method itself. Those tests also measured that every XML fixture in the suite is invalid against the strict Ant schema (skips not allowed, timestamp/hostname required, properties expected) — pytest's, googletest's, ctest's output included — so wiring validate() into the parsing path would reject real reports.
Decide: either (a) delete validate() and the XSD (and the two tests, the junit_xsd constructor argument, the artefact fence's "must ship the XSD" line), or (b) keep it as an opt-in diagnostic with a lenient schema that matches what the parsers actually accept — in which case the schema is the contract and needs the fixtures as its corpus. (a) is smaller and honest about what ships today. Marco's call, since the XSD predates the monorepo; whichever it is, the changelog of the core's next release says so.
JUnitParser.validate()(ub_test_reports/junitparser.py:146,39b73156) parses the shippedschemas/JUnit.xsdand validates the report against it — and nothing calls it: not the directives, not the converter, not the plugin. Found by #2009's mutation M6b: a wheel with the XSD deleted stayed green until two tests were added for the method itself. Those tests also measured that every XML fixture in the suite is invalid against the strict Ant schema (skipsnot allowed,timestamp/hostnamerequired,propertiesexpected) — pytest's, googletest's, ctest's output included — so wiringvalidate()into the parsing path would reject real reports.Decide: either (a) delete
validate()and the XSD (and the two tests, thejunit_xsdconstructor argument, the artefact fence's "must ship the XSD" line), or (b) keep it as an opt-in diagnostic with a lenient schema that matches what the parsers actually accept — in which case the schema is the contract and needs the fixtures as its corpus. (a) is smaller and honest about what ships today. Marco's call, since the XSD predates the monorepo; whichever it is, the changelog of the core's next release says so.