|
Revision tags: llvmorg-18.1.8, llvmorg-18.1.7, llvmorg-18.1.6, llvmorg-18.1.5, llvmorg-18.1.4, llvmorg-18.1.3, llvmorg-18.1.2, llvmorg-18.1.1, llvmorg-18.1.0, llvmorg-18.1.0-rc4, llvmorg-18.1.0-rc3, llvmorg-18.1.0-rc2, llvmorg-18.1.0-rc1, llvmorg-19-init |
|
| #
be811d16 |
| 29-Nov-2023 |
Michael Platings <michael.platings@arm.com> |
[libc++] Run picolibc tests with qemu
This patch actually runs the tests for picolibc behind an emulator, removing a few workarounds and increasing coverage.
Differential Revision: https://reviews.
[libc++] Run picolibc tests with qemu
This patch actually runs the tests for picolibc behind an emulator, removing a few workarounds and increasing coverage.
Differential Revision: https://reviews.llvm.org/D155521
show more ...
|
| #
8aeacebf |
| 29-Nov-2023 |
Michael Platings <michael.platings@arm.com> |
[libc++] Add initial support for picolibc
Picolibc is a C Standard Library that is commonly used in embedded environments. This patch adds initial support for this configuration along with pre-commi
[libc++] Add initial support for picolibc
Picolibc is a C Standard Library that is commonly used in embedded environments. This patch adds initial support for this configuration along with pre-commit CI. As of this patch, the test suite only builds the tests and nothing is run. A follow-up patch will make the test suite actually run the tests.
Differential Revision: https://reviews.llvm.org/D154246
show more ...
|
|
Revision tags: llvmorg-17.0.6, llvmorg-17.0.5, llvmorg-17.0.4, llvmorg-17.0.3, llvmorg-17.0.2 |
|
| #
257eb745 |
| 20-Sep-2023 |
Louis Dionne <ldionne.2@gmail.com> |
[libc++] Simplify how the global stream tests are written (#66842)
Instead of relying on Bash, use the builtin Lit commands whenever
possible. The motivation is to stop running %t.exe behind Bash,
[libc++] Simplify how the global stream tests are written (#66842)
Instead of relying on Bash, use the builtin Lit commands whenever
possible. The motivation is to stop running %t.exe behind Bash, which
breaks on macOS 13.5 with SIP enabled because DYLD_LIBRARY_PATH isn't
forwarded to the underlying process when running through a protected
process.
For more details, see [1].
[1]: https://developer.apple.com/library/archive/documentation/Security/Conceptual/System_Integrity_Protection_Guide/RuntimeProtections/RuntimeProtections.html
show more ...
|
|
Revision tags: llvmorg-17.0.1, llvmorg-17.0.0, llvmorg-17.0.0-rc4, llvmorg-17.0.0-rc3, llvmorg-17.0.0-rc2, llvmorg-17.0.0-rc1, llvmorg-18-init |
|
| #
f9bd4597 |
| 20-Jul-2023 |
Louis Dionne <ldionne.2@gmail.com> |
[libc++][NFC] Fix synopsis comments in cout tests
|
|
Revision tags: llvmorg-16.0.6, llvmorg-16.0.5, llvmorg-16.0.4, llvmorg-16.0.3, llvmorg-16.0.2, llvmorg-16.0.1, llvmorg-16.0.0, llvmorg-16.0.0-rc4, llvmorg-16.0.0-rc3, llvmorg-16.0.0-rc2, llvmorg-16.0.0-rc1, llvmorg-17-init, llvmorg-15.0.7, llvmorg-15.0.6, llvmorg-15.0.5, llvmorg-15.0.4, llvmorg-15.0.3, working, llvmorg-15.0.2, llvmorg-15.0.1, llvmorg-15.0.0, llvmorg-15.0.0-rc3, llvmorg-15.0.0-rc2, llvmorg-15.0.0-rc1, llvmorg-16-init, llvmorg-14.0.6, llvmorg-14.0.5, llvmorg-14.0.4, llvmorg-14.0.3, llvmorg-14.0.2, llvmorg-14.0.1, llvmorg-14.0.0, llvmorg-14.0.0-rc4, llvmorg-14.0.0-rc3, llvmorg-14.0.0-rc2, llvmorg-14.0.0-rc1, llvmorg-15-init, llvmorg-13.0.1, llvmorg-13.0.1-rc3, llvmorg-13.0.1-rc2 |
|
| #
d67b25e7 |
| 21-Dec-2021 |
Martin Storsjö <martin@martin.st> |
[libcxx] [test] Extend test for bash for executor-has-no-bash
If %{exec} sets "--env PATH=single-dir", the directory containing bash and related shell utils is omitted from the path, which means tha
[libcxx] [test] Extend test for bash for executor-has-no-bash
If %{exec} sets "--env PATH=single-dir", the directory containing bash and related shell utils is omitted from the path, which means that most shell scripts would fail.
(Setting PATH is needed for DLL builds on Windows; PATH fills the same role as e.g. LD_LIBRARY_PATH on Linux.)
This condition is missed in the current test, because the executor run.py first resolves the executable to run using the original path, then invokes that executable with an environment with a restricted path. Thus the executor is able to run bash, but that bash is then unable to run further shell commands (other than bash builtins).
Extend the test from "bash --version" to "bash -c 'bash --version'". This correctly identifies the executor-has-no-bash condition in the current Windows CI configs, allowing removing 6 cases of LIBCXX-WINDOWS-FIXME.
Another longterm fix would be to extend run.py with an option like "--env-prepend PATH=dir", to allow keeping the current path while adding a directory to it.
Differential Revision: https://reviews.llvm.org/D116117
show more ...
|
|
Revision tags: llvmorg-13.0.1-rc1, llvmorg-13.0.0, llvmorg-13.0.0-rc4, llvmorg-13.0.0-rc3, llvmorg-13.0.0-rc2, llvmorg-13.0.0-rc1, llvmorg-14-init, llvmorg-12.0.1, llvmorg-12.0.1-rc4, llvmorg-12.0.1-rc3, llvmorg-12.0.1-rc2, llvmorg-12.0.1-rc1, llvmorg-12.0.0, llvmorg-12.0.0-rc5, llvmorg-12.0.0-rc4, llvmorg-12.0.0-rc3, llvmorg-12.0.0-rc2, llvmorg-11.1.0, llvmorg-11.1.0-rc3, llvmorg-12.0.0-rc1, llvmorg-13-init, llvmorg-11.1.0-rc2, llvmorg-11.1.0-rc1, llvmorg-11.0.1, llvmorg-11.0.1-rc2, llvmorg-11.0.1-rc1 |
|
| #
87fe0709 |
| 03-Nov-2020 |
Louis Dionne <ldionne@apple.com> |
[libc++] Allow detecting whether the executor supports Bash
A few tests in the test suite require support for Bash. For example, tests that run a program and send data through stdin to it require so
[libc++] Allow detecting whether the executor supports Bash
A few tests in the test suite require support for Bash. For example, tests that run a program and send data through stdin to it require some way of piping the data in, and we use a Bash script for that.
However, some executors (e.g. an embedded systems simulator) do not support Bash, so these tests will fail. This commit adds a Lit feature that tries to detect whether Bash is available through conventional means, and disables the tests that require it otherwise.
Differential Revision: https://reviews.llvm.org/D114612
show more ...
|
| #
87dd5198 |
| 24-Aug-2021 |
Louis Dionne <ldionne.2@gmail.com> |
[libc++] Remove support for CloudABI, which has been abandoned
Based on https://github.com/NuxiNL/cloudlibc, it appears that the CloudABI project has been abandoned. This patch removes a bunch of Cl
[libc++] Remove support for CloudABI, which has been abandoned
Based on https://github.com/NuxiNL/cloudlibc, it appears that the CloudABI project has been abandoned. This patch removes a bunch of CloudABI specific logic that had been added to support that platform.
Note that some knobs like LIBCXX_ENABLE_STDIN and LIBCXX_ENABLE_STDOUT coud be useful in their own right, however those are currently broken. If we want to re-add such knobs in the future, we can do it like we've done it for localization & friends so that we can officially support that configuration.
Differential Revision: https://reviews.llvm.org/D108637
show more ...
|
| #
4f7fa06a |
| 20-Mar-2021 |
Martin Storsjö <martin@martin.st> |
[libcxx] [test] Add XFAIL LIBCXX-WINDOWS-FIXME in 124 tests that fail in the future CI configuration
This makes no attempt yet to look into the why/what for each of them, but makes the CI configurat
[libcxx] [test] Add XFAIL LIBCXX-WINDOWS-FIXME in 124 tests that fail in the future CI configuration
This makes no attempt yet to look into the why/what for each of them, but makes the CI configuration useful for tracking further regressions. After looking into each case, they can either be fixed, or converted into UNSUPPORTED: windows or XFAIL: windows, once the cause is known and explained.
A number of the filesystem cases can be fixed by patches that are currently in review.
Differential Revision: https://reviews.llvm.org/D99095
show more ...
|
| #
8e5156f6 |
| 03-Nov-2020 |
Louis Dionne <ldionne@apple.com> |
[libc++] Harden tests against executors not running tests in a shell
Some executors do not run the tests in a shell, and so assuming that they can understand shell builtins is wrong. Instead, call B
[libc++] Harden tests against executors not running tests in a shell
Some executors do not run the tests in a shell, and so assuming that they can understand shell builtins is wrong. Instead, call Bash directly to do what we need to do.
This still requires the executor to be able to run Bash, but at least it does not require it to interpret command lines in the Bash language.
show more ...
|
|
Revision tags: llvmorg-11.0.0, llvmorg-11.0.0-rc6, llvmorg-11.0.0-rc5, llvmorg-11.0.0-rc4, llvmorg-11.0.0-rc3, llvmorg-11.0.0-rc2, llvmorg-11.0.0-rc1, llvmorg-12-init, llvmorg-10.0.1, llvmorg-10.0.1-rc4, llvmorg-10.0.1-rc3, llvmorg-10.0.1-rc2 |
|
| #
1fc5010d |
| 10-Jun-2020 |
Louis Dionne <ldionne@apple.com> |
[libc++] Consider everything inside %T to be a dependency of each test
Instead of passing file dependencies individually, assume that the whole content of the unique test directory is a dependency.
[libc++] Consider everything inside %T to be a dependency of each test
Instead of passing file dependencies individually, assume that the whole content of the unique test directory is a dependency. This simplifies the test harness significantly, by making %T the directory that contains everything required to run a test. This also removes the need for the %{file_dependencies} substitution, which is removed by this patch.
Furthermore, this patch also changes the harness to execute tests locally inside %T, so as to avoid creating a separate directory for no purpose.
show more ...
|
|
Revision tags: llvmorg-10.0.1-rc1 |
|
| #
50cd964e |
| 05-May-2020 |
Louis Dionne <ldionne@apple.com> |
[libc++] Rewrite the tests for cin, cout, clog, cerr and friends
The tests were disabled with `#if 0`, most likely because there was no way of writing shell tests when they were first written.
|