Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Stopwatch elapsed count can decrease without calling reset() #477

Closed
DartBot opened this issue Nov 16, 2011 · 8 comments
Closed

Stopwatch elapsed count can decrease without calling reset() #477

DartBot opened this issue Nov 16, 2011 · 8 comments
Assignees
@rmacnak-google
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.

Comments

@DartBot
Copy link

DartBot commented Nov 16, 2011

This issue was originally filed by rodion...@unipro.ru

What steps will reproduce the problem?

  1. run LibTest/core/StopWatch/start/StopWatch_start_A01_t02.dart
    several times, if necessary

What is the expected output?
Test is expected to pass and each successful number it prints should be greater than or equal to the last.
What do you see instead?
Elapsed: 3192373
Elapsed: 3193985
Elapsed: 3192729

What version of the product are you using? On what operating system?
rev. 1562, ubuntu 10 x64
@floitschG
Copy link
Contributor

Added Area-VM, Triaged labels.

@iposva-google
Copy link
Contributor

We are not calling monotonic time, so I can imagine that this happens occasionally when the time is being adjusted.

Eventually Stopwatch should use a high-performance, high-resolution time source.

Set owner to @a-siva.
Added this to the M1 milestone.
Added Accepted label.

@iposva-google
Copy link
Contributor

Removed this from the M1 milestone.
Added this to the M3 milestone.

@iposva-google
Copy link
Contributor

Removed this from the M3 milestone.
Added this to the M4 milestone.

@larsbak
Copy link

larsbak commented May 28, 2013

Removed this from the M4 milestone.
Added this to the M5 milestone.

@iposva-google
Copy link
Contributor

Removed Priority-Medium label.
Added Priority-Unassigned label.

@iposva-google
Copy link
Contributor

Removed this from the M5 milestone.

@DartBot DartBot added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Jun 5, 2013
@rmacnak-google
Copy link
Contributor

c99df05

This was referenced Oct 29, 2020
Open
Closed
Closed
This was referenced Nov 5, 2020
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rmacnak-google rmacnak-google

Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@iposva-google @larsbak @rmacnak-google @floitschG @a-siva @DartBot