jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Sitnikov <sitnikov.vladi...@gmail.com>
Subject GitHub Actions vs Thread.sleep
Date Tue, 15 Oct 2019 07:30:56 GMT
I see GitHub Actions (both Windows and macOS) are very flaky when it comes
to "thread.sleep-related tests".

In other words:

long a = System.currentTimeMillis();
Thread.sleep(100);
long b = System.currentTimeMillis();

b-a can easily be 421 (see child1Elapsed in
https://github.com/vlsi/jmeter/runs/259886838#step:4:468 ).

I see a couple of ways out there:
1) Exclude the tests from GitHub Actions CI
2) Rewrite the tests with https://github.com/Devexperts/time-test

Are there volunteers to heal GitHub Actions CI?

Vladimir

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message