Skip to content

Investigate non-determinism in manifest generation #40968

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.

Sign up for GitHub

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

Jump to bottom
Closed
brson opened this issue Mar 31, 2017 · 1 comment
Closed

Investigate non-determinism in manifest generation #40968

brson opened this issue Mar 31, 2017 · 1 comment
Assignees
@brson
Milestone
1.17

Comments

@brson
Copy link
Contributor

brson commented Mar 31, 2017 •
edited
Loading

1.17 is the first release that will be built by the new infrastructure. Last time I looked at one of the manifests generated from the new system, I saw some weird item orderings that made me suspicious, and I am worried about how that impacts rustup. Investigate.
@brson brson added this to the 1.17 milestone Mar 31, 2017
@brson brson self-assigned this Mar 31, 2017
@brson
Copy link
Contributor Author

brson commented Apr 10, 2017

I went through the output and it looks fine. I did submit a PR to convert HashMap to BTreeMap anyway: #41202

@brson brson closed this as completed Apr 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brson brson

Labels
None yet
Projects
None yet
Milestone
1.17
Development

No branches or pull requests
1 participant
@brson