thread 'rustc' panicked at 'other was less than the current instant' #48514
Comments
|
This sounds like another case of faulty hardware/OS causing Could you provide details on what your exact CPU is? |
pietroalbini
added
I-ICE
|
hw.machine=amd64
hw.model=Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
hw.ncpu=4
hw.byteorder=1234
hw.pagesize=4096
hw.vendor=LENOVO
hw.product=20GJ003QMC
hw.version=ThinkPad S2
|
|
In my experience, |
This was referenced Dec 18, 2018
Closed
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this issue
Jan 7, 2019
This commit is an attempt to force `Instant::now` to be monotonic through any means possible. We tried relying on OS/hardware/clock implementations, but those seem buggy enough that we can't rely on them in practice. This commit implements the same hammer Firefox recently implemented (noted in rust-lang#56612) which is to just keep whatever the lastest `Instant::now()` return value was in memory, returning that instead of the OS looks like it's moving backwards. Closes rust-lang#48514 Closes rust-lang#49281 cc rust-lang#51648 cc rust-lang#56560 Closes rust-lang#56612 Closes rust-lang#56940
bors
added a commit
that referenced
this issue
Jan 8, 2019
std: Force `Instant::now()` to be monotonic This commit is an attempt to force `Instant::now` to be monotonic through any means possible. We tried relying on OS/hardware/clock implementations, but those seem buggy enough that we can't rely on them in practice. This commit implements the same hammer Firefox recently implemented (noted in #56612) which is to just keep whatever the lastest `Instant::now()` return value was in memory, returning that instead of the OS looks like it's moving backwards. Closes #48514 Closes #49281 cc #51648 cc #56560 Closes #56612 Closes #56940
bors
added a commit
that referenced
this issue
Jan 8, 2019
std: Force `Instant::now()` to be monotonic This commit is an attempt to force `Instant::now` to be monotonic through any means possible. We tried relying on OS/hardware/clock implementations, but those seem buggy enough that we can't rely on them in practice. This commit implements the same hammer Firefox recently implemented (noted in #56612) which is to just keep whatever the lastest `Instant::now()` return value was in memory, returning that instead of the OS looks like it's moving backwards. Closes #48514 Closes #49281 cc #51648 cc #56560 Closes #56612 Closes #56940
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I created hello.rs file with copy of example on https://www.rust-lang.org/en-US/
then
rustc hello.rs
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: rustc 1.20.0 running on x86_64-unknown-openbsd
thread 'rustc' panicked at 'other was less than the current instant', /usr/obj/ports/rust-1.20.0/rustc-1.20.0-src/src/libstd/sys/unix/time.rs:276:16
note: Run with
RUST_BACKTRACE=1for a backtrace.I'm on OpenBSD 6.2 amd64 with rust-1.20.0
The text was updated successfully, but these errors were encountered: