You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am building LLVM + all the included projects on top of GCC in a non standard location.
The problem I am having is that in the execution of the test-suite, several tests related to libunwind and libc++ link to libatomic, but during the execution of the compiled test with run.py the environment is not carried over.
When running the test-suite on my WS where a version of libatomic is present also in a standard location this is not a problem (guess it could still be if the version i am compiling of top of is incompatible with the one i have by default on my system?).
If the system does not have libatomic in a standard location (eg the build node I am using for testing), the test-suite gives many false failures of the type
I've looked a little to see if there is some option to pass to LIT_ARGS to bypass this by allowing all or some environment variable to be carried over to the test execution, but I haven't found anything.
The only other solution would be to hack the run.py or the configuration file before running the test.
I was wondering while probably niche, if this should be supported by the test-suite (or if it already is and I've missed it)
The text was updated successfully, but these errors were encountered:
As a bit of extra info this is the number of tests failing due to this error in the various configs of the test suite (the second number is the number of failures_due_to_libatomic + successes)
Since it's very difficult to support arbitrary use cases, the test suite was designed to be easily extensible and configurable by creating your own "base" config. You can define your own configuration file like libcxx/test/configs/llvm-libc++-shared.cfg.in and provide the compiler + linker flags of your choice in it. You can then point the test suite to that config file by using LIBCXX_TEST_CONFIG (& similar for libc++abi/libunwind) at CMake configuration time.
Please reopen if that approach doesn't solve your problem!
I am building LLVM + all the included projects on top of GCC in a non standard location.
The problem I am having is that in the execution of the test-suite, several tests related to
libunwind
andlibc++
link tolibatomic
, but during the execution of the compiled test with run.py the environment is not carried over.When running the test-suite on my WS where a version of
libatomic
is present also in a standard location this is not a problem (guess it could still be if the version i am compiling of top of is incompatible with the one i have by default on my system?).If the system does not have
libatomic
in a standard location (eg the build node I am using for testing), the test-suite gives many false failures of the typeI've looked a little to see if there is some option to pass to
LIT_ARGS
to bypass this by allowing all or some environment variable to be carried over to the test execution, but I haven't found anything.The only other solution would be to hack the
run.py
or the configuration file before running the test.I was wondering while probably niche, if this should be supported by the test-suite (or if it already is and I've missed it)
The text was updated successfully, but these errors were encountered: