maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/libcxx/utils/ci/run-buildbot

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

577 lines
21 KiB
Plaintext
Raw Normal View History

[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
#!/usr/bin/env bash
#===----------------------------------------------------------------------===##
#
# Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
# See https://llvm.org/LICENSE.txt for license information.
# SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
#
#===----------------------------------------------------------------------===##
set -ex
[libc++] Add format check to CI Note: contrary to what I said previously, I didn't change .clang-format nor utils/generate_feature_test_macro_components.py script. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D92229
2021-02-05 04:13:22 +08:00
set -o pipefail
[libc++] [test] Recommit the unsetting of LC_COLLATE in the builder script. This re-reverts one piece of 1b885573327d0f6b36f24ad23d243642f658750b, reapplying one piece of D101437 (but not the "service"-queue piece of it). It turns out that the behavior of `grep [^ -~]`, or even `grep [A-Z]`, depends on locale, specifically `LC_COLLATE`. So we want to make sure we're not in any weird locale, no matter what machine we're running on. Yes, "en_US.UTF-8" counts as weird! https://stackoverflow.com/questions/67320156/misbehavior-of-gnu-grep-when-grepping-for-ignores-spaces https://stackoverflow.com/questions/6799872/how-to-make-grep-a-z-independent-of-locale
2021-05-01 02:43:33 +08:00
unset LANG
unset LC_ALL
unset LC_COLLATE
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
PROGNAME="$(basename "${0}")"
function usage() {
cat <<EOF
Usage:
${PROGNAME} [options] <BUILDER>
[-h|--help] Display this help and exit.
--llvm-root <DIR> Path to the root of the LLVM monorepo. By default, we try
to figure it out based on the current working directory.
[libc++] Also allow customizing the build directory when running CI
2020-11-06 08:09:03 +08:00
--build-dir <DIR> The directory to use for building the library. By default,
this is '<llvm-root>/build/<builder>'.
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
--osx-roots <DIR> Path to pre-downloaded macOS dylibs. By default, we download
them from Green Dragon. This is only relevant at all when
running back-deployment testing if one wants to override
the old dylibs we use to run the tests with different ones.
EOF
}
while [[ $# -gt 0 ]]; do
case ${1} in
-h|--help)
usage
exit 0
;;
--llvm-root)
MONOREPO_ROOT="${2}"
shift; shift
;;
[libc++] Also allow customizing the build directory when running CI
2020-11-06 08:09:03 +08:00
--build-dir)
BUILD_DIR="${2}"
shift; shift
;;
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
--osx-roots)
OSX_ROOTS="${2}"
shift; shift
;;
*)
BUILDER="${1}"
shift
;;
esac
done
MONOREPO_ROOT="${MONOREPO_ROOT:="$(git rev-parse --show-toplevel)"}"
[libc++] Also allow customizing the build directory when running CI
2020-11-06 08:09:03 +08:00
BUILD_DIR="${BUILD_DIR:=${MONOREPO_ROOT}/build/${BUILDER}}"
[libc++] Fix typo in run-buildbot The installation directory was never meant to contain a brace.
2021-01-08 06:37:09 +08:00
INSTALL_DIR="${BUILD_DIR}/install"
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
[libc++] Use Xcode's CMake if it's present This resolves issues when the CMake in use on the host is too old to configure libc++ properly, but Xcode has a sufficiently recent version. It is technically possible for the reverse issue to happen, where the Xcode version would be too old and the user-installed version would be better, however in the context of our build bots, we use AppleClang on Apple platforms, and the CMake shipped with Xcode should work with the AppleClang shipped alongside that Xcode. Differential Revision: https://reviews.llvm.org/D102083
2021-05-08 01:14:57 +08:00
# If we can find Ninja/CMake provided by Xcode, use those since we know their
# version will generally work with the Clang shipped in Xcode (e.g. if Clang
# knows about -std=c++20, the CMake bundled in Xcode will probably know about
# that flag too).
if xcrun --find ninja &>/dev/null; then NINJA="$(xcrun --find ninja)"; else NINJA="ninja"; fi
if xcrun --find cmake &>/dev/null; then CMAKE="$(xcrun --find cmake)"; else CMAKE="cmake"; fi
[libc++] Properly pick up the Ninja from Xcode in the CI script
2021-03-05 05:01:36 +08:00
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
function clean() {
rm -rf "${BUILD_DIR}"
}
[libcxx] [ci] Add a Windows CI configuration for a statically linked libc++ On Windows, static vs DLL linking affects details in quite a few cases, so it's good to have coverage for both cases. Testing with static linking also increases coverage for a number of cases and individual checks that have had to be waived for the DLL case, and allows testing libc++experimental, increasing the number of test cases actually executed by 180 (176 new tests from libc++experimental and 4 ones that are XFAIL windows-dll). Also drop the "generic-" prefix from these configuration names, as they're perhaps not what the "generic" prefix intended originally in the other generic-posix configurations. Differential Revision: https://reviews.llvm.org/D101565
2021-04-06 05:17:30 +08:00
function generate-cmake-base() {
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
echo "--- Generating CMake"
[libc++] Use Xcode's CMake if it's present This resolves issues when the CMake in use on the host is too old to configure libc++ properly, but Xcode has a sufficiently recent version. It is technically possible for the reverse issue to happen, where the Xcode version would be too old and the user-installed version would be better, however in the context of our build bots, we use AppleClang on Apple platforms, and the CMake shipped with Xcode should work with the AppleClang shipped alongside that Xcode. Differential Revision: https://reviews.llvm.org/D102083
2021-05-08 01:14:57 +08:00
${CMAKE} \
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
-B "${BUILD_DIR}" \
[libc++] Properly pick up the Ninja from Xcode in the CI script
2021-03-05 05:01:36 +08:00
-GNinja -DCMAKE_MAKE_PROGRAM="${NINJA}" \
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_INSTALL_PREFIX="${INSTALL_DIR}" \
-DLLVM_LIT_ARGS="-sv --show-unsupported --xunit-xml-output test-results.xml" \
[libcxx] [ci] Add a Windows CI configuration for a statically linked libc++ On Windows, static vs DLL linking affects details in quite a few cases, so it's good to have coverage for both cases. Testing with static linking also increases coverage for a number of cases and individual checks that have had to be waived for the DLL case, and allows testing libc++experimental, increasing the number of test cases actually executed by 180 (176 new tests from libc++experimental and 4 ones that are XFAIL windows-dll). Also drop the "generic-" prefix from these configuration names, as they're perhaps not what the "generic" prefix intended originally in the other generic-posix configurations. Differential Revision: https://reviews.llvm.org/D101565
2021-04-06 05:17:30 +08:00
"${@}"
}
function generate-cmake() {
generate-cmake-base \
-S "${MONOREPO_ROOT}/llvm" \
-DLLVM_ENABLE_PROJECTS="libcxx;libunwind;libcxxabi" \
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
-DLIBCXX_CXX_ABI=libcxxabi \
[libc++] Add a Buildkite job that tests back-deployment on Apple The current way we test this is pretty cheap, i.e. we download previously released macOS dylibs and run against that. Ideally, we would require a full host running the appropriate version of macOS, and we'd execute the tests using SSH on that host. But since we don't have such hosts available easily for now, this is better than nothing. At the same time, also fix some tests that were failing when back deploying. Differential Revision: https://reviews.llvm.org/D90869
2020-11-05 23:47:06 +08:00
"${@}"
}
[libcxx] [ci] Add a Windows CI configuration for a statically linked libc++ On Windows, static vs DLL linking affects details in quite a few cases, so it's good to have coverage for both cases. Testing with static linking also increases coverage for a number of cases and individual checks that have had to be waived for the DLL case, and allows testing libc++experimental, increasing the number of test cases actually executed by 180 (176 new tests from libc++experimental and 4 ones that are XFAIL windows-dll). Also drop the "generic-" prefix from these configuration names, as they're perhaps not what the "generic" prefix intended originally in the other generic-posix configurations. Differential Revision: https://reviews.llvm.org/D101565
2021-04-06 05:17:30 +08:00
function generate-cmake-libcxx-win() {
# TODO: Clang-cl in MSVC configurations don't have access to compiler_rt
# builtins helpers for int128 division. See
# https://reviews.llvm.org/D91139#2429595 for a comment about longterm
# intent for handling the issue. In the meantime, define
# -D_LIBCPP_HAS_NO_INT128 (both when building the library itself and
# when building tests) to allow enabling filesystem for running tests,
# even if it uses a non-permanent ABI.
generate-cmake-base \
-S "${MONOREPO_ROOT}/libcxx" \
-DCMAKE_C_COMPILER=clang-cl \
-DCMAKE_CXX_COMPILER=clang-cl \
-DLIBCXX_ENABLE_FILESYSTEM=YES \
-DCMAKE_CXX_FLAGS="-D_LIBCPP_HAS_NO_INT128" \
-DLIBCXX_TEST_COMPILER_FLAGS="-D_LIBCPP_HAS_NO_INT128" \
"${@}"
}
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
function check-cxx-cxxabi() {
[libc++] Add a CI configuration with static libc++/libc++abi Differential Revision: https://reviews.llvm.org/D99268
2021-03-24 21:50:59 +08:00
echo "--- Installing libc++ and libc++abi to a fake location"
${NINJA} -vC "${BUILD_DIR}" install-cxx install-cxxabi
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
echo "+++ Running the libc++ tests"
[libc++] Run ninja with --verbose This makes it easier to see what exact build commands are used. Differential Revision: https://reviews.llvm.org/D98992
2021-03-20 07:26:15 +08:00
${NINJA} -vC "${BUILD_DIR}" check-cxx
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
echo "+++ Running the libc++abi tests"
[libc++] Run ninja with --verbose This makes it easier to see what exact build commands are used. Differential Revision: https://reviews.llvm.org/D98992
2021-03-20 07:26:15 +08:00
${NINJA} -vC "${BUILD_DIR}" check-cxxabi
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
}
[libc++] Formalize what configurations are covered by the ABI lists By encoding ABI-affecting properties in the name of the ABI list, it makes it clear when an ABI list test should or should not be available, and what results we should expect. Note that we clearly don't encode all ABI-affecting parameters in the name right now -- I just ported over what we supported in the code that was there previously. As we encounter configurations that we wish to support but produce different ABI lists, we can add those to the ABI identifier and start supporting them. This commit also starts checking the ABI list in the CI jobs that run a supported configuration. Eventually, all configurations should have a generated ABI list and the test should even run implicitly as part of the Lit test suite. Differential Revision: https://reviews.llvm.org/D92194
2020-11-27 04:00:42 +08:00
# TODO: The goal is to test this against all configurations. We should also move
# this to the Lit test suite instead of being a separate CMake target.
function check-abi-list() {
echo "+++ Running the libc++ ABI list test"
[libc++] Run ninja with --verbose This makes it easier to see what exact build commands are used. Differential Revision: https://reviews.llvm.org/D98992
2021-03-20 07:26:15 +08:00
${NINJA} -vC "${BUILD_DIR}" check-cxx-abilist || (
[libc++] [P0482] [C++20] Implement missing bits for codecvt and codecvt_byname. Add codecvt*<char16_t, char8_t> and codecvt*<char32_t, char8_t>. Deprecate codecvt<char(16|32)_t, char>. Enable disabled tests. Update _LIBCPP_STD_VER to use 20 for C++20. Add _LIBCPP_DEPRECATED_IN_CXX20 macro. Reviewed By: ldionne, #libc, #libc_abi Differential Revision: https://reviews.llvm.org/D91517
2020-12-02 15:57:02 +08:00
echo "+++ Generating the libc++ ABI list after failed check"
[libc++] Run ninja with --verbose This makes it easier to see what exact build commands are used. Differential Revision: https://reviews.llvm.org/D98992
2021-03-20 07:26:15 +08:00
${NINJA} -vC "${BUILD_DIR}" generate-cxx-abilist
[libc++] [P0482] [C++20] Implement missing bits for codecvt and codecvt_byname. Add codecvt*<char16_t, char8_t> and codecvt*<char32_t, char8_t>. Deprecate codecvt<char(16|32)_t, char>. Enable disabled tests. Update _LIBCPP_STD_VER to use 20 for C++20. Add _LIBCPP_DEPRECATED_IN_CXX20 macro. Reviewed By: ldionne, #libc, #libc_abi Differential Revision: https://reviews.llvm.org/D91517
2020-12-02 15:57:02 +08:00
false
)
[libc++] Formalize what configurations are covered by the ABI lists By encoding ABI-affecting properties in the name of the ABI list, it makes it clear when an ABI list test should or should not be available, and what results we should expect. Note that we clearly don't encode all ABI-affecting parameters in the name right now -- I just ported over what we supported in the code that was there previously. As we encounter configurations that we wish to support but produce different ABI lists, we can add those to the ABI identifier and start supporting them. This commit also starts checking the ABI list in the CI jobs that run a supported configuration. Eventually, all configurations should have a generated ABI list and the test should even run implicitly as part of the Lit test suite. Differential Revision: https://reviews.llvm.org/D92194
2020-11-27 04:00:42 +08:00
}
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
function check-cxx-benchmarks() {
echo "--- Running the benchmarks"
[libc++] Run ninja with --verbose This makes it easier to see what exact build commands are used. Differential Revision: https://reviews.llvm.org/D98992
2021-03-20 07:26:15 +08:00
${NINJA} -vC "${BUILD_DIR}" check-cxx-benchmarks
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
}
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
[libc++] Print the CMake version before generating CMake
2021-04-02 01:40:04 +08:00
# Print the version of a few tools to aid diagnostics in some cases
[libc++] Use Xcode's CMake if it's present This resolves issues when the CMake in use on the host is too old to configure libc++ properly, but Xcode has a sufficiently recent version. It is technically possible for the reverse issue to happen, where the Xcode version would be too old and the user-installed version would be better, however in the context of our build bots, we use AppleClang on Apple platforms, and the CMake shipped with Xcode should work with the AppleClang shipped alongside that Xcode. Differential Revision: https://reviews.llvm.org/D102083
2021-05-08 01:14:57 +08:00
${CMAKE} --version
[libc++] Print the CMake version before generating CMake
2021-04-02 01:40:04 +08:00
${NINJA} --version
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
case "${BUILDER}" in
[libc++] Add format check to CI Note: contrary to what I said previously, I didn't change .clang-format nor utils/generate_feature_test_macro_components.py script. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D92229
2021-02-05 04:13:22 +08:00
check-format)
clean
echo "+++ Checking formatting"
# We need to set --extensions so that clang-format checks extensionless files.
mkdir -p ${BUILD_DIR}
git-clang-format \
--binary /usr/bin/clang-format --diff \
--extensions ',h,hh,hpp,hxx,c,cc,cxx,cpp' HEAD~1 \
-- \
libcxx/{benchmarks,include,src,test} \
libcxxabi/{fuzz,include,src,test} \
| tee ${BUILD_DIR}/clang-format.patch
# Check if the diff is empty, fail otherwise.
! grep -q '^--- a' ${BUILD_DIR}/clang-format.patch
;;
[libc++] [CI] Validate the output of the generated scripts. This adds a CI job validating that the output of utils/generate_feature_test_macro_components.py, libcxx/utils/generate_header_inclusion_tests.py, and utils/generate_header_tests.py are up to date. The validation method has been copied from the Format job. Differential Revision: https://reviews.llvm.org/D99862
2021-04-05 02:11:48 +08:00
check-generated-output)
[libc++][CI] Fix check-generated-output. Before the script detected non-ASCII characters but let them pass. This fixes the issue. I had a way to solve the issue, during review @Quuxplusone suggested a better alternative. The patch has been changed to use this alternative. Intended failed builds: - Not updated generated files https://buildkite.com/llvm-project/libcxx-ci/builds/2822 - Not updated generated files and non-ASCII usage https://buildkite.com/llvm-project/libcxx-ci/builds/2835 - Non-ASCII usage https://buildkite.com/llvm-project/libcxx-ci/builds/2836 Reviewed By: #libc, Quuxplusone, curdeius Differential Revision: https://reviews.llvm.org/D101303
2021-04-29 01:13:52 +08:00
# `! foo` doesn't work properly with `set -e`, use `! foo || false` instead.
# https://stackoverflow.com/questions/57681955/set-e-does-not-respect-logical-not
[libc++] [CI] Validate the output of the generated scripts. This adds a CI job validating that the output of utils/generate_feature_test_macro_components.py, libcxx/utils/generate_header_inclusion_tests.py, and utils/generate_header_tests.py are up to date. The validation method has been copied from the Format job. Differential Revision: https://reviews.llvm.org/D99862
2021-04-05 02:11:48 +08:00
clean
[libc++] Add a CMake target to re-generate files and revamp CONTRIBUTING.rst As we automate more and more things in the library, it becomes useful for contributors to have a single target for running all the automation as part of their workflow. This commit adds a new `libcxx-generate-files` target that should re-generate all the auto-generated files in the library. As a fly-by, I also revamped the documentation on Contributing to account for this new target and present it as a bullet list of things to check before committing. I also added a few things that are often overlooked to that list, such as updating the synopsis and the status files. Differential Revision: https://reviews.llvm.org/D106067
2021-07-15 22:19:39 +08:00
generate-cmake
# Reject patches that forgot to re-run the generator scripts.
echo "+++ Making sure the generator scripts were run"
${NINJA} -vC "${BUILD_DIR}" libcxx-generate-files
[libc++] [CI] Validate the output of the generated scripts. This adds a CI job validating that the output of utils/generate_feature_test_macro_components.py, libcxx/utils/generate_header_inclusion_tests.py, and utils/generate_header_tests.py are up to date. The validation method has been copied from the Format job. Differential Revision: https://reviews.llvm.org/D99862
2021-04-05 02:11:48 +08:00
git diff | tee ${BUILD_DIR}/generated_output.patch
[libc++][ci] Detect not committed generated files. The Generated output CI job only tests for modified files. This job should also fail the generated output contains new files. It would be possible to test modified and untracked files in one execution of `git ls-files`. However the diff is stored as an artifact so the execution of `git diff` would still be required. Discussion: Would it be better to do `git ls-files -om` and remove the excution of `! grep -q '^--- a' ${BUILD_DIR}/generated_output.patch || false` ? (Obviously then the name `generated_output.untracked` should change to something like `generated_output.status`) Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D106534
2021-07-22 17:17:53 +08:00
git ls-files -o --exclude-standard | tee ${BUILD_DIR}/generated_output.status
[libc++][CI] Fix check-generated-output. Before the script detected non-ASCII characters but let them pass. This fixes the issue. I had a way to solve the issue, during review @Quuxplusone suggested a better alternative. The patch has been changed to use this alternative. Intended failed builds: - Not updated generated files https://buildkite.com/llvm-project/libcxx-ci/builds/2822 - Not updated generated files and non-ASCII usage https://buildkite.com/llvm-project/libcxx-ci/builds/2835 - Non-ASCII usage https://buildkite.com/llvm-project/libcxx-ci/builds/2836 Reviewed By: #libc, Quuxplusone, curdeius Differential Revision: https://reviews.llvm.org/D101303
2021-04-29 01:13:52 +08:00
! grep -q '^--- a' ${BUILD_DIR}/generated_output.patch || false
[libc++][ci] Detect not committed generated files. The Generated output CI job only tests for modified files. This job should also fail the generated output contains new files. It would be possible to test modified and untracked files in one execution of `git ls-files`. However the diff is stored as an artifact so the execution of `git diff` would still be required. Discussion: Would it be better to do `git ls-files -om` and remove the excution of `! grep -q '^--- a' ${BUILD_DIR}/generated_output.patch || false` ? (Obviously then the name `generated_output.untracked` should change to something like `generated_output.status`) Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D106534
2021-07-22 17:17:53 +08:00
if [ -s ${BUILD_DIR}/generated_output.status ]; then
echo "It looks like not all the generator scripts were run,"
echo "did you forget to build the libcxx-generate-files target?"
echo "Did you add all new files it generated?"
false
fi
[libc++] Add a CMake target to re-generate files and revamp CONTRIBUTING.rst As we automate more and more things in the library, it becomes useful for contributors to have a single target for running all the automation as part of their workflow. This commit adds a new `libcxx-generate-files` target that should re-generate all the auto-generated files in the library. As a fly-by, I also revamped the documentation on Contributing to account for this new target and present it as a bullet list of things to check before committing. I also added a few things that are often overlooked to that list, such as updating the synopsis and the status files. Differential Revision: https://reviews.llvm.org/D106067
2021-07-15 22:19:39 +08:00
[libc++][CI] Fix check-generated-output. Before the script detected non-ASCII characters but let them pass. This fixes the issue. I had a way to solve the issue, during review @Quuxplusone suggested a better alternative. The patch has been changed to use this alternative. Intended failed builds: - Not updated generated files https://buildkite.com/llvm-project/libcxx-ci/builds/2822 - Not updated generated files and non-ASCII usage https://buildkite.com/llvm-project/libcxx-ci/builds/2835 - Non-ASCII usage https://buildkite.com/llvm-project/libcxx-ci/builds/2836 Reviewed By: #libc, Quuxplusone, curdeius Differential Revision: https://reviews.llvm.org/D101303
2021-04-29 01:13:52 +08:00
# Reject patches that introduce non-ASCII characters or hard tabs.
[libc++] [test] Recommit the unsetting of LC_COLLATE in the builder script. This re-reverts one piece of 1b885573327d0f6b36f24ad23d243642f658750b, reapplying one piece of D101437 (but not the "service"-queue piece of it). It turns out that the behavior of `grep [^ -~]`, or even `grep [A-Z]`, depends on locale, specifically `LC_COLLATE`. So we want to make sure we're not in any weird locale, no matter what machine we're running on. Yes, "en_US.UTF-8" counts as weird! https://stackoverflow.com/questions/67320156/misbehavior-of-gnu-grep-when-grepping-for-ignores-spaces https://stackoverflow.com/questions/6799872/how-to-make-grep-a-z-independent-of-locale
2021-05-01 02:43:33 +08:00
# Depends on LC_COLLATE set at the top of this script.
[libc++][CI] Fix check-generated-output. Before the script detected non-ASCII characters but let them pass. This fixes the issue. I had a way to solve the issue, during review @Quuxplusone suggested a better alternative. The patch has been changed to use this alternative. Intended failed builds: - Not updated generated files https://buildkite.com/llvm-project/libcxx-ci/builds/2822 - Not updated generated files and non-ASCII usage https://buildkite.com/llvm-project/libcxx-ci/builds/2835 - Non-ASCII usage https://buildkite.com/llvm-project/libcxx-ci/builds/2836 Reviewed By: #libc, Quuxplusone, curdeius Differential Revision: https://reviews.llvm.org/D101303
2021-04-29 01:13:52 +08:00
! grep -rn '[^ -~]' libcxx/include/ || false
[libc++] Add a CMake target to re-generate files and revamp CONTRIBUTING.rst As we automate more and more things in the library, it becomes useful for contributors to have a single target for running all the automation as part of their workflow. This commit adds a new `libcxx-generate-files` target that should re-generate all the auto-generated files in the library. As a fly-by, I also revamped the documentation on Contributing to account for this new target and present it as a bullet list of things to check before committing. I also added a few things that are often overlooked to that list, such as updating the synopsis and the status files. Differential Revision: https://reviews.llvm.org/D106067
2021-07-15 22:19:39 +08:00
# Reject patches that introduce dependency cycles in the headers.
[libc++] [CI] Fail if the headers contain cyclic dependencies. Since we have a tool to detect cycles now; and since we're entering a phase where people can easily introduce cycles by accident (D100682) or by request (D90999), I think it's increasingly important to shift the burden of detecting these cycles onto the buildbot instead of the poor human reviewer. Also, grep for non-ASCII characters (such as U+200B and U+00AD) and hard tabs; don't let those get checked in. Differential Review: https://reviews.llvm.org/D100703
2021-04-17 21:56:34 +08:00
python3 libcxx/utils/graph_header_deps.py >/dev/null
[libc++] [CI] Validate the output of the generated scripts. This adds a CI job validating that the output of utils/generate_feature_test_macro_components.py, libcxx/utils/generate_header_inclusion_tests.py, and utils/generate_header_tests.py are up to date. The validation method has been copied from the Format job. Differential Revision: https://reviews.llvm.org/D99862
2021-04-05 02:11:48 +08:00
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-cxx03)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Switch a few CI jobs to the minimal Lit configuration Eventually, this should become the default way of running the tests. For now, only move a few CI nodes to it, and keep a node that runs the legacy configuration. Differential Revision: https://reviews.llvm.org/D97565
2021-02-27 02:18:21 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-cxx03.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Formalize what configurations are covered by the ABI lists By encoding ABI-affecting properties in the name of the ABI list, it makes it clear when an ABI list test should or should not be available, and what results we should expect. Note that we clearly don't encode all ABI-affecting parameters in the name right now -- I just ported over what we supported in the code that was there previously. As we encounter configurations that we wish to support but produce different ABI lists, we can add those to the ABI identifier and start supporting them. This commit also starts checking the ABI list in the CI jobs that run a supported configuration. Eventually, all configurations should have a generated ABI list and the test should even run implicitly as part of the Lit test suite. Differential Revision: https://reviews.llvm.org/D92194
2020-11-27 04:00:42 +08:00
check-abi-list
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-cxx11)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Switch a few CI jobs to the minimal Lit configuration Eventually, this should become the default way of running the tests. For now, only move a few CI nodes to it, and keep a node that runs the legacy configuration. Differential Revision: https://reviews.llvm.org/D97565
2021-02-27 02:18:21 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-cxx11.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Formalize what configurations are covered by the ABI lists By encoding ABI-affecting properties in the name of the ABI list, it makes it clear when an ABI list test should or should not be available, and what results we should expect. Note that we clearly don't encode all ABI-affecting parameters in the name right now -- I just ported over what we supported in the code that was there previously. As we encounter configurations that we wish to support but produce different ABI lists, we can add those to the ABI identifier and start supporting them. This commit also starts checking the ABI list in the CI jobs that run a supported configuration. Eventually, all configurations should have a generated ABI list and the test should even run implicitly as part of the Lit test suite. Differential Revision: https://reviews.llvm.org/D92194
2020-11-27 04:00:42 +08:00
check-abi-list
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-cxx14)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Switch a few CI jobs to the minimal Lit configuration Eventually, this should become the default way of running the tests. For now, only move a few CI nodes to it, and keep a node that runs the legacy configuration. Differential Revision: https://reviews.llvm.org/D97565
2021-02-27 02:18:21 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-cxx14.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Formalize what configurations are covered by the ABI lists By encoding ABI-affecting properties in the name of the ABI list, it makes it clear when an ABI list test should or should not be available, and what results we should expect. Note that we clearly don't encode all ABI-affecting parameters in the name right now -- I just ported over what we supported in the code that was there previously. As we encounter configurations that we wish to support but produce different ABI lists, we can add those to the ABI identifier and start supporting them. This commit also starts checking the ABI list in the CI jobs that run a supported configuration. Eventually, all configurations should have a generated ABI list and the test should even run implicitly as part of the Lit test suite. Differential Revision: https://reviews.llvm.org/D92194
2020-11-27 04:00:42 +08:00
check-abi-list
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-cxx17)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Switch a few CI jobs to the minimal Lit configuration Eventually, this should become the default way of running the tests. For now, only move a few CI nodes to it, and keep a node that runs the legacy configuration. Differential Revision: https://reviews.llvm.org/D97565
2021-02-27 02:18:21 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-cxx17.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Formalize what configurations are covered by the ABI lists By encoding ABI-affecting properties in the name of the ABI list, it makes it clear when an ABI list test should or should not be available, and what results we should expect. Note that we clearly don't encode all ABI-affecting parameters in the name right now -- I just ported over what we supported in the code that was there previously. As we encounter configurations that we wish to support but produce different ABI lists, we can add those to the ABI identifier and start supporting them. This commit also starts checking the ABI list in the CI jobs that run a supported configuration. Eventually, all configurations should have a generated ABI list and the test should even run implicitly as part of the Lit test suite. Differential Revision: https://reviews.llvm.org/D92194
2020-11-27 04:00:42 +08:00
check-abi-list
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++] Use c++20 instead of c++2a consistently. * The only exception is that the flag -std=c++2a is still used not to break compatibility with older compilers (clang <= 9, gcc <= 9). * Bump _LIBCPP_STD_VER for C++20 to 20 and use 21 for the future standard (C++2b). That's a preparation step to add c++2b support to libc++. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D93383
2021-01-07 19:29:04 +08:00
generic-cxx20)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Switch a few CI jobs to the minimal Lit configuration Eventually, this should become the default way of running the tests. For now, only move a few CI nodes to it, and keep a node that runs the legacy configuration. Differential Revision: https://reviews.llvm.org/D97565
2021-02-27 02:18:21 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-cxx20.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Add basic support for -std=c++2b. * Add feature test macros. * Add buildbot configuration generic-cxx2b that uses clang-tot. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D94227
2021-01-09 01:40:42 +08:00
check-abi-list
;;
generic-cxx2b)
clean
[libc++] Switch a few CI jobs to the minimal Lit configuration Eventually, this should become the default way of running the tests. For now, only move a few CI nodes to it, and keep a node that runs the legacy configuration. Differential Revision: https://reviews.llvm.org/D97565
2021-02-27 02:18:21 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-cxx2b.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Add basic support for -std=c++2b. * Add feature test macros. * Add buildbot configuration generic-cxx2b that uses clang-tot. Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D94227
2021-01-09 01:40:42 +08:00
check-cxx-cxxabi
[libc++] Formalize what configurations are covered by the ABI lists By encoding ABI-affecting properties in the name of the ABI list, it makes it clear when an ABI list test should or should not be available, and what results we should expect. Note that we clearly don't encode all ABI-affecting parameters in the name right now -- I just ported over what we supported in the code that was there previously. As we encounter configurations that we wish to support but produce different ABI lists, we can add those to the ABI identifier and start supporting them. This commit also starts checking the ABI list in the CI jobs that run a supported configuration. Eventually, all configurations should have a generated ABI list and the test should even run implicitly as part of the Lit test suite. Differential Revision: https://reviews.llvm.org/D92194
2020-11-27 04:00:42 +08:00
check-abi-list
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++] Fix libc++ build with assertions enabled This fixes http://llvm.org/PR50534. This is another take on D103960 which is less disruptive. Differential Revision: https://reviews.llvm.org/D103964
2021-06-09 21:41:27 +08:00
generic-assertions)
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-assertions.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Fix libc++ build with assertions enabled This fixes http://llvm.org/PR50534. This is another take on D103960 which is less disruptive. Differential Revision: https://reviews.llvm.org/D103964
2021-06-09 21:41:27 +08:00
check-cxx-cxxabi
check-abi-list
;;
[libc++] [test] Add a debug-mode CI. To run llvm-lit manually from the command line: ./bin/llvm-lit -sv --param std=c++2b --param cxx_under_test=`pwd`/bin/clang \ --param debug_level=1 ../libcxx/test/ Tests that currently fail with `debug_level=1` are marked `LIBCXX-DEBUG-FIXME`, but my intent is to deal with all of them and leave no such annotations in the codebase within the next couple weeks. (I have patches for all of them in my local checkout.) Differential Revision: https://reviews.llvm.org/D100866
2021-04-20 23:27:03 +08:00
generic-debug-iterators)
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-debug-iterators.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] [test] Add a debug-mode CI. To run llvm-lit manually from the command line: ./bin/llvm-lit -sv --param std=c++2b --param cxx_under_test=`pwd`/bin/clang \ --param debug_level=1 ../libcxx/test/ Tests that currently fail with `debug_level=1` are marked `LIBCXX-DEBUG-FIXME`, but my intent is to deal with all of them and leave no such annotations in the codebase within the next couple weeks. (I have patches for all of them in my local checkout.) Differential Revision: https://reviews.llvm.org/D100866
2021-04-20 23:27:03 +08:00
check-cxx-cxxabi
check-abi-list
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-noexceptions)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-noexceptions.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++] Add a CI configuration for the modular build Differential Revision: https://reviews.llvm.org/D103559
2021-06-03 05:07:57 +08:00
generic-modules)
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-modules.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Add a CI configuration for the modular build Differential Revision: https://reviews.llvm.org/D103559
2021-06-03 05:07:57 +08:00
check-cxx-cxxabi
;;
[libc++] Add a CI configuration with static libc++/libc++abi Differential Revision: https://reviews.llvm.org/D99268
2021-03-24 21:50:59 +08:00
generic-static)
clean
[libc++] Switch a few CI jobs to the minimal Lit configuration Eventually, this should become the default way of running the tests. For now, only move a few CI nodes to it, and keep a node that runs the legacy configuration. Differential Revision: https://reviews.llvm.org/D97565
2021-02-27 02:18:21 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-static.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-static.cfg.in"
[libc++] Add a CI configuration with static libc++/libc++abi Differential Revision: https://reviews.llvm.org/D99268
2021-03-24 21:50:59 +08:00
check-cxx-cxxabi
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-32bit)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-32bits.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++][ci] Test Clang ToT by default, and add jobs on Clang 11 and 12 It makes the most sense to test with Clang ToT by default since that's exactly what we're trying to QA: that libc++ works with whatever compiler we're going to release next.
2021-07-09 00:26:33 +08:00
generic-clang-11)
export CC=clang-11
export CXX=clang++-11
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++][ci] Test Clang ToT by default, and add jobs on Clang 11 and 12 It makes the most sense to test with Clang ToT by default since that's exactly what we're trying to QA: that libc++ works with whatever compiler we're going to release next.
2021-07-09 00:26:33 +08:00
check-cxx-cxxabi
;;
generic-clang-12)
export CC=clang-12
export CXX=clang++-12
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++][ci] Test Clang ToT by default, and add jobs on Clang 11 and 12 It makes the most sense to test with Clang ToT by default since that's exactly what we're trying to QA: that libc++ works with whatever compiler we're going to release next.
2021-07-09 00:26:33 +08:00
check-cxx-cxxabi
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-gcc)
[libc++] Promote GCC 11 to mandatory CI Also, fix the last issue that prevented GCC 11 from passing the test suite. Thanks to everyone else who fixed issues. Differential Revision: https://reviews.llvm.org/D104315
2021-06-16 03:07:03 +08:00
export CC=gcc-11
export CXX=g++-11
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Add a CI configuration with static libc++/libc++abi Differential Revision: https://reviews.llvm.org/D99268
2021-03-24 21:50:59 +08:00
generate-cmake
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++] Add a job running GCC with C++11 This configuration is interesting because GCC has a different level of strictness for some C++ rules. In particular, it implements the older standards more stringently than Clang, which can help find places where we are non-conforming (especially in the test suite). Differential Revision: https://reviews.llvm.org/D105936
2021-07-15 21:46:36 +08:00
generic-gcc-cxx11)
export CC=gcc-11
export CXX=g++-11
clean
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-cxx11.cmake"
check-cxx-cxxabi
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-asan)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-asan.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-msan)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-msan.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-tsan)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-tsan.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-ubsan)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-ubsan.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-with_llvm_unwinder)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -DLIBCXXABI_USE_LLVM_UNWINDER=ON \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++][ci] Add a job to run the vanilla configuration on Apple Previously, we'd only have jobs testing the Apple cache on Apple platforms, but libc++ should also work out-of-the-box.
2020-10-02 01:55:39 +08:00
generic-singlethreaded)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-singlethreaded.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
;;
[libc++] NFC: nodebug => no-debug in the CI configurations
2021-03-24 02:09:52 +08:00
generic-no-debug)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-no-debug.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Add a CMake option to control whether the debug mode is supported Some libc++ builds may want to disable support for the debug mode, for example to reduce code size or because the current implementation of the debug mode requires a global map. This commit adds the LIBCXX_ENABLE_DEBUG_MODE CMake option and ties it into the test suite. It also adds a CI job to test this configuration going forward. Differential Revision: https://reviews.llvm.org/D88923
2020-10-07 04:46:58 +08:00
;;
[libc++] Make LIBCXX_ENABLE_FILESYSTEM fully consistent Previously, LIBCXX_ENABLE_FILESYSTEM controlled only whether the filesystem support was compiled into libc++'s library. This commit promotes the setting to a first-class option like LIBCXX_ENABLE_LOCALIZATION, where the whole library is aware of the setting and features that depend on <filesystem> won't be provided at all. The test suite is also properly annotated such that tests that depend on <filesystem> are disabled when the library doesn't support it. This is an alternative to https://llvm.org/D94824, but also an improvement along the lines of LIBCXX_ENABLE_LOCALIZATION that I had been wanting to make for a while. Differential Revision: https://reviews.llvm.org/D94921
2021-01-19 01:18:18 +08:00
generic-no-filesystem)
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-no-filesystem.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Make LIBCXX_ENABLE_FILESYSTEM fully consistent Previously, LIBCXX_ENABLE_FILESYSTEM controlled only whether the filesystem support was compiled into libc++'s library. This commit promotes the setting to a first-class option like LIBCXX_ENABLE_LOCALIZATION, where the whole library is aware of the setting and features that depend on <filesystem> won't be provided at all. The test suite is also properly annotated such that tests that depend on <filesystem> are disabled when the library doesn't support it. This is an alternative to https://llvm.org/D94824, but also an improvement along the lines of LIBCXX_ENABLE_LOCALIZATION that I had been wanting to make for a while. Differential Revision: https://reviews.llvm.org/D94921
2021-01-19 01:18:18 +08:00
check-cxx-cxxabi
;;
[libc++] Allow building libc++ on platforms without a random device Some platforms, like several embedded platforms, do not provide a source of randomness through a random device. This commit makes it possible to build and test libc++ for such platforms, i.e. without std::random_device. Surprisingly, the only functionality that doesn't work on such platforms is std::random_device itself -- everything else in <random> still works, one just has to find alternative ways to seed the PRNGs.
2020-10-15 22:32:09 +08:00
generic-no-random_device)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-no-random_device.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++] Allow building libc++ on platforms without a random device Some platforms, like several embedded platforms, do not provide a source of randomness through a random device. This commit makes it possible to build and test libc++ for such platforms, i.e. without std::random_device. Surprisingly, the only functionality that doesn't work on such platforms is std::random_device itself -- everything else in <random> still works, one just has to find alternative ways to seed the PRNGs.
2020-10-15 22:32:09 +08:00
;;
[libc++] Add a libc++ configuration that does not support localization When porting libc++ to embedded systems, it can be useful to drop support for localization, which these systems don't implement or care about. Differential Revision: https://reviews.llvm.org/D90072
2020-10-10 03:31:05 +08:00
generic-no-localization)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-no-localization.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Add a libc++ configuration that does not support localization When porting libc++ to embedded systems, it can be useful to drop support for localization, which these systems don't implement or care about. Differential Revision: https://reviews.llvm.org/D90072
2020-10-10 03:31:05 +08:00
check-cxx-cxxabi
;;
[libc++][format] Add a CMake Unicode option. This option is used to select between the format headers output column width option. This option should be independent of the locale setting. It's encouraged to default to Unicode unless the platform doesn't offer that option. [format.string.std]/10 ``` For the purposes of width computation, a string is assumed to be in a locale-independent, implementation-defined encoding. Implementations should use a Unicode encoding on platforms capable of displaying Unicode ``` Reviewed By: #libc, ldionne, vitaut Differential Revision: https://reviews.llvm.org/D103379
2021-05-26 02:11:08 +08:00
generic-no-unicode)
clean
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-no-unicode.cmake"
check-cxx-cxxabi
;;
[libc++][ci] Add a configuration testing Apple's system library build Differential Revision: https://reviews.llvm.org/D88650
2020-10-01 20:55:40 +08:00
x86_64-apple-system)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Apple.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
[libc++][ci] Add a configuration testing Apple's system library build Differential Revision: https://reviews.llvm.org/D88650
2020-10-01 20:55:40 +08:00
;;
x86_64-apple-system-noexceptions)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Apple.cmake" \
-DLIBCXX_ENABLE_EXCEPTIONS=OFF \
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
-DLIBCXXABI_ENABLE_EXCEPTIONS=OFF \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-cxxabi
;;
[libc++] Add a Buildkite job that tests back-deployment on Apple The current way we test this is pretty cheap, i.e. we download previously released macOS dylibs and run against that. Ideally, we would require a full host running the appropriate version of macOS, and we'd execute the tests using SSH on that host. But since we don't have such hosts available easily for now, this is better than nothing. At the same time, also fix some tests that were failing when back deploying. Differential Revision: https://reviews.llvm.org/D90869
2020-11-05 23:47:06 +08:00
x86_64-apple-system-backdeployment-*)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
if [[ "${OSX_ROOTS}" == "" ]]; then
echo "--- Downloading previous macOS dylibs"
[libc++] Re-enable macOS back-deployment testing Download older roots from Dropbox instead of Green Dragon, which is too unreliable. Also XFAIL tests that were broken for back-deployment configurations by D98097. Differential Revision: https://reviews.llvm.org/D99359
2021-03-26 02:14:20 +08:00
PREVIOUS_DYLIBS_URL="https://dl.dropboxusercontent.com/s/liu4fmc53qzlfly/libcxx-roots.tar.gz"
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
OSX_ROOTS="${BUILD_DIR}/macos-roots"
mkdir -p "${OSX_ROOTS}"
curl "${PREVIOUS_DYLIBS_URL}" | tar -xz --strip-components=1 -C "${OSX_ROOTS}"
fi
DEPLOYMENT_TARGET="${BUILDER#x86_64-apple-system-backdeployment-}"
[libc++/abi] Allow running back-deployment testing against libc++abi Before this patch, we could only link against the back-deployment libc++abi dylib. This patch allows linking against the just-built libc++abi, but running against the back-deployment one -- just like we do for libc++. Also, add XFAIL markup to flag expected errors. Differential Revision: https://reviews.llvm.org/D91069
2020-07-09 04:38:54 +08:00
# TODO: On Apple platforms, we never produce libc++abi.1.dylib, always libc++abi.dylib.
# Fix that in the build so that the tests stop searching for @rpath/libc++abi.1.dylib.
cp "${OSX_ROOTS}/macOS/libc++abi/${DEPLOYMENT_TARGET}/libc++abi.dylib" \
"${OSX_ROOTS}/macOS/libc++abi/${DEPLOYMENT_TARGET}/libc++abi.1.dylib"
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
PARAMS="target_triple=x86_64-apple-macosx${DEPLOYMENT_TARGET}"
PARAMS+=";cxx_runtime_root=${OSX_ROOTS}/macOS/libc++/${DEPLOYMENT_TARGET}"
[libc++/abi] Allow running back-deployment testing against libc++abi Before this patch, we could only link against the back-deployment libc++abi dylib. This patch allows linking against the just-built libc++abi, but running against the back-deployment one -- just like we do for libc++. Also, add XFAIL markup to flag expected errors. Differential Revision: https://reviews.llvm.org/D91069
2020-07-09 04:38:54 +08:00
PARAMS+=";abi_runtime_root=${OSX_ROOTS}/macOS/libc++abi/${DEPLOYMENT_TARGET}"
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
PARAMS+=";use_system_cxx_lib=True"
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Apple.cmake" \
-DLIBCXX_TEST_PARAMS="${PARAMS}" \
-DLIBCXXABI_TEST_PARAMS="${PARAMS}"
[libc++/abi] Allow running back-deployment testing against libc++abi Before this patch, we could only link against the back-deployment libc++abi dylib. This patch allows linking against the just-built libc++abi, but running against the back-deployment one -- just like we do for libc++. Also, add XFAIL markup to flag expected errors. Differential Revision: https://reviews.llvm.org/D91069
2020-07-09 04:38:54 +08:00
check-cxx-cxxabi
[libc++] Add a Buildkite job that tests back-deployment on Apple The current way we test this is pretty cheap, i.e. we download previously released macOS dylibs and run against that. Ideally, we would require a full host running the appropriate version of macOS, and we'd execute the tests using SSH on that host. But since we don't have such hosts available easily for now, this is better than nothing. At the same time, also fix some tests that were failing when back deploying. Differential Revision: https://reviews.llvm.org/D90869
2020-11-05 23:47:06 +08:00
;;
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
benchmarks)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Refactor the run-buildbot script to make it more modular, and run the benchmarks As a fly-by fix, unbreak the benchmarks on Apple platforms. Differential Revision: https://reviews.llvm.org/D90043
2020-10-23 22:02:14 +08:00
check-cxx-benchmarks
[libc++][ci] Add a configuration testing Apple's system library build Differential Revision: https://reviews.llvm.org/D88650
2020-10-01 20:55:40 +08:00
;;
[libc++] Add a CI job to build the documentation At the same time, fix an issue that broke the documentation since 2eadbc86142b.
2020-11-06 03:34:29 +08:00
documentation)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
generate-cmake -DLLVM_ENABLE_SPHINX=ON
echo "+++ Generating documentation"
[libc++] Run ninja with --verbose This makes it easier to see what exact build commands are used. Differential Revision: https://reviews.llvm.org/D98992
2021-03-20 07:26:15 +08:00
${NINJA} -vC "${BUILD_DIR}" docs-libcxx-html
[libc++] Add a CI job to build the documentation At the same time, fix an issue that broke the documentation since 2eadbc86142b.
2020-11-06 03:34:29 +08:00
;;
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
unified-standalone)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
echo "--- Generating CMake"
[libc++] Use Xcode's CMake if it's present This resolves issues when the CMake in use on the host is too old to configure libc++ properly, but Xcode has a sufficiently recent version. It is technically possible for the reverse issue to happen, where the Xcode version would be too old and the user-installed version would be better, however in the context of our build bots, we use AppleClang on Apple platforms, and the CMake shipped with Xcode should work with the AppleClang shipped alongside that Xcode. Differential Revision: https://reviews.llvm.org/D102083
2021-05-08 01:14:57 +08:00
${CMAKE} \
-S "${MONOREPO_ROOT}/libcxx/utils/ci/runtimes" \
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
-B "${BUILD_DIR}" \
[libc++] Properly pick up the Ninja from Xcode in the CI script
2021-03-05 05:01:36 +08:00
-GNinja -DCMAKE_MAKE_PROGRAM="${NINJA}" \
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_INSTALL_PREFIX="${INSTALL_DIR}" \
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
-DLLVM_ENABLE_PROJECTS="libcxx;libcxxabi;libunwind" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
check-cxx-cxxabi
;;
[libc++] Add a CI job to test the Runtimes build Differential Revision: https://reviews.llvm.org/D97888
2021-03-17 02:57:42 +08:00
runtimes-build)
clean
echo "--- Generating CMake"
[libc++][ci] Enable modules in the Runtimes build The runtimes build has assertions enabled, which is necessary to catch some of the modules-related issues we've been seeing recently. This patch enables testing with modules in the runtimes build so as to cover those cases. In the future, a better solution would be to systematically use versions of Clang that have assertions enabled. However, the Clangs we release currently don't have assertions enabled by default, which causes a challenge for the CI (we could try to build our own Clang from ToT with assertions in the CI, but that poses some problems). Differential Revision: https://reviews.llvm.org/D104252
2021-06-15 02:36:13 +08:00
# TODO: We currently enable modules and assertions in the runtimes build
# because that provides coverage for some specific Clang failures
# we've been seeing recently, however it would be better to instead
# run all CI configurations against a Clang that has assertions enabled.
[libc++] Use Xcode's CMake if it's present This resolves issues when the CMake in use on the host is too old to configure libc++ properly, but Xcode has a sufficiently recent version. It is technically possible for the reverse issue to happen, where the Xcode version would be too old and the user-installed version would be better, however in the context of our build bots, we use AppleClang on Apple platforms, and the CMake shipped with Xcode should work with the AppleClang shipped alongside that Xcode. Differential Revision: https://reviews.llvm.org/D102083
2021-05-08 01:14:57 +08:00
${CMAKE} \
-S "${MONOREPO_ROOT}/llvm" \
[libc++] Add a CI job to test the Runtimes build Differential Revision: https://reviews.llvm.org/D97888
2021-03-17 02:57:42 +08:00
-B "${BUILD_DIR}" \
[libc++] Use Xcode's CMake if it's present This resolves issues when the CMake in use on the host is too old to configure libc++ properly, but Xcode has a sufficiently recent version. It is technically possible for the reverse issue to happen, where the Xcode version would be too old and the user-installed version would be better, however in the context of our build bots, we use AppleClang on Apple platforms, and the CMake shipped with Xcode should work with the AppleClang shipped alongside that Xcode. Differential Revision: https://reviews.llvm.org/D102083
2021-05-08 01:14:57 +08:00
-GNinja -DCMAKE_MAKE_PROGRAM="${NINJA}" \
[libc++] Add a CI job to test the Runtimes build Differential Revision: https://reviews.llvm.org/D97888
2021-03-17 02:57:42 +08:00
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_INSTALL_PREFIX="${INSTALL_DIR}" \
-DLLVM_ENABLE_PROJECTS="clang" \
-DLLVM_ENABLE_RUNTIMES="libcxx;libcxxabi" \
[libcxx][ci] enables assertions for runtimes-build This will catch nasty Clang bugs like https://bugs.llvm.org/show_bug.cgi?id=50592 before we merge stuff into libc++ main. Differential Revision: https://reviews.llvm.org/D103863
2021-06-08 08:09:36 +08:00
-DLLVM_RUNTIME_TARGETS="x86_64-unknown-linux-gnu" \
[libc++][ci] Enable modules in the Runtimes build The runtimes build has assertions enabled, which is necessary to catch some of the modules-related issues we've been seeing recently. This patch enables testing with modules in the runtimes build so as to cover those cases. In the future, a better solution would be to systematically use versions of Clang that have assertions enabled. However, the Clangs we release currently don't have assertions enabled by default, which causes a challenge for the CI (we could try to build our own Clang from ToT with assertions in the CI, but that poses some problems). Differential Revision: https://reviews.llvm.org/D104252
2021-06-15 02:36:13 +08:00
-DLLVM_ENABLE_ASSERTIONS=ON \
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
-C "${MONOREPO_ROOT}/libcxx/cmake/caches/Generic-modules.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libc++] Add a CI job to test the Runtimes build Differential Revision: https://reviews.llvm.org/D97888
2021-03-17 02:57:42 +08:00
echo "+++ Running the libc++ and libc++abi tests"
${NINJA} -C "${BUILD_DIR}" check-runtimes
echo "--- Installing libc++ and libc++abi to a fake location"
[libc++][docs] Overhaul the documentation for building and using libc++ This patch overhauls the documentation around building libc++ for vendors, and using libc++ for end-users. It also: - Removes mention of the standalone build, which we've been trying to get rid of for a long time. - Removes mention of using a local ABI installation, which we don't do and is documented as "not recommended". - Removes mention of the separate libc++filesystem.a library, which isn't relevant anymore since filesystem support is in the main library. - Adds mention of the GDB pretty printers and how to use them.
2021-07-06 22:39:01 +08:00
${NINJA} -C "${BUILD_DIR}" install-runtimes
[libc++] Add a CI job to test the Runtimes build Differential Revision: https://reviews.llvm.org/D97888
2021-03-17 02:57:42 +08:00
;;
[libc++] Switch a few CI jobs to the minimal Lit configuration Eventually, this should become the default way of running the tests. For now, only move a few CI nodes to it, and keep a node that runs the legacy configuration. Differential Revision: https://reviews.llvm.org/D97565
2021-02-27 02:18:21 +08:00
legacy-test-config)
clean
generate-cmake -DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/legacy.cfg.in"
check-cxx-cxxabi
;;
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
legacy-standalone)
[libc++] Allow customizing a few paths when running build bots This allows reusing run-buildbot for downstream testing as well.
2020-11-06 08:02:32 +08:00
clean
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
echo "--- Generating CMake"
[libc++] Use Xcode's CMake if it's present This resolves issues when the CMake in use on the host is too old to configure libc++ properly, but Xcode has a sufficiently recent version. It is technically possible for the reverse issue to happen, where the Xcode version would be too old and the user-installed version would be better, however in the context of our build bots, we use AppleClang on Apple platforms, and the CMake shipped with Xcode should work with the AppleClang shipped alongside that Xcode. Differential Revision: https://reviews.llvm.org/D102083
2021-05-08 01:14:57 +08:00
${CMAKE} \
-S "${MONOREPO_ROOT}/libcxx" \
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
-B "${BUILD_DIR}/libcxx" \
[libc++] Properly pick up the Ninja from Xcode in the CI script
2021-03-05 05:01:36 +08:00
-GNinja -DCMAKE_MAKE_PROGRAM="${NINJA}" \
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_INSTALL_PREFIX="${INSTALL_DIR}" \
-DLLVM_PATH="${MONOREPO_ROOT}/llvm" \
-DLIBCXX_CXX_ABI=libcxxabi \
-DLIBCXX_CXX_ABI_INCLUDE_PATHS="${MONOREPO_ROOT}/libcxxabi/include" \
-DLIBCXX_CXX_ABI_LIBRARY_PATH="${BUILD_DIR}/libcxxabi/lib"
[libc++] Use Xcode's CMake if it's present This resolves issues when the CMake in use on the host is too old to configure libc++ properly, but Xcode has a sufficiently recent version. It is technically possible for the reverse issue to happen, where the Xcode version would be too old and the user-installed version would be better, however in the context of our build bots, we use AppleClang on Apple platforms, and the CMake shipped with Xcode should work with the AppleClang shipped alongside that Xcode. Differential Revision: https://reviews.llvm.org/D102083
2021-05-08 01:14:57 +08:00
${CMAKE} \
-S "${MONOREPO_ROOT}/libcxxabi" \
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
-B "${BUILD_DIR}/libcxxabi" \
[libc++] Properly pick up the Ninja from Xcode in the CI script
2021-03-05 05:01:36 +08:00
-GNinja -DCMAKE_MAKE_PROGRAM="${NINJA}" \
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DCMAKE_INSTALL_PREFIX="${INSTALL_DIR}" \
-DLLVM_PATH="${MONOREPO_ROOT}/llvm" \
-DLIBCXXABI_LIBCXX_PATH="${MONOREPO_ROOT}/libcxx" \
[libc++] Include <__config_site> from <__config> Prior to this patch, we would generate a fancy <__config> header by concatenating <__config_site> and <__config>. This complexifies the build system and also increases the difference between what's tested and what's actually installed. This patch removes that complexity and instead simply installs <__config_site> alongside the libc++ headers. <__config_site> is then included by <__config>, which is much simpler. Doing this also opens the door to having different <__config_site> headers depending on the target, which was impossible before. It does change the workflow for testing header-only changes to libc++. Previously, we would run `lit` against the headers in libcxx/include. After this patch, we run it against a fake installation root of the headers (containing a proper <__config_site> header). This makes use closer to testing what we actually install, which is good, however it does mean that we have to update that root before testing header changes. Thus, we now need to run `ninja check-cxx-deps` before running `lit` by hand. Differential Revision: https://reviews.llvm.org/D97572
2020-06-27 00:08:59 +08:00
-DLIBCXXABI_LIBCXX_INCLUDES="${BUILD_DIR}/libcxx/include/c++/v1" \
[libc++abi] Make sure we can run the tests in Standalone mode The tests would previously fail if the `python` executable wasn't found, because we were missing the mandatory find_package.
2020-10-27 02:25:49 +08:00
-DLIBCXXABI_LIBCXX_LIBRARY_PATH="${BUILD_DIR}/libcxx/lib"
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
[libc++] Include <__config_site> from <__config> Prior to this patch, we would generate a fancy <__config> header by concatenating <__config_site> and <__config>. This complexifies the build system and also increases the difference between what's tested and what's actually installed. This patch removes that complexity and instead simply installs <__config_site> alongside the libc++ headers. <__config_site> is then included by <__config>, which is much simpler. Doing this also opens the door to having different <__config_site> headers depending on the target, which was impossible before. It does change the workflow for testing header-only changes to libc++. Previously, we would run `lit` against the headers in libcxx/include. After this patch, we run it against a fake installation root of the headers (containing a proper <__config_site> header). This makes use closer to testing what we actually install, which is good, however it does mean that we have to update that root before testing header changes. Thus, we now need to run `ninja check-cxx-deps` before running `lit` by hand. Differential Revision: https://reviews.llvm.org/D97572
2020-06-27 00:08:59 +08:00
echo "+++ Generating libc++ headers"
${NINJA} -vC "${BUILD_DIR}/libcxx" generate-cxx-headers
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
echo "+++ Building libc++abi"
[libc++] Run ninja with --verbose This makes it easier to see what exact build commands are used. Differential Revision: https://reviews.llvm.org/D98992
2021-03-20 07:26:15 +08:00
${NINJA} -vC "${BUILD_DIR}/libcxxabi" cxxabi
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
echo "+++ Building libc++"
[libc++] Run ninja with --verbose This makes it easier to see what exact build commands are used. Differential Revision: https://reviews.llvm.org/D98992
2021-03-20 07:26:15 +08:00
${NINJA} -vC "${BUILD_DIR}/libcxx" cxx
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
echo "+++ Running the libc++ tests"
[libc++] Run ninja with --verbose This makes it easier to see what exact build commands are used. Differential Revision: https://reviews.llvm.org/D98992
2021-03-20 07:26:15 +08:00
${NINJA} -vC "${BUILD_DIR}/libcxx" check-cxx
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
echo "+++ Running the libc++abi tests"
[libc++] Run ninja with --verbose This makes it easier to see what exact build commands are used. Differential Revision: https://reviews.llvm.org/D98992
2021-03-20 07:26:15 +08:00
${NINJA} -vC "${BUILD_DIR}/libcxxabi" check-cxxabi
[libc++] Add a CI jobs to test the Standalone builds
2020-10-24 04:27:41 +08:00
;;
[libcxx] Move Linaro AArch64 buildbots to buildkite Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D96267
2021-02-08 18:43:21 +08:00
aarch64)
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/AArch64.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libcxx] Move Linaro AArch64 buildbots to buildkite Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D96267
2021-02-08 18:43:21 +08:00
check-cxx-cxxabi
;;
aarch64-noexceptions)
clean
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/AArch64.cmake" \
[libc++] NFC: Reindent the run-buildbot script
2021-07-16 01:29:47 +08:00
-DLIBCXX_ENABLE_EXCEPTIONS=OFF \
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
-DLIBCXXABI_ENABLE_EXCEPTIONS=OFF \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libcxx] Move Linaro AArch64 buildbots to buildkite Reviewed By: #libc, ldionne Differential Revision: https://reviews.llvm.org/D96267
2021-02-08 18:43:21 +08:00
check-cxx-cxxabi
;;
[libcxx] Move Linaro 32 bit armv bots to buildkite Instead of setting mcpu like the previous bots, set the target triple. Each config builds either Arm only or Thumb only code. This gives us some coverage of thumb specific issues. The new agents on Linaro's side are running on v8 hardware so will report arch "armv8l" just like the v8 bots. (and buildkite can choose any of them for v7/v8 jobs) Reviewed By: #libc, curdeius, Mordante Differential Revision: https://reviews.llvm.org/D98019
2021-03-02 23:07:19 +08:00
# Aka Armv8 32 bit
armv8)
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Armv8Arm.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libcxx] Move Linaro 32 bit armv bots to buildkite Instead of setting mcpu like the previous bots, set the target triple. Each config builds either Arm only or Thumb only code. This gives us some coverage of thumb specific issues. The new agents on Linaro's side are running on v8 hardware so will report arch "armv8l" just like the v8 bots. (and buildkite can choose any of them for v7/v8 jobs) Reviewed By: #libc, curdeius, Mordante Differential Revision: https://reviews.llvm.org/D98019
2021-03-02 23:07:19 +08:00
check-cxx-cxxabi
;;
armv8-noexceptions)
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Armv8Thumb-noexceptions.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libcxx] Move Linaro 32 bit armv bots to buildkite Instead of setting mcpu like the previous bots, set the target triple. Each config builds either Arm only or Thumb only code. This gives us some coverage of thumb specific issues. The new agents on Linaro's side are running on v8 hardware so will report arch "armv8l" just like the v8 bots. (and buildkite can choose any of them for v7/v8 jobs) Reviewed By: #libc, curdeius, Mordante Differential Revision: https://reviews.llvm.org/D98019
2021-03-02 23:07:19 +08:00
check-cxx-cxxabi
;;
# Armv7 32 bit. One building Arm only one Thumb only code.
armv7)
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Armv7Arm.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libcxx] Move Linaro 32 bit armv bots to buildkite Instead of setting mcpu like the previous bots, set the target triple. Each config builds either Arm only or Thumb only code. This gives us some coverage of thumb specific issues. The new agents on Linaro's side are running on v8 hardware so will report arch "armv8l" just like the v8 bots. (and buildkite can choose any of them for v7/v8 jobs) Reviewed By: #libc, curdeius, Mordante Differential Revision: https://reviews.llvm.org/D98019
2021-03-02 23:07:19 +08:00
check-cxx-cxxabi
;;
armv7-noexceptions)
clean
[libc++] Move additional build bots to the from-scratch config Once all the bots are passing with from-scratch configs, we can attempt to make the from-scratch config the default configuration. Differential Revision: https://reviews.llvm.org/D103417
2021-06-01 00:44:48 +08:00
generate-cmake -C "${MONOREPO_ROOT}/libcxx/cmake/caches/Armv7Thumb-noexceptions.cmake" \
-DLIBCXX_TEST_CONFIG="${MONOREPO_ROOT}/libcxx/test/configs/libcxx-trunk-shared.cfg.in"
[libcxx] Move Linaro 32 bit armv bots to buildkite Instead of setting mcpu like the previous bots, set the target triple. Each config builds either Arm only or Thumb only code. This gives us some coverage of thumb specific issues. The new agents on Linaro's side are running on v8 hardware so will report arch "armv8l" just like the v8 bots. (and buildkite can choose any of them for v7/v8 jobs) Reviewed By: #libc, curdeius, Mordante Differential Revision: https://reviews.llvm.org/D98019
2021-03-02 23:07:19 +08:00
check-cxx-cxxabi
;;
[libcxx] [ci] Add a Windows CI configuration for a statically linked libc++ On Windows, static vs DLL linking affects details in quite a few cases, so it's good to have coverage for both cases. Testing with static linking also increases coverage for a number of cases and individual checks that have had to be waived for the DLL case, and allows testing libc++experimental, increasing the number of test cases actually executed by 180 (176 new tests from libc++experimental and 4 ones that are XFAIL windows-dll). Also drop the "generic-" prefix from these configuration names, as they're perhaps not what the "generic" prefix intended originally in the other generic-posix configurations. Differential Revision: https://reviews.llvm.org/D101565
2021-04-06 05:17:30 +08:00
windows-dll)
[libcxx] [ci] Add a Windows CI buildkite configuration Differential Revision: https://reviews.llvm.org/D99093
2021-03-17 18:10:42 +08:00
clean
# TODO: Currently, building with the experimental library breaks running
# tests (the test linking look for the c++experimental library with the
# wrong name, and the statically linked c++experimental can't be linked
# correctly when libc++ visibility attributes indicate dllimport linkage
# anyway), thus just disable the experimental library. Remove this
# setting when cmake and the test driver does the right thing automatically.
[libcxx] [ci] Add a Windows CI configuration for a statically linked libc++ On Windows, static vs DLL linking affects details in quite a few cases, so it's good to have coverage for both cases. Testing with static linking also increases coverage for a number of cases and individual checks that have had to be waived for the DLL case, and allows testing libc++experimental, increasing the number of test cases actually executed by 180 (176 new tests from libc++experimental and 4 ones that are XFAIL windows-dll). Also drop the "generic-" prefix from these configuration names, as they're perhaps not what the "generic" prefix intended originally in the other generic-posix configurations. Differential Revision: https://reviews.llvm.org/D101565
2021-04-06 05:17:30 +08:00
generate-cmake-libcxx-win -DLIBCXX_ENABLE_EXPERIMENTAL_LIBRARY=OFF
echo "+++ Running the libc++ tests"
${NINJA} -vC "${BUILD_DIR}" check-cxx
;;
windows-static)
clean
generate-cmake-libcxx-win -DLIBCXX_ENABLE_SHARED=OFF
[libcxx] [ci] Add a Windows CI buildkite configuration Differential Revision: https://reviews.llvm.org/D99093
2021-03-17 18:10:42 +08:00
echo "+++ Running the libc++ tests"
${NINJA} -vC "${BUILD_DIR}" check-cxx
;;
[libc++] NFC: Make it easier for vendors to extend the run-buildbot script
2021-05-28 04:51:38 +08:00
#################################################################
# Insert vendor-specific internal configurations below.
#
# This allows vendors to extend this file with their own internal
# configurations without running into merge conflicts with upstream.
#################################################################
#################################################################
[libc++] Initial support for pre-commit CI with Buildkite This commit adds basic files and scripts that are used for the Buildkite pre-commit CI setup. This was tested to mostly work on a fork of llvm-project, however some adjustments will have to be made as we complete the real setup.
2020-09-23 21:20:03 +08:00
*)
echo "${BUILDER} is not a known configuration"
exit 1
;;
esac