-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Tests are failing on 1.54.0
stable toolchain
#9627
Comments
Fails on the fresh |
the failing test are UI tests, I think those tests are not relevant for your case, maybe we should introduce a feature to be able not to run them. like feature |
I can add some switches (e.g. add an environment variable to all jobs if a pipeline was triggered from a nightly build), but doing so will branch the project's CI/CD pipeline into two separate entities:
IMO that's pointless. Staging has to be production-like and simulate a production run. If those would differ, the current staging activity (build a staging image and trigger a Substrate's pipeline with it) will make no sense. |
sorry, I missunderstood, I thought we were using 1.54 in CI and you wanted to run test for an old image with 1.53. |
FYI: rust 1.55 is out: https://blog.rust-lang.org/2021/09/09/Rust-1.55.0.html, can we go straight to 1.55? |
Yeah, probably a good idea :D |
Hi!
ci-linux:production
image, which is used in Substrate and related projects pipelines, is stuck withrustc 1.53.0 (53cb7b09b 2021-06-17)
due to failing tests on the recent stable. Here is failing test job example with staging image bundled withrustc 1.54.0 (a178d0322 2021-07-26)
.I'm unable to gracefully promote current staging images into production images. Doing so forcefully will break stuff as in the example above.
The text was updated successfully, but these errors were encountered: