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

Update minimum rust version to 1.9.0 #525

Merged
merged 1 commit into from
Feb 27, 2017
Merged

Conversation

Susurrus
Copy link
Contributor

This is largely because of features used in tempfile from 1.8 and 1.9. This was tested locally, so we'll see what CI says.

This does bring up the issue of the CI testing in the ci folder. That specifies the rust version as 1.7.0, but then when I looked at the docker images they seemed to only support 1.10, so maybe someone can comment on whether anything should be done about those things.

@Susurrus
Copy link
Contributor Author

Looks like Rust 1.9 fails on ARM targets, which isn't surprising given the comments in the code. Maybe it's time to switch to using trust templates to do this testing? Though I don't know how this was supposed to work considering the mips targets weren't even supported until Rust 1.14

@posborne
Copy link
Member

That specifies the rust version as 1.7.0, but then when I looked at the docker images they seemed to only support 1.10

Yeah, I built newer images somewhere along the line with 1.10 but never got around to fully updating nix to use the new stuff. I think the current is still using 1.7 images as it is pointed to posborne/rust-cross:<platform>. The latest stuff from https://github.com/rust-embedded/docker-rust-cross results in images in the form posborne/rust-cross-<platform>:<version> being published. That's not what we point to at the moment.

There are images for several of the platforms pushed for 1.10 now, but I haven't updated nix but it would be great to move to something a bit newer. Long term, I think I prefer the approach that https://github.com/japaric/trust takes.

@Susurrus
Copy link
Contributor Author

So is there anything I should change in this PR, maybe move all the ARM stuff to use 1.10 and keep the other targets on 1.9?

This still leaves the question about mips targets pre-1.14. I don't even understand how they could compile since those targets didn't exist previously.

@Susurrus
Copy link
Contributor Author

Note that tempfile has clarified that their minimum supported version is 1.9.0 and they now do CI on that version (see Stebalien/tempfile@0b7e0d5)

@fiveop
Copy link
Contributor

fiveop commented Feb 26, 2017

I suggest, that you only change the README.md in this PR. We certainly do not support lower versions. Fixin the CI is different problem, thus I would leave the other two files alone.

@Susurrus
Copy link
Contributor Author

Done.

@fiveop
Copy link
Contributor

fiveop commented Feb 27, 2017

@homu r+

After we are done setting up the new CI configuration, we should probably revisit this.

@homu
Copy link
Contributor

homu commented Feb 27, 2017

📌 Commit 98dcc84 has been approved by fiveop

@homu
Copy link
Contributor

homu commented Feb 27, 2017

⚡ Test exempted - status

@homu homu merged commit 98dcc84 into nix-rust:master Feb 27, 2017
homu added a commit that referenced this pull request Feb 27, 2017
Update minimum rust version to 1.9.0

This is largely because of features used in `tempfile` from 1.8 and 1.9. This was tested locally, so we'll see what CI says.

This does bring up the issue of the CI testing in the `ci` folder. That specifies the rust version as 1.7.0, but then when I looked at the docker images they seemed to only support 1.10, so maybe someone can comment on whether anything should be done about those things.
@Susurrus Susurrus deleted the min_rust branch February 27, 2017 16:28
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.

4 participants