Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

travis: Update pinned dependancies #157

Merged
merged 3 commits into from
Sep 8, 2020
Merged

Conversation

josephlr
Copy link
Member

@josephlr josephlr commented Sep 8, 2020

Also, pin the version of rustc, so that nightly updates don't break
our build. This means that we can add the nightlies back into the
blocking set of tests.

Move cloudabi to cargo xbuild as it is now a Teir 3 target

Disable Firefox testing due to rustwasm/wasm-bindgen#2261

Signed-off-by: Joe Richey [email protected]

Also, pin the version of rustc, so that nightly updates don't break
our build. This means that we can add the nightlies back into the
blocking set of tests.

Update the Ubuntu version to 20.04
Don't run any cargo-web tests (upstream is broken)

Signed-off-by: Joe Richey <[email protected]>
josephlr added a commit to josephlr/getrandom that referenced this pull request Sep 8, 2020
josephlr added a commit to josephlr/getrandom that referenced this pull request Sep 8, 2020
josephlr added a commit to josephlr/getrandom that referenced this pull request Sep 8, 2020
josephlr added a commit to josephlr/getrandom that referenced this pull request Sep 8, 2020
Cloud ABI [is now Tier 3](rust-lang/rust#75568),
so its libstd is no longer distributed with Rust.

Firefox testing is also disabled due to:
  rustwasm/wasm-bindgen#2261

Signed-off-by: Joe Richey <[email protected]>
josephlr added a commit that referenced this pull request Sep 8, 2020
.travis.yml Outdated
@@ -88,7 +91,7 @@ matrix:
- RUSTFLAGS='-C debuginfo=0' cargo test --target asmjs-unknown-emscripten

- name: "Linux, nightly, docs"
rust: nightly
rust: nightly-2020-09-08
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure if it's a good idea to pin Nightly. Even if in future some change will break our build, I think it's better to find about it sooner than later.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you want to mark all of the nightly builds as non-blocking then? We use nightly for:

  • a Linux build
  • a Mac build
  • cross compiling
  • All of our WASM targets

Copy link
Member Author

@josephlr josephlr Sep 8, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I generally agree with this point though. I think we should move as much as we can out of the nightly tests into the stable tests. Then, mark all the stable tests as non-blocking.

EDIT: Note that we have blocking beta tests, so we should be able to catch anything super-bad before it hits stable.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we have problems with nightly builds previously? If I had to chose, I would prefer making those jobs non-blocking.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We did, a nightly didn't have some component we needed (rustfmt maybe, but that's already non-blocking).

I agree that we should have them be blocking, should be fixed now.

Copy link
Member

@newpavlov newpavlov Sep 8, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BTW do we have cron jobs enabled in Travis?

cc @dhardy

UPD: It looks we do.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

@newpavlov newpavlov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, but note that I do not have a deep understanding of the WASM part of CI job.

@josephlr josephlr merged commit 7dcb167 into rust-random:master Sep 8, 2020
@josephlr josephlr deleted the ci-master branch September 8, 2020 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants