[llvm-branch-commits] [CI] Setup generate_report to describe ninja failures (PR #152621)
Aiden Grossman via llvm-branch-commits
llvm-branch-commits at lists.llvm.org
Fri Aug 8 06:47:53 PDT 2025
================
@@ -246,6 +288,58 @@ def test_no_failures_build_failed(self):
),
)
+ def test_no_failures_build_failed_ninja_log(self):
+ self.assertEqual(
+ generate_test_report_lib.generate_report(
+ "Foo",
+ 1,
+ [
+ junit_from_xml(
+ dedent(
+ """\
+ <?xml version="1.0" encoding="UTF-8"?>
+ <testsuites time="0.00">
+ <testsuite name="Passed" tests="1" failures="0" skipped="0" time="0.00">
+ <testcase classname="Bar/test_1" name="test_1" time="0.00"/>
+ </testsuite>
+ </testsuites>"""
+ )
+ )
+ ],
+ [
+ [
+ "[1/5] test/1.stamp",
+ "[2/5] test/2.stamp",
+ "[3/5] test/3.stamp",
+ "[4/5] test/4.stamp",
+ "FAILED: test/4.stamp",
+ "touch test/4.stamp",
+ "Wow! Close To You!",
+ "[5/5] test/5.stamp",
+ ]
+ ],
+ ),
+ (
+ dedent(
+ """\
+ # Foo
+
+ * 1 test passed
----------------
boomanaiden154 wrote:
We can't trivially just report build failures along with test failures because the `check-*` targets will show up as build failures given they are run through ninja. We should be able to detect that and filter them out, but I think it's reasonable to leave them out of scope for now.
https://github.com/llvm/llvm-project/pull/152621
More information about the llvm-branch-commits
mailing list