2016-10-07 11:43:26 -05:00
|
|
|
environment:
|
2017-09-14 15:17:25 -05:00
|
|
|
SCCACHE_BUCKET: rust-lang-ci-sccache2
|
|
|
|
|
SCCACHE_REGION: us-west-1
|
2017-09-07 00:47:56 -05:00
|
|
|
AWS_ACCESS_KEY_ID: AKIAJAMV3QAMMA6AXHFQ
|
2016-12-12 13:36:52 -06:00
|
|
|
AWS_SECRET_ACCESS_KEY:
|
2017-09-07 00:47:56 -05:00
|
|
|
secure: 7Y+JiquYedOAgnUU26uL0DPzrxmTtR+qIwG6rNKSuWDffqU3vVZxbGXim9QpTO80
|
2016-12-12 13:36:52 -06:00
|
|
|
SCCACHE_DIGEST: f808afabb4a4eb1d7112bcb3fa6be03b61e93412890c88e177c667eb37f46353d7ec294e559b16f9f4b5e894f2185fe7670a0df15fd064889ecbd80f0c34166c
|
2017-12-04 08:31:57 -06:00
|
|
|
TOOLSTATE_REPO_ACCESS_TOKEN:
|
|
|
|
|
secure: PTZiSxJMVUZ0VnMR5i13E4OagbXfglj7pcskDQiKufVrDm13mLoI0vDJAEM35+bY
|
2017-07-19 07:57:56 -05:00
|
|
|
|
|
|
|
|
# By default schannel checks revocation of certificates unlike some other SSL
|
|
|
|
|
# backends, but we've historically had problems on CI where a revocation
|
|
|
|
|
# server goes down presumably. See #43333 for more info
|
|
|
|
|
CARGO_HTTP_CHECK_REVOKE: false
|
|
|
|
|
|
2016-10-07 11:43:26 -05:00
|
|
|
matrix:
|
2017-02-15 11:36:52 -06:00
|
|
|
# 32/64 bit MSVC tests
|
2016-10-07 11:43:26 -05:00
|
|
|
- MSYS_BITS: 64
|
2017-06-06 12:09:33 -05:00
|
|
|
RUST_CONFIGURE_ARGS: --build=x86_64-pc-windows-msvc --enable-profiler
|
2017-02-15 11:36:52 -06:00
|
|
|
SCRIPT: python x.py test
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: x86_64-msvc
|
2016-10-07 11:43:26 -05:00
|
|
|
- MSYS_BITS: 32
|
2018-03-06 21:19:56 -06:00
|
|
|
RUST_CONFIGURE_ARGS: --build=i686-pc-windows-msvc
|
2018-03-24 15:44:28 -05:00
|
|
|
SCRIPT: make appveyor-subset-1
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: i686-msvc-1
|
2018-03-06 21:19:56 -06:00
|
|
|
- MSYS_BITS: 32
|
|
|
|
|
RUST_CONFIGURE_ARGS: --build=i686-pc-windows-msvc
|
2018-03-24 15:44:28 -05:00
|
|
|
SCRIPT: make appveyor-subset-2
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: i686-msvc-2
|
2016-10-07 11:43:26 -05:00
|
|
|
|
2017-02-15 11:36:52 -06:00
|
|
|
# MSVC aux tests
|
2016-10-07 11:43:26 -05:00
|
|
|
- MSYS_BITS: 64
|
2018-03-07 15:57:17 -06:00
|
|
|
RUST_CHECK_TARGET: check-aux EXCLUDE_CARGO=1
|
2018-03-06 21:19:56 -06:00
|
|
|
RUST_CONFIGURE_ARGS: --build=x86_64-pc-windows-msvc
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: x86_64-msvc-aux
|
2018-03-06 21:19:56 -06:00
|
|
|
- MSYS_BITS: 64
|
|
|
|
|
SCRIPT: python x.py test src/tools/cargotest src/tools/cargo
|
2016-11-16 14:31:19 -06:00
|
|
|
RUST_CONFIGURE_ARGS: --build=x86_64-pc-windows-msvc
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: x86_64-msvc-cargo
|
2016-10-07 11:43:26 -05:00
|
|
|
|
2017-11-28 09:19:54 -06:00
|
|
|
# MSVC tools tests
|
2017-09-15 13:31:48 -05:00
|
|
|
- MSYS_BITS: 64
|
2017-12-04 08:31:57 -06:00
|
|
|
SCRIPT: src/ci/docker/x86_64-gnu-tools/checktools.sh x.py /tmp/toolstates.json windows
|
|
|
|
|
RUST_CONFIGURE_ARGS: --build=x86_64-pc-windows-msvc --save-toolstates=/tmp/toolstates.json --enable-test-miri
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: x86_64-msvc-tools
|
2017-09-15 13:31:48 -05:00
|
|
|
|
2016-10-07 11:43:26 -05:00
|
|
|
# 32/64-bit MinGW builds.
|
|
|
|
|
#
|
2017-04-14 04:27:35 -05:00
|
|
|
# We are using MinGW with posix threads since LLVM does not compile with
|
|
|
|
|
# the win32 threads version due to missing support for C++'s std::thread.
|
2016-10-07 11:43:26 -05:00
|
|
|
#
|
2017-04-14 04:27:35 -05:00
|
|
|
# Instead of relying on the MinGW version installed on appveryor we download
|
|
|
|
|
# and install one ourselves so we won't be surprised by changes to appveyor's
|
|
|
|
|
# build image.
|
2016-10-07 11:43:26 -05:00
|
|
|
#
|
|
|
|
|
# Finally, note that the downloads below are all in the `rust-lang-ci` S3
|
|
|
|
|
# bucket, but they cleraly didn't originate there! The downloads originally
|
|
|
|
|
# came from the mingw-w64 SourceForge download site. Unfortunately
|
|
|
|
|
# SourceForge is notoriously flaky, so we mirror it on our own infrastructure.
|
2017-02-15 11:36:52 -06:00
|
|
|
- MSYS_BITS: 32
|
2017-02-25 11:53:46 -06:00
|
|
|
RUST_CONFIGURE_ARGS: --build=i686-pc-windows-gnu
|
2018-03-24 15:44:28 -05:00
|
|
|
SCRIPT: make appveyor-subset-1
|
2018-02-23 17:19:17 -06:00
|
|
|
MINGW_URL: https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror
|
|
|
|
|
MINGW_ARCHIVE: i686-6.3.0-release-posix-dwarf-rt_v5-rev2.7z
|
|
|
|
|
MINGW_DIR: mingw32
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: i686-mingw-1
|
2018-02-23 17:19:17 -06:00
|
|
|
- MSYS_BITS: 32
|
|
|
|
|
RUST_CONFIGURE_ARGS: --build=i686-pc-windows-gnu
|
2018-03-24 15:44:28 -05:00
|
|
|
SCRIPT: make appveyor-subset-2
|
2017-09-15 18:04:13 -05:00
|
|
|
MINGW_URL: https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror
|
2017-04-20 10:35:03 -05:00
|
|
|
MINGW_ARCHIVE: i686-6.3.0-release-posix-dwarf-rt_v5-rev2.7z
|
2017-02-15 11:36:52 -06:00
|
|
|
MINGW_DIR: mingw32
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: i686-mingw-2
|
2017-02-15 11:36:52 -06:00
|
|
|
- MSYS_BITS: 64
|
|
|
|
|
SCRIPT: python x.py test
|
2017-02-25 11:53:46 -06:00
|
|
|
RUST_CONFIGURE_ARGS: --build=x86_64-pc-windows-gnu
|
2017-09-15 18:04:13 -05:00
|
|
|
MINGW_URL: https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror
|
2017-04-20 10:35:03 -05:00
|
|
|
MINGW_ARCHIVE: x86_64-6.3.0-release-posix-seh-rt_v5-rev2.7z
|
2017-02-15 11:36:52 -06:00
|
|
|
MINGW_DIR: mingw64
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: x86_64-mingw
|
2017-02-15 11:36:52 -06:00
|
|
|
|
|
|
|
|
# 32/64 bit MSVC and GNU deployment
|
|
|
|
|
- RUST_CONFIGURE_ARGS: >
|
|
|
|
|
--build=x86_64-pc-windows-msvc
|
rust: Import LLD for linking wasm objects
This commit imports the LLD project from LLVM to serve as the default linker for
the `wasm32-unknown-unknown` target. The `binaryen` submoule is consequently
removed along with "binaryen linker" support in rustc.
Moving to LLD brings with it a number of benefits for wasm code:
* LLD is itself an actual linker, so there's no need to compile all wasm code
with LTO any more. As a result builds should be *much* speedier as LTO is no
longer forcibly enabled for all builds of the wasm target.
* LLD is quickly becoming an "official solution" for linking wasm code together.
This, I believe at least, is intended to be the main supported linker for
native code and wasm moving forward. Picking up support early on should help
ensure that we can help LLD identify bugs and otherwise prove that it works
great for all our use cases!
* Improvements to the wasm toolchain are currently primarily focused around LLVM
and LLD (from what I can tell at least), so it's in general much better to be
on this bandwagon for bugfixes and new features.
* Historical "hacks" like `wasm-gc` will soon no longer be necessary, LLD
will [natively implement][gc] `--gc-sections` (better than `wasm-gc`!) which
means a postprocessor is no longer needed to show off Rust's "small wasm
binary size".
LLD is added in a pretty standard way to rustc right now. A new rustbuild target
was defined for building LLD, and this is executed when a compiler's sysroot is
being assembled. LLD is compiled against the LLVM that we've got in tree, which
means we're currently on the `release_60` branch, but this may get upgraded in
the near future!
LLD is placed into rustc's sysroot in a `bin` directory. This is similar to
where `gcc.exe` can be found on Windows. This directory is automatically added
to `PATH` whenever rustc executes the linker, allowing us to define a `WasmLd`
linker which implements the interface that `wasm-ld`, LLD's frontend, expects.
Like Emscripten the LLD target is currently only enabled for Tier 1 platforms,
notably OSX/Windows/Linux, and will need to be installed manually for compiling
to wasm on other platforms. LLD is by default turned off in rustbuild, and
requires a `config.toml` option to be enabled to turn it on.
Finally the unstable `#![wasm_import_memory]` attribute was also removed as LLD
has a native option for controlling this.
[gc]: https://reviews.llvm.org/D42511
2017-08-26 20:30:12 -05:00
|
|
|
--enable-full-tools
|
2017-06-06 12:09:33 -05:00
|
|
|
--enable-profiler
|
2017-02-15 11:36:52 -06:00
|
|
|
SCRIPT: python x.py dist
|
|
|
|
|
DEPLOY: 1
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: dist-x86_64-msvc
|
2017-02-15 11:36:52 -06:00
|
|
|
- RUST_CONFIGURE_ARGS: >
|
|
|
|
|
--build=i686-pc-windows-msvc
|
|
|
|
|
--target=i586-pc-windows-msvc
|
rust: Import LLD for linking wasm objects
This commit imports the LLD project from LLVM to serve as the default linker for
the `wasm32-unknown-unknown` target. The `binaryen` submoule is consequently
removed along with "binaryen linker" support in rustc.
Moving to LLD brings with it a number of benefits for wasm code:
* LLD is itself an actual linker, so there's no need to compile all wasm code
with LTO any more. As a result builds should be *much* speedier as LTO is no
longer forcibly enabled for all builds of the wasm target.
* LLD is quickly becoming an "official solution" for linking wasm code together.
This, I believe at least, is intended to be the main supported linker for
native code and wasm moving forward. Picking up support early on should help
ensure that we can help LLD identify bugs and otherwise prove that it works
great for all our use cases!
* Improvements to the wasm toolchain are currently primarily focused around LLVM
and LLD (from what I can tell at least), so it's in general much better to be
on this bandwagon for bugfixes and new features.
* Historical "hacks" like `wasm-gc` will soon no longer be necessary, LLD
will [natively implement][gc] `--gc-sections` (better than `wasm-gc`!) which
means a postprocessor is no longer needed to show off Rust's "small wasm
binary size".
LLD is added in a pretty standard way to rustc right now. A new rustbuild target
was defined for building LLD, and this is executed when a compiler's sysroot is
being assembled. LLD is compiled against the LLVM that we've got in tree, which
means we're currently on the `release_60` branch, but this may get upgraded in
the near future!
LLD is placed into rustc's sysroot in a `bin` directory. This is similar to
where `gcc.exe` can be found on Windows. This directory is automatically added
to `PATH` whenever rustc executes the linker, allowing us to define a `WasmLd`
linker which implements the interface that `wasm-ld`, LLD's frontend, expects.
Like Emscripten the LLD target is currently only enabled for Tier 1 platforms,
notably OSX/Windows/Linux, and will need to be installed manually for compiling
to wasm on other platforms. LLD is by default turned off in rustbuild, and
requires a `config.toml` option to be enabled to turn it on.
Finally the unstable `#![wasm_import_memory]` attribute was also removed as LLD
has a native option for controlling this.
[gc]: https://reviews.llvm.org/D42511
2017-08-26 20:30:12 -05:00
|
|
|
--enable-full-tools
|
2017-06-06 12:09:33 -05:00
|
|
|
--enable-profiler
|
2017-02-15 11:36:52 -06:00
|
|
|
SCRIPT: python x.py dist
|
|
|
|
|
DEPLOY: 1
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: dist-i686-msvc
|
2016-10-07 11:43:26 -05:00
|
|
|
- MSYS_BITS: 32
|
rust: Import LLD for linking wasm objects
This commit imports the LLD project from LLVM to serve as the default linker for
the `wasm32-unknown-unknown` target. The `binaryen` submoule is consequently
removed along with "binaryen linker" support in rustc.
Moving to LLD brings with it a number of benefits for wasm code:
* LLD is itself an actual linker, so there's no need to compile all wasm code
with LTO any more. As a result builds should be *much* speedier as LTO is no
longer forcibly enabled for all builds of the wasm target.
* LLD is quickly becoming an "official solution" for linking wasm code together.
This, I believe at least, is intended to be the main supported linker for
native code and wasm moving forward. Picking up support early on should help
ensure that we can help LLD identify bugs and otherwise prove that it works
great for all our use cases!
* Improvements to the wasm toolchain are currently primarily focused around LLVM
and LLD (from what I can tell at least), so it's in general much better to be
on this bandwagon for bugfixes and new features.
* Historical "hacks" like `wasm-gc` will soon no longer be necessary, LLD
will [natively implement][gc] `--gc-sections` (better than `wasm-gc`!) which
means a postprocessor is no longer needed to show off Rust's "small wasm
binary size".
LLD is added in a pretty standard way to rustc right now. A new rustbuild target
was defined for building LLD, and this is executed when a compiler's sysroot is
being assembled. LLD is compiled against the LLVM that we've got in tree, which
means we're currently on the `release_60` branch, but this may get upgraded in
the near future!
LLD is placed into rustc's sysroot in a `bin` directory. This is similar to
where `gcc.exe` can be found on Windows. This directory is automatically added
to `PATH` whenever rustc executes the linker, allowing us to define a `WasmLd`
linker which implements the interface that `wasm-ld`, LLD's frontend, expects.
Like Emscripten the LLD target is currently only enabled for Tier 1 platforms,
notably OSX/Windows/Linux, and will need to be installed manually for compiling
to wasm on other platforms. LLD is by default turned off in rustbuild, and
requires a `config.toml` option to be enabled to turn it on.
Finally the unstable `#![wasm_import_memory]` attribute was also removed as LLD
has a native option for controlling this.
[gc]: https://reviews.llvm.org/D42511
2017-08-26 20:30:12 -05:00
|
|
|
RUST_CONFIGURE_ARGS: --build=i686-pc-windows-gnu --enable-full-tools
|
2017-02-15 11:36:52 -06:00
|
|
|
SCRIPT: python x.py dist
|
2017-09-15 18:04:13 -05:00
|
|
|
MINGW_URL: https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror
|
2017-04-20 10:35:03 -05:00
|
|
|
MINGW_ARCHIVE: i686-6.3.0-release-posix-dwarf-rt_v5-rev2.7z
|
2016-10-07 11:43:26 -05:00
|
|
|
MINGW_DIR: mingw32
|
2016-12-31 19:42:40 -06:00
|
|
|
DEPLOY: 1
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: dist-i686-mingw
|
2016-10-07 11:43:26 -05:00
|
|
|
- MSYS_BITS: 64
|
2017-02-15 11:36:52 -06:00
|
|
|
SCRIPT: python x.py dist
|
rust: Import LLD for linking wasm objects
This commit imports the LLD project from LLVM to serve as the default linker for
the `wasm32-unknown-unknown` target. The `binaryen` submoule is consequently
removed along with "binaryen linker" support in rustc.
Moving to LLD brings with it a number of benefits for wasm code:
* LLD is itself an actual linker, so there's no need to compile all wasm code
with LTO any more. As a result builds should be *much* speedier as LTO is no
longer forcibly enabled for all builds of the wasm target.
* LLD is quickly becoming an "official solution" for linking wasm code together.
This, I believe at least, is intended to be the main supported linker for
native code and wasm moving forward. Picking up support early on should help
ensure that we can help LLD identify bugs and otherwise prove that it works
great for all our use cases!
* Improvements to the wasm toolchain are currently primarily focused around LLVM
and LLD (from what I can tell at least), so it's in general much better to be
on this bandwagon for bugfixes and new features.
* Historical "hacks" like `wasm-gc` will soon no longer be necessary, LLD
will [natively implement][gc] `--gc-sections` (better than `wasm-gc`!) which
means a postprocessor is no longer needed to show off Rust's "small wasm
binary size".
LLD is added in a pretty standard way to rustc right now. A new rustbuild target
was defined for building LLD, and this is executed when a compiler's sysroot is
being assembled. LLD is compiled against the LLVM that we've got in tree, which
means we're currently on the `release_60` branch, but this may get upgraded in
the near future!
LLD is placed into rustc's sysroot in a `bin` directory. This is similar to
where `gcc.exe` can be found on Windows. This directory is automatically added
to `PATH` whenever rustc executes the linker, allowing us to define a `WasmLd`
linker which implements the interface that `wasm-ld`, LLD's frontend, expects.
Like Emscripten the LLD target is currently only enabled for Tier 1 platforms,
notably OSX/Windows/Linux, and will need to be installed manually for compiling
to wasm on other platforms. LLD is by default turned off in rustbuild, and
requires a `config.toml` option to be enabled to turn it on.
Finally the unstable `#![wasm_import_memory]` attribute was also removed as LLD
has a native option for controlling this.
[gc]: https://reviews.llvm.org/D42511
2017-08-26 20:30:12 -05:00
|
|
|
RUST_CONFIGURE_ARGS: --build=x86_64-pc-windows-gnu --enable-full-tools
|
2017-09-15 18:04:13 -05:00
|
|
|
MINGW_URL: https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror
|
2017-04-20 10:35:03 -05:00
|
|
|
MINGW_ARCHIVE: x86_64-6.3.0-release-posix-seh-rt_v5-rev2.7z
|
2016-10-07 11:43:26 -05:00
|
|
|
MINGW_DIR: mingw64
|
2016-12-31 19:42:40 -06:00
|
|
|
DEPLOY: 1
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: dist-x86_64-mingw
|
2016-10-07 11:43:26 -05:00
|
|
|
|
2017-02-11 19:28:29 -06:00
|
|
|
# "alternate" deployment, see .travis.yml for more info
|
|
|
|
|
- MSYS_BITS: 64
|
2017-07-11 07:01:04 -05:00
|
|
|
RUST_CONFIGURE_ARGS: --build=x86_64-pc-windows-msvc --enable-extended --enable-profiler
|
2017-02-11 19:28:29 -06:00
|
|
|
SCRIPT: python x.py dist
|
|
|
|
|
DEPLOY_ALT: 1
|
2018-04-05 12:09:59 -05:00
|
|
|
CI_JOB_NAME: dist-x86_64-msvc-alt
|
2017-02-11 19:28:29 -06:00
|
|
|
|
2017-01-19 19:18:12 -06:00
|
|
|
matrix:
|
|
|
|
|
fast_finish: true
|
|
|
|
|
|
2017-12-29 10:05:15 -06:00
|
|
|
clone_depth: 2
|
2016-10-07 11:43:26 -05:00
|
|
|
build: false
|
|
|
|
|
|
|
|
|
|
install:
|
|
|
|
|
# If we need to download a custom MinGW, do so here and set the path
|
|
|
|
|
# appropriately.
|
|
|
|
|
#
|
|
|
|
|
# Note that this *also* means that we're not using what is typically
|
|
|
|
|
# /mingw32/bin/python2.7.exe, which is a "correct" python interpreter where
|
|
|
|
|
# /usr/bin/python2.7.exe is not. To ensure we use the right interpreter we
|
|
|
|
|
# move `C:\Python27` ahead in PATH and then also make sure the `python2.7.exe`
|
|
|
|
|
# file exists in there (which it doesn't by default).
|
2017-02-25 02:00:47 -06:00
|
|
|
- if defined MINGW_URL appveyor-retry appveyor DownloadFile %MINGW_URL%/%MINGW_ARCHIVE%
|
2016-10-07 11:43:26 -05:00
|
|
|
- if defined MINGW_URL 7z x -y %MINGW_ARCHIVE% > nul
|
2017-02-15 11:36:52 -06:00
|
|
|
- if defined MINGW_URL set PATH=%CD%\%MINGW_DIR%\bin;C:\msys64\usr\bin;%PATH%
|
2016-10-07 11:43:26 -05:00
|
|
|
|
2018-04-24 10:34:14 -05:00
|
|
|
# If we're compiling for MSVC then we, like most other distribution builders,
|
|
|
|
|
# switch to clang as the compiler. This'll allow us eventually to enable LTO
|
|
|
|
|
# amongst LLVM and rustc. Note that we only do this on MSVC as I don't think
|
|
|
|
|
# clang has an output mode compatible with MinGW that we need. If it does we
|
|
|
|
|
# should switch to clang for MinGW as well!
|
|
|
|
|
#
|
|
|
|
|
# Note that the LLVM installer is an NSIS installer
|
|
|
|
|
#
|
|
|
|
|
# Original downloaded here came from
|
|
|
|
|
# http://releases.llvm.org/6.0.0/LLVM-6.0.0-win64.exe
|
|
|
|
|
- if NOT defined MINGW_URL appveyor-retry appveyor DownloadFile https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror/LLVM-6.0.0-win64.exe
|
|
|
|
|
- if NOT defined MINGW_URL .\LLVM-6.0.0-win64.exe /S /NCRC /D=C:\clang-rust
|
|
|
|
|
- if NOT defined MINGW_URL set RUST_CONFIGURE_ARGS=%RUST_CONFIGURE_ARGS% --set llvm.clang-cl=C:\clang-rust\bin\clang-cl.exe
|
|
|
|
|
|
2017-04-20 10:35:03 -05:00
|
|
|
# Here we do a pretty heinous thing which is to mangle the MinGW installation
|
|
|
|
|
# we just had above. Currently, as of this writing, we're using MinGW-w64
|
|
|
|
|
# builds of gcc, and that's currently at 6.3.0. We use 6.3.0 as it appears to
|
|
|
|
|
# be the first version which contains a fix for #40546, builds randomly
|
|
|
|
|
# failing during LLVM due to ar.exe/ranlib.exe failures.
|
|
|
|
|
#
|
|
|
|
|
# Unfortunately, though, 6.3.0 *also* is the first version of MinGW-w64 builds
|
|
|
|
|
# to contain a regression in gdb (#40184). As a result if we were to use the
|
|
|
|
|
# gdb provided (7.11.1) then we would fail all debuginfo tests.
|
|
|
|
|
#
|
|
|
|
|
# In order to fix spurious failures (pretty high priority) we use 6.3.0. To
|
|
|
|
|
# avoid disabling gdb tests we download an *old* version of gdb, specifically
|
|
|
|
|
# that found inside the 6.2.0 distribution. We then overwrite the 6.3.0 gdb
|
|
|
|
|
# with the 6.2.0 gdb to get tests passing.
|
|
|
|
|
#
|
|
|
|
|
# Note that we don't literally overwrite the gdb.exe binary because it appears
|
|
|
|
|
# to just use gdborig.exe, so that's the binary we deal with instead.
|
|
|
|
|
- if defined MINGW_URL appveyor-retry appveyor DownloadFile %MINGW_URL%/2017-04-20-%MSYS_BITS%bit-gdborig.exe
|
|
|
|
|
- if defined MINGW_URL mv 2017-04-20-%MSYS_BITS%bit-gdborig.exe %MINGW_DIR%\bin\gdborig.exe
|
|
|
|
|
|
2016-10-07 11:43:26 -05:00
|
|
|
# Otherwise pull in the MinGW installed on appveyor
|
|
|
|
|
- if NOT defined MINGW_URL set PATH=C:\msys64\mingw%MSYS_BITS%\bin;C:\msys64\usr\bin;%PATH%
|
|
|
|
|
|
2017-02-15 11:36:52 -06:00
|
|
|
# Prefer the "native" Python as LLVM has trouble building with MSYS sometimes
|
|
|
|
|
- copy C:\Python27\python.exe C:\Python27\python2.7.exe
|
|
|
|
|
- set PATH=C:\Python27;%PATH%
|
|
|
|
|
|
2016-12-12 13:36:52 -06:00
|
|
|
# Download and install sccache
|
2018-04-24 10:34:14 -05:00
|
|
|
- appveyor-retry appveyor DownloadFile https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror/2018-04-26-sccache-x86_64-pc-windows-msvc
|
|
|
|
|
- mv 2018-04-26-sccache-x86_64-pc-windows-msvc sccache.exe
|
2017-02-24 15:16:54 -06:00
|
|
|
- set PATH=%PATH%;%CD%
|
2016-12-12 13:36:52 -06:00
|
|
|
|
2017-03-15 09:35:35 -05:00
|
|
|
# Download and install ninja
|
|
|
|
|
#
|
|
|
|
|
# Note that this is originally from the github releases patch of Ninja
|
2017-09-15 18:04:13 -05:00
|
|
|
- appveyor-retry appveyor DownloadFile https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror/2017-03-15-ninja-win.zip
|
2017-03-15 09:35:35 -05:00
|
|
|
- 7z x 2017-03-15-ninja-win.zip
|
2017-02-25 11:53:46 -06:00
|
|
|
- set RUST_CONFIGURE_ARGS=%RUST_CONFIGURE_ARGS% --enable-ninja
|
2017-03-15 09:35:35 -05:00
|
|
|
# - set PATH=%PATH%;%CD% -- this already happens above for sccache
|
|
|
|
|
|
2017-01-20 19:03:06 -06:00
|
|
|
# Install InnoSetup to get `iscc` used to produce installers
|
2017-09-15 18:04:13 -05:00
|
|
|
- appveyor-retry appveyor DownloadFile https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror/2017-08-22-is.exe
|
2017-08-22 21:42:28 -05:00
|
|
|
- 2017-08-22-is.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-
|
2017-01-20 19:03:06 -06:00
|
|
|
- set PATH="C:\Program Files (x86)\Inno Setup 5";%PATH%
|
|
|
|
|
|
2016-12-29 17:58:57 -06:00
|
|
|
# Help debug some handle issues on AppVeyor
|
2017-09-15 18:04:13 -05:00
|
|
|
- appveyor-retry appveyor DownloadFile https://s3-us-west-1.amazonaws.com/rust-lang-ci2/rust-ci-mirror/2017-05-15-Handle.zip
|
2016-12-29 17:58:57 -06:00
|
|
|
- mkdir handle
|
2017-05-14 14:41:42 -05:00
|
|
|
- 7z x -ohandle 2017-05-15-Handle.zip
|
2016-12-29 17:58:57 -06:00
|
|
|
- set PATH=%PATH%;%CD%\handle
|
|
|
|
|
- handle.exe -accepteula -help
|
|
|
|
|
|
2016-10-07 11:43:26 -05:00
|
|
|
test_script:
|
2017-04-04 16:51:16 -05:00
|
|
|
- if not exist C:\cache\rustsrc\NUL mkdir C:\cache\rustsrc
|
|
|
|
|
- sh src/ci/init_repo.sh . /c/cache/rustsrc
|
2016-11-16 14:31:19 -06:00
|
|
|
- set SRC=.
|
|
|
|
|
- set NO_CCACHE=1
|
|
|
|
|
- sh src/ci/run.sh
|
2016-10-07 11:43:26 -05:00
|
|
|
|
2018-05-10 23:30:50 -05:00
|
|
|
on_failure:
|
|
|
|
|
# Dump crash log
|
|
|
|
|
- set PATH=%PATH%;"C:\Program Files (x86)\Windows Kits\10\Debuggers\X64"
|
|
|
|
|
- if exist %LOCALAPPDATA%\CrashDumps for %%f in (%LOCALAPPDATA%\CrashDumps\*) do cdb -c "k;q" -G -z "%%f"
|
|
|
|
|
|
2016-10-07 11:43:26 -05:00
|
|
|
branches:
|
|
|
|
|
only:
|
|
|
|
|
- auto
|
|
|
|
|
|
2016-12-31 19:42:40 -06:00
|
|
|
before_deploy:
|
|
|
|
|
- ps: |
|
|
|
|
|
New-Item -Path deploy -ItemType directory
|
2017-01-28 12:24:42 -06:00
|
|
|
Remove-Item -Recurse -Force build\dist\doc
|
2017-01-25 13:55:30 -06:00
|
|
|
Get-ChildItem -Path build\dist | Move-Item -Destination deploy
|
2016-12-31 19:42:40 -06:00
|
|
|
Get-ChildItem -Path deploy | Foreach-Object {
|
|
|
|
|
Push-AppveyorArtifact $_.FullName -FileName ${env:APPVEYOR_REPO_COMMIT}/$_
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
deploy:
|
|
|
|
|
- provider: S3
|
|
|
|
|
skip_cleanup: true
|
2017-09-07 00:47:56 -05:00
|
|
|
access_key_id: AKIAJVBODR3IA4O72THQ
|
2016-12-31 19:42:40 -06:00
|
|
|
secret_access_key:
|
2017-09-07 00:47:56 -05:00
|
|
|
secure: tQWIE+DJHjXaV4np/3YeETkEmXngtIuIgAO/LYKQaUshGLgN8cBCFGG3cHx5lKLt
|
2017-09-15 18:04:13 -05:00
|
|
|
bucket: rust-lang-ci2
|
2016-12-31 19:42:40 -06:00
|
|
|
set_public: true
|
2017-09-15 18:04:13 -05:00
|
|
|
region: us-west-1
|
2017-01-25 13:55:30 -06:00
|
|
|
artifact: /.*/
|
2016-12-31 19:42:40 -06:00
|
|
|
folder: rustc-builds
|
|
|
|
|
on:
|
|
|
|
|
branch: auto
|
|
|
|
|
DEPLOY: 1
|
2017-03-23 09:07:02 -05:00
|
|
|
max_error_retry: 5
|
2016-12-31 19:42:40 -06:00
|
|
|
|
2017-02-11 19:28:29 -06:00
|
|
|
# This provider is the same as the one above except that it has a slightly
|
|
|
|
|
# different upload directory and a slightly different trigger
|
|
|
|
|
- provider: S3
|
|
|
|
|
skip_cleanup: true
|
2017-09-07 00:47:56 -05:00
|
|
|
access_key_id: AKIAJVBODR3IA4O72THQ
|
2017-02-11 19:28:29 -06:00
|
|
|
secret_access_key:
|
2017-09-07 00:47:56 -05:00
|
|
|
secure: tQWIE+DJHjXaV4np/3YeETkEmXngtIuIgAO/LYKQaUshGLgN8cBCFGG3cHx5lKLt
|
2017-09-15 18:04:13 -05:00
|
|
|
bucket: rust-lang-ci2
|
2017-02-11 19:28:29 -06:00
|
|
|
set_public: true
|
2017-09-15 18:04:13 -05:00
|
|
|
region: us-west-1
|
2017-02-11 19:28:29 -06:00
|
|
|
artifact: /.*/
|
|
|
|
|
folder: rustc-builds-alt
|
|
|
|
|
on:
|
|
|
|
|
branch: auto
|
|
|
|
|
DEPLOY_ALT: 1
|
2017-03-23 09:07:02 -05:00
|
|
|
max_error_retry: 5
|
2017-02-11 19:28:29 -06:00
|
|
|
|
2016-10-07 11:43:26 -05:00
|
|
|
# init:
|
|
|
|
|
# - ps: iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/enable-rdp.ps1'))
|
|
|
|
|
# on_finish:
|
|
|
|
|
# - ps: $blockRdp = $true; iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/enable-rdp.ps1'))
|
