diff options
| author | Arkadiusz Hiler <arkadiusz.hiler@intel.com> | 2019-12-11 10:37:19 +0200 |
|---|---|---|
| committer | Arkadiusz Hiler <arkadiusz.hiler@intel.com> | 2019-12-11 15:39:41 +0200 |
| commit | e941638ce652140e89fe65c3437c55aca9d32865 (patch) | |
| tree | c03cb557e75e50cc0c6bb1e4a5e08903020855b6 /lib/intel_batchbuffer.c | |
| parent | e3664f8ce1f9152712b32e9bfa1e4ec93ffa5349 (diff) | |
runner/tests: Increase the timeout by 10x
The default timeout is 30s.
Recently we see more `ninja test` invocation failing due to runner tests
timing out. This happens for slower environments, i.e. running the
cross-compiled binaries through qemu.
Freedesktop CI/CD runners are shared machines with a lot of cores and
they accept many parallel jobs coming from multiple projects. There
are no resources guarantees, which leads to the sporadic slowness.
Runner tests are taking 10x longer than the next slowest test invoked by
`ninja test` on a typical run. They also seem more prone to resource
thrashing by other processes on the machine, probably due to heavier
reliance on disk IO.
Let's just give them proportional leeway when it comes to timing out.
Cc: Petri Latvala <petri.latvala@intel.com>
Issue: https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/197
Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
Diffstat (limited to 'lib/intel_batchbuffer.c')
0 files changed, 0 insertions, 0 deletions