Skip to content

MacOS beta missing #52686

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

Closed
durka opened this issue Jul 25, 2018 · 11 comments
Closed

MacOS beta missing #52686

durka opened this issue Jul 25, 2018 · 11 comments
Labels
O-macos Operating system: macOS P-high High priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@durka
Copy link
Contributor

durka commented Jul 25, 2018

Rustup reports that all of the components are discontinued when trying to update beta. Nightly updates successfully. This doesn't appear to happen on Linux either.

$ rustup update beta
info: syncing channel updates for 'beta-x86_64-apple-darwin'
info: latest update on 2018-07-25, rust version 1.28.0-beta.14 (0aaa819fe 2018-07-24)
warning: component 'rustc' is not available anymore on target 'x86_64-apple-darwin'
warning: component 'rust-std' is not available anymore on target 'x86_64-apple-darwin'
warning: component 'cargo' is not available anymore on target 'x86_64-apple-darwin'
warning: component 'rust-docs' is not available anymore on target 'x86_64-apple-darwin'
warning: component 'rust-src' is not available anymore
warning: component 'rustfmt-preview' is not available anymore on target 'x86_64-apple-darwin'
warning: component 'rust-std' is not available anymore on target 'wasm32-unknown-emscripten'
warning: component 'rust-std' is not available anymore on target 'asmjs-unknown-emscripten'
error: some components unavailable for download: 'rustc', 'cargo'
@pietroalbini pietroalbini added O-macos Operating system: macOS I-nominated P-high High priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Jul 25, 2018
@pietroalbini
Copy link
Member

cc @rust-lang/infra
1.28 will be released in a week.

@pietroalbini
Copy link
Member

Looking at the manifest, these targets have all their components marked as available = false:

Tier 1 platforms (tests guaranteed to pass):

  • x86_64-apple-darwin
  • i686-apple-darwin

Tier 2 platforms (builds guaranteed to be available):

  • aarch64-apple-ios
  • armv7-apple-ios
  • armv7s-apple-ios
  • i386-apple-ios
  • x86_64-apple-ios

So yeah, everything Apple is broken. Build different.

@pietroalbini

This comment has been minimized.

@pietroalbini
Copy link
Member

Builds for Apple platforms seems to be available, so this is probably a bug in the manifest generation.

@alexcrichton
Copy link
Member

Erm... Looking at the Travis build the OSX workers are... just gone!

@alexcrichton
Copy link
Member

This... may be a travis bug? Our Travis configuration for that commit indeed says if: branch = auto but the build logs confirm that it was built on the auto branch...

Er wait, oh dear!

...

Oh dear!

We're not building mac builds any more at all -- https://travis-ci.org/rust-lang/rust/builds/407985371

@cotsog
Copy link

cotsog commented Jul 25, 2018

Hello everyone, I'm a Customer Support Engineer @ Travis CI and I wanted to acknowledge that the issue here is most probably on our end. Our team will be looking into it shortly and hopefully, the Rust Mac beta builds will be available again soon. Thank you for your patience!

@svenfuchs
Copy link

This should now be fixed.

We have recently shipped a new parser for env vars in order to address performance issues with the previous regex based version that did not perform well under very specific conditions.

This new parser has been tripped up by the extra newline that your env var strings have due to the YAML syntax used on the osx jobs:

- env: >

Our test suite did not account for this case, and the parser blew up, causing the condition to reject the respective jobs.

We've shipped a fix for this, and this looks like it confirms we should now respond correctly to your build config, too (these builds ran on staging, but we've also confirmed this in production):

Again, sorry about the issue, and thank you for your patience!

@Mark-Simulacrum
Copy link
Member

Yes, this should be fixed and I believe a macOS beta is or will be out in the next ~24 hours.

@durka
Copy link
Contributor Author

durka commented Jul 26, 2018

Great, I will be back to complain if it doesn't show up tomorrow!

@oconnor663
Copy link
Contributor

This seems fixed for me now. Thanks all!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-macos Operating system: macOS P-high High priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

8 participants