diff options
| author | Kendal Harland <3987220+kendalharland@users.noreply.github.com> | 2024-08-16 10:54:25 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-16 10:54:25 -0700 |
| commit | 9f89d31d5185015f8eea9c0f3d35e7ba9d353e67 (patch) | |
| tree | 8777dfa6ea395beb553b9d7d659213106ec937ce /llvm/lib/Object/MachOObjectFile.cpp | |
| parent | b81697718f49b0f353882e178f25981f47b2aa43 (diff) | |
| download | llvm-9f89d31d5185015f8eea9c0f3d35e7ba9d353e67.zip llvm-9f89d31d5185015f8eea9c0f3d35e7ba9d353e67.tar.gz llvm-9f89d31d5185015f8eea9c0f3d35e7ba9d353e67.tar.bz2 | |
[lldb][test] Mark gtest cases as XFAIL if the test suite is XFAIL (#102986)
When a test case inside of a gtest suite fails, we report a failure
which causes the entire `ninja check-lldb` invocation to fail, even if
the outer test case is marked as XFAIL - each test case result is
reported as its own lit test run. This PR updates lit so it checks
whether each test case's parent test suite is XFAIL before setting the
status to FAIL.
This is especially problematic because the failing tests can't manually
be marked as XFAIL, due to
https://github.com/llvm/llvm-project/issues/102264.
Fixes https://github.com/llvm/llvm-project/issues/102265
### Repro instructions
1. Modify any gtest test case to generate a failure.
2. Mark the outer lit test with XFAIL using either `--xfail-tests` flag
or `LIT_XFAIL` env var.
3. Run the tests
4. Observe the lit test is XFAIL as expected, but the failed child test
cases show up as separate failures.
Co-authored-by: kendal <kendal@thebrowser.company>
Diffstat (limited to 'llvm/lib/Object/MachOObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions