This is an archive of the discontinued LLVM Phabricator instance.

[runtimes][ci] Run the tests for libunwind in the CI
ClosedPublic

Authored by ldionne on Sep 30 2021, 12:12 PM.

Details

Reviewers
ldionne
Group Reviewers
Restricted Project
Restricted Project
Commits
rG60fe1f59d08b: [runtimes][ci] Run the tests for libunwind in the CI
Summary

We should arguably have always been doing that. The state of libunwind
is quite sad, so this commit adds several XFAILs to make the CI pass.
We need to investigate why so many tests are not passing in some
configurations, but I'll defer that to folks who actually work on
libunwind for lack of bandwidth.

Diff Detail

Event Timeline

ldionne created this revision.Sep 30 2021, 12:12 PM
ldionne requested review of this revision.Sep 30 2021, 12:12 PM
Herald added a project: Restricted Project. · View Herald TranscriptSep 30 2021, 12:12 PM
Herald added a reviewer: Restricted Project. · View Herald Transcript
Herald added a reviewer: Restricted Project. · View Herald Transcript

Note that I suspect this won't work out-of-the-box cause the libunwind tests might be broken in a few ways (and that's why we haven't been running those tests from the start), however let's see what the CI tells us.

ldionne updated this revision to Diff 377294.Oct 5 2021, 10:35 AM

XFAIL a test on GCC

Herald added a project: Restricted Project. · View Herald TranscriptOct 5 2021, 10:35 AM
Herald added a reviewer: Restricted Project. · View Herald Transcript
danielkiss added inline comments.
libcxx/utils/ci/run-buildbot
92

Isn't -DLIBCXXABI_USE_LLVM_UNWINDER=Y needed also to use the in tree version of libunwind?

ldionne updated this revision to Diff 377355.Oct 5 2021, 2:24 PM
ldionne retitled this revision from [libc++][ci] Also run the tests for libunwind in the CI to [runtimes][ci] Run the tests for libunwind in the CI.
ldionne edited the summary of this revision. (Show Details)

Add a bunch of XFAILs. This is really bad, we have like 8 tests and more than half
of them are failing even in some common configurations. We'll need some serious
investigation.

jloser added a subscriber: jloser.Oct 5 2021, 2:40 PM

Add a bunch of XFAILs. This is really bad, we have like 8 tests and more than half
of them are failing even in some common configurations. We'll need some serious
investigation.

Yikes.

Add a bunch of XFAILs. This is really bad, we have like 8 tests and more than half
of them are failing even in some common configurations. We'll need some serious
investigation.

Yikes.

I am pretty sure that all the tests used to pass on macOS a couple years ago, but apparently a lot of changes have landed without proper CI and testing, so now they're red.

Pinging some people who have touched libunwind lately: @vitalybuka @MaskRay @danielkiss. I'm not sure who's closest to being a libunwind code owner, but it would be awesome if we could get a grip over the project. I'd do it, but libc++ and libc++abi are already borderline too much. I'll add this CI to avoid introducing new regressions, at least that's one step forward.

ldionne updated this revision to Diff 377388.Oct 5 2021, 4:50 PM

Rebase onto main (there were many concurrent changes in run-buildbot)

ldionne accepted this revision.Oct 6 2021, 8:24 AM
This revision was not accepted when it landed; it landed in state Needs Review.Oct 6 2021, 8:25 AM
This revision was automatically updated to reflect the committed changes.

@ldionne I'll take a look.