Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
None
-
production
-
None
-
Android emulator run on RHEL 8.4 on x86_64 hardware; compiled by gcc.
-
-
39efd3c35fd6713104d7cc2f47567010485cdae5
Description
This attempted integration timed out after 3 hours. I can't see anything obviously stuck, just the whole process of running tests takes a long time, possibly due to running on VMs that weren't getting enough time-slices. There is one pause of several minutes, from 22:39:09's computation of the test timeout (which appears to be when the three hour timer started) to 22:43:24's report of executing the first test; this may well just be the time that test took to run. Other than that, the three hours do appear to have simply been taken up by running tests at a steady rate, with no obviously visible long delays.
Possible remedies:
- Replace the wall-clock time-out with a system-time time-out (so when the process has actually used 3h of CPU-time, not counting time it was swapped out to let some other process run (other than its children) or time when its VM wasn't getting run).
- Increase the time-out, at least for this platform.
(I note, in passing, that "Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0." We should probably fix that, too.)