Skip to content

CI failure on mac : suite::cli_self_upd::rustup_init_works_with_weird_names #3437

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
rbtcollins opened this issue Aug 13, 2023 · 1 comment
Closed

Comments

@rbtcollins
Copy link
Contributor

Problem you are trying to solve

I'm not sure if this is affecting every PR or just a flake on my recent docs PR.

I wonder perhaps if the (2) filename on Mac is triggering some OS level issue?

Solution you'd like

failures:

---- suite::cli_self_upd::rustup_init_works_with_weird_names stdout ----
ran: rustup ["set", "default-host", "x86_64-apple-darwin"]
inprocess: true
status: Some(0)
duration: 0.029s
stdout:
====

====

stderr:
====

====

ran: rustup ["set", "auto-self-update", "disable"]
inprocess: true
status: Some(0)
duration: 0.003s
stdout:
====

====

stderr:
====
info: auto-self-update mode set to 'disable'

====

ran: rustup-init(2) ["-y", "--no-modify-path"]
inprocess: false
status: None
duration: 0.002s
stdout:
====

====

stderr:
====

====


> rustup-init(2) -y --no-modify-path
out.ok: false
out.stdout (0 lines):
    
out.stderr (0 lines):
    
expected.ok: true
thread 'suite::cli_self_upd::rustup_init_works_with_weird_names' panicked at 'explicit panic', tests/suite/cli_self_upd.rs:678:16
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Notes

No response

@rbtcollins
Copy link
Contributor Author

Looks like a runner-flakiness issue :/.

@rbtcollins rbtcollins closed this as not planned Won't fix, can't repro, duplicate, stale Aug 13, 2023
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

No branches or pull requests

1 participant