oxidecomputer / oxidecomputer/oxide.rs
spurious failure from test_auth_login_double
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 75
- Forks
- 21
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Here's what I saw:
---- test_auth_login_double stdout ----
thread 'test_auth_login_double' panicked at cli/tests/test_auth.rs:400:5:
assertion failed: modes do not match for /var/folders/q4/wlt470150sn72ty0zyxxcng8003c85/T/.tmpBZiLqQ/config.toml
expected: 0o644
actual: 0o666
umask: 0o022
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
I was on macOS; I've only seen this failure once.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with cli/tests/test_auth.rs around test_auth_login_double and its assertion at line 400. Reproduce the macOS failure and inspect how config.toml permissions are checked against the umask. Done means the test no longer spuriously fails and its permission expectation is consistent with the observed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100