`test_uptime::test_uptime_with_file_containing_valid_boot_time_utmpx_record stdout` fails on linux arm64
Open
Nobody has claimed this yet.
U - uptime
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
See:
https://github.com/uutils/coreutils/pull/7153
---- test_uptime::test_uptime_with_file_containing_valid_boot_time_utmpx_record stdout ----
run: /home/runner/work/coreutils/coreutils/target/aarch64-unknown-linux-gnu/debug/coreutils uptime testx
thread 'test_uptime::test_uptime_with_file_containing_valid_boot_time_utmpx_record' panicked at tests/by-util/test_uptime.rs:116:10:
Command was expected to succeed. code: 101
stdout = 09:22:30
stderr = thread 'main' panicked at src/uucore/src/lib/features/utmpx.rs:190:31:
attempt to multiply with overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
stack backtrace:
0: rust_begin_unwind
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/std/src/panicking.rs:652:5
1: core::panicking::panic_fmt
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/panicking.rs:72:14
2: tests::common::util::CmdResult::success
at ./tests/common/util.rs:417:9
3: tests::common::util::UCommand::succeeds
at ./tests/common/util.rs:1782:9
4: tests::test_uptime::test_uptime_with_file_containing_valid_boot_time_utmpx_record
at ./tests/by-util/test_uptime.rs:114:5
5: tests::test_uptime::test_uptime_with_file_containing_valid_boot_time_utmpx_record::{{closure}}
at ./tests/by-util/test_uptime.rs:103:67
6: core::ops::function::FnOnce::call_once
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/ops/function.rs:250:5
7: core::ops::function::FnOnce::call_once
at /rustc/129f3b9964af4d4a709d1383930ade12dfe7c081/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Contributor guide
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
Inspect the failure in src/uucore/src/lib/features/utmpx.rs:190 and the reproducing test in tests/by-util/test_uptime.rs:103-116. Run test_uptime::test_uptime_with_file_containing_valid_boot_time_utmpx_record on Linux arm64, then verify the test succeeds without the overflow panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100