When LLVM is built under MSVC and libcxx ABI is set to 2, the 'copy_move.pass' test will unexpectedly pass. This patch mitigate this issue by setting this test will only expecting FAIL when libcxx ABI version is set to 1.
Details
- Reviewers
mstorsjo phosek ldionne - Group Reviewers
Restricted Project - Commits
- rG310255abef23: [libcxx] Fix copy_move.pass test
rGbe9f55f4fff4: [libcxx] Fix copy_move.pass test
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Tested under Windows with LIT_FILTER=.*func.wrap.func.con/copy_move.pass.cpp ninja check-runtimes-x86_64-pc-windows-msvc . The unexpected pass issue disappeared.
I reverted this change. As a matter of policy, please do not commit patches to libc++ unless the libc++ review group is green. The review process we follow is documented here: https://libcxx.llvm.org/Contributing.html#the-review-process -- it is a bit stricter than the usual LLVM review process because we have an automatically-added review group.
Furthermore, the change itself looked wrong, see my comment.
libcxx/test/std/utilities/function.objects/func.wrap/func.wrap.func/func.wrap.func.con/copy_move.pass.cpp | ||
---|---|---|
11 | libcxx-abi-version-1 is not a Lit feature that we ever populate. We do have libcpp-abi-version=<VERSION>, so this should probably be libcpp-abi-version=1. |
OK, I will pay attention next time.
I see why my patch works in the local test now.
That tag wasn't defined.
Just FWIW, it seems like the premerge CI never ran for this change. As long as all is well and it didn't trip anything up, this was fine, but ideally we should have fixed (setting the "repository" field to "rG" in the phabricator upload form, which gets set automatically when posting with arcanist) that and made sure the CI actually ran, before pushing it. It looks like the later scheduled runs on main are fine though.
I locally test it before I submit the change.
I noticed that the premerge bot unexpected timed out when checking out this change and I don't know how to kick it start again. So I just landed it and monitor the post submit bots.
We don't have post-submit bots in libc++. Please make sure to follow these instructions for contributing in the future: https://libcxx.llvm.org/Contributing.html. In particular, using arc diff to upload your patch is mandatory for libc++, since it will ensure that CI runs properly.
I locally test it before I submit the change.
We test 58 configurations in the CI. Local testing is not close to being enough for libc++.
libcxx-abi-version-1 is not a Lit feature that we ever populate. We do have libcpp-abi-version=<VERSION>, so this should probably be libcpp-abi-version=1.