| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This works around the following error:
java.lang.NoSuchMethodError: java.nio.ByteBuffer.clear()Ljava/nio/ByteBuffer;
at com.google.devtools.build.lib.profiler.Profiler$BinaryFormatWriter.run(Profiler.java:949)
at java.lang.Thread.run(Thread.java:748)
JDK 9 introduced an overloaded methods with covariant return type.
Closes #5886.
PiperOrigin-RevId: 208642556
|
|
|
|
|
|
|
|
|
|
| |
This will test that we can correctly build Bazel via RBE on each pre- and postsubmit.
It's also required for the downstream pipeline to work again.
I've tested this change via a GitHub PR here: https://buildkite.com/bazel/bazel-bazel-github-presubmit/builds/333
RELNOTES: None.
PiperOrigin-RevId: 207675545
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First, make the function that wastes user time keep track of how much
processor time has been used so far, and make the function that wastes
system time track overall wall time. This is to minimize the number
of "overhead" system calls, which can tamper with our measurements.
Second, make the loop of the function that wastes user time more costly
so that modern processors don't run it too fast. Otherwise, the overhead
to track used time becomes significant in system time and makes our
tests fail.
This should fix the flakiness observed in our process-wrapper tests
when run on the modern CPUs that the iMac Pros carry.
Tested: I haven't been able to reproduce the flakiness. Running the
spend_cpu_time binary by hand reports very accurate timings for both
system and user time, even when pausing the program while it runs.
RELNOTES: None.
PiperOrigin-RevId: 204264910
|
|
|
|
| |
PiperOrigin-RevId: 203746935
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 203736658
|
|
|
|
|
|
|
|
|
| |
it consistently takes over 10 minutes for little
benefit on presubmit. we'll continue to run it on
postsubmit for every commit.
RELNOTES: None
PiperOrigin-RevId: 202094016
|
|
|
|
|
|
|
|
| |
I have added Buildkite workers running on Ubuntu 18.04 LTS.
We should test Bazel on it.
RELNOTES: None
PiperOrigin-RevId: 201677421
|
|
|
|
|
|
|
|
|
|
| |
We are seeing quite a lot of test timeouts of very long
running tests. This significantly adds to presubmit times
as we retry failing tests up to 3 times. This change increases
the test timeout from 15 to 20 minutes.
RELNOTES: None
PiperOrigin-RevId: 201514589
|
|
|
|
|
|
| |
TESTED=presubmit
RELNOTES: None
PiperOrigin-RevId: 190056498
|
|
Closes #4900.
PiperOrigin-RevId: 190043375
|