Skip to content

Improve error message on home directory mismatch#1895

Merged
kinnison merged 1 commit intorust-lang:masterfrom
calebcartwright:home-mismatch-errors
Jun 11, 2019
Merged

Improve error message on home directory mismatch#1895
kinnison merged 1 commit intorust-lang:masterfrom
calebcartwright:home-mismatch-errors

Conversation

@calebcartwright
Copy link
Copy Markdown
Member

Refs #1884 - Augment error message displayed to the user when there's a mismatch between $HOME and the euid-obtained value for the home directory

@calebcartwright
Copy link
Copy Markdown
Member Author

AppVeyor had a couple tests failing, all with an error message of: An attempt was made to create more links on a file than the file system supports.

I don't think that's due to the changes here (I see the same error message in other PR builds), but let me know if that's something I need to look at on my end.

@kinnison
Copy link
Copy Markdown
Contributor

AppVeyor had a couple tests failing, all with an error message of: An attempt was made to create more links on a file than the file system supports.

I don't think that's due to the changes here (I see the same error message in other PR builds), but let me know if that's something I need to look at on my end.

Yeah, that's appveyor being a pain. I'm looking at what it might take to switch to a different Windows provider for builds. I'm going to chat to someone from Travis tomorrow.

kinnison
kinnison previously approved these changes Jun 11, 2019
Copy link
Copy Markdown
Contributor

@kinnison kinnison left a comment

Choose a reason for hiding this comment

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

I think this looks good to me.

@kinnison kinnison dismissed their stale review June 11, 2019 22:39

Noticed a problem

Copy link
Copy Markdown
Contributor

@kinnison kinnison left a comment

Choose a reason for hiding this comment

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

Please fold the commits together - 'chore' commits are not in-style for rustup.

Once that's done it looks good to me.

@calebcartwright
Copy link
Copy Markdown
Member Author

thanks @kinnison! squashed accordingly.

so I know for future reference, is it that rustup uses different commit message standards or that contributors should squash all commits into one?

@calebcartwright
Copy link
Copy Markdown
Member Author

Travis failure seems unrelated, but again please let me know if there's anything needed on my end

info: downloading component 'rustfmt'
error: component download failed for rustfmt-x86_64-unknown-linux-gnu
info: caused by: could not download file from 'https://static.rust-lang.org/dist/2019-05-23/rustfmt-1.2.0-x86_64-unknown-linux-gnu.tar.xz' to '/home/travis/.rustup/downloads/c6a734a2721ec288f9e96d7e33f23fd1ed6f85effd4bcac28f020f7b2db247fb.partial'
info: caused by: failed to make network request
info: caused by: https://static.rust-lang.org/dist/2019-05-23/rustfmt-1.2.0-x86_64-unknown-linux-gnu.tar.xz: timed out
error: 'rustfmt' is not installed for the toolchain 'stable-x86_64-unknown-linux-gnu'

@kinnison
Copy link
Copy Markdown
Contributor

thanks @kinnison! squashed accordingly.

so I know for future reference, is it that rustup uses different commit message standards or that contributors should squash all commits into one?

It's more that I prefer the commits be actually useful for working out why a line is what it is.

i.e. the change should be attributed to the functional difference, not that you were making a cleanup in response to a code review :D

@kinnison
Copy link
Copy Markdown
Contributor

Travis failure seems unrelated, but again please let me know if there's anything needed on my end

I've retried the travis, it shouldn't be anything you did, looks like an internal timeout in Travis

@kinnison kinnison merged commit 04039b0 into rust-lang:master Jun 11, 2019
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