# Rust 1.17.0 prerelease testing **URL:** \ **Category:** announcements\ **Created:** [April 25, 2017, 4:43pm UTC](https://internals.rust-lang.org/t/rust-1-17-0-prerelease-testing/5142 "2017-04-25T16:43:39Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![alexcrichton](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/alexcrichton/32/4501_2.png) [@alexcrichton](https://internals.rust-lang.org/u/alexcrichton)\ **Post date:** [April 25, 2017, 4:43pm UTC](https://internals.rust-lang.org/t/rust-1-17-0-prerelease-testing/5142/1 "2017-04-25T16:43:39Z")
It’s that time of the … every 6 weeks … again! Rust 1.17 is released on Thursday and builds are available now for testing. This is our first stable release produced from Travis and AppVeyor so although we’ve all been testing nightly/beta for 6 weeks (right? right?) it’s good to keep a sharp eye out for any regressions! Release artifacts are uploaded to _dev_ ([dev-static.rust-lang.org](http://dev-static.rust-lang.org)) currently and will be promoted to prod ([static.rust-lang.org](http://static.rust-lang.org)) this Thursday. The URL is [https://dev-static.rust-lang.org/dist/2017-04-25/](https://dev-static.rust-lang.org/dist/2017-04-25/) You can test rustup with ```bash RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup update stable ``` Please let us know if you run into any issues! Pending any detected regressions these are likely to be the exact artifacts that we’ll release on Thursday. ---
**Author:** ![alexcrichton](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/alexcrichton/32/4501_2.png) [@alexcrichton](https://internals.rust-lang.org/u/alexcrichton)\ **Post date:** [April 25, 2017, 4:44pm UTC](https://internals.rust-lang.org/t/rust-1-17-0-prerelease-testing/5142/2 "2017-04-25T16:44:24Z")
Oh I forgot to mention, but once you’re done testing you can go back to the normal stable channel on rustup with: ```rust rustup update stable ``` (note the lack of `RUSTUP_DIST_SERVER` environment variable) ---
**Author:** ![cuviper](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/cuviper/32/1897_2.png) [@cuviper](https://internals.rust-lang.org/u/cuviper)\ **Post date:** [April 25, 2017, 4:52pm UTC](https://internals.rust-lang.org/t/rust-1-17-0-prerelease-testing/5142/3 "2017-04-25T16:52:13Z")
Are release notes ready to pore over? ---
**Author:** ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)\ **Post date:** [April 25, 2017, 4:55pm UTC](https://internals.rust-lang.org/t/rust-1-17-0-prerelease-testing/5142/4 "2017-04-25T16:55:29Z")
I will have them sometime today. Sorry for waiting until the last minute. ---
**Author:** ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)\ **Post date:** [April 25, 2017, 5:01pm UTC](https://internals.rust-lang.org/t/rust-1-17-0-prerelease-testing/5142/5 "2017-04-25T17:01:04Z")
I tested x86\_64-unknown-linux-gnu, i686-unknown-linux-gnu, x86\_64-pc-windows-msvc, and the msi’s for i686-pc-windows-msvc and x86\_64-pc-windows-gnu. ---
**Author:** ![brson](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/brson/32/5197_2.png) [@brson](https://internals.rust-lang.org/u/brson)\ **Post date:** [April 26, 2017, 1:05am UTC](https://internals.rust-lang.org/t/rust-1-17-0-prerelease-testing/5142/6 "2017-04-26T01:05:27Z")
[Release notes](https://github.com/rust-lang/rust/pull/41548). ---
**Author:** ![semarie](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/semarie/32/2012_2.png) [@semarie](https://internals.rust-lang.org/u/semarie)\ **Post date:** [April 26, 2017, 9:58am UTC](https://internals.rust-lang.org/t/rust-1-17-0-prerelease-testing/5142/7 "2017-04-26T09:58:02Z")
Currently, I failed to build compiletest out-of-box using rustc-1.17.0. My configuration is a bit particular: it is the package distribution system of OpenBSD. So I first build rustc using 1.16.0 version, and next I rebuild it using itself (using local-rebuild feature). And now when testing the binary, it fails to build compiletest. The compilation of `rustc-1.17.0-src/src/tools/compiletest/src/main.rs` failed due to use of `#![feature(static_in_const)]`. A warning is issued (`this feature has been stable since 1.17.0. Attribute no longer needed`), and warnings are denied. I have locally patched compiletest, but prefer to let know that testsuite isn’t runnable out-of-box in context of local-rebuild. ---
**Author:** ![alexcrichton](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/alexcrichton/32/4501_2.png) [@alexcrichton](https://internals.rust-lang.org/u/alexcrichton)\ **Post date:** [April 26, 2017, 2:31pm UTC](https://internals.rust-lang.org/t/rust-1-17-0-prerelease-testing/5142/8 "2017-04-26T14:31:22Z")
I believe tools like compiletest expect themselves to be compiled with the stage0 compiler, running tests and such with `local-rebuild` likely has bugs like this with it. ---
**Author:** ![alexcrichton](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/alexcrichton/32/4501_2.png) [@alexcrichton](https://internals.rust-lang.org/u/alexcrichton)\ **Post date:** [March 25, 2019, 8:28am UTC](https://internals.rust-lang.org/t/rust-1-17-0-prerelease-testing/5142/9 "2019-03-25T08:28:26Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.