Guilherme Gallo ffe2b31f9a ci/lava: Detect hard resets during test phase ... Hard resets should not occur during the test phase. Therefore, let's detect them through specific log messages and raise an exception for a known issue if it occurs. Without this detection, the job will continue running on both Gitlab and LAVA until a timeout occurs. Real case: https://gitlab.freedesktop.org/mesa/mesa/-/jobs/53546660 Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26995>		2024-01-23 22:47:24 +00:00
..
utils	ci/lava: Detect hard resets during test phase	2024-01-23 22:47:24 +00:00
__init__.py	ci/lava: Create LogFollower and move logging methods	2022-07-07 00:28:53 +00:00
exceptions.py	ci/lava: Refactor LAVAJobSubmitter and add tests	2023-04-19 14:36:37 +00:00
lava_job_submitter.py	ci: deduplicate constructing the ARTIFACTS_BASE_URL	2023-12-13 21:12:22 +00:00
lava-gitlab-ci.yml	ci/traces: extend no-output timeout by 5 minutes	2023-09-07 23:43:02 +00:00
lava-pytest.sh	ci: enable shellcheck on whole .gitlab-ci	2023-05-25 16:06:53 +02:00
lava-submit.sh	ci: inject gfx-ci/linux S3 artifacts without rebuilding containers	2023-11-07 12:22:09 +00:00
requirements-test.txt	ci/lava: Add LavaFarm class to find LAVA farm from runner tag	2023-02-16 13:08:41 +00:00
requirements.txt	ci/lava: Use python-fire in job submitter	2023-04-19 14:36:37 +00:00