Guilherme Gallo 9024e0df83 ci/lava: Don't fail if the section times mismatches ... Time drift can occur during LAVA job execution due to transitions between three different clocks. The process begins in the GitLab job [1], using the CI_JOB_STARTED_AT variable. If SSH is enabled, we then connect to the DUT through an Alpine-based SSH client container inside the LAVA dispatcher [2], where some GitLab-related steps are timestamped by lava_job_submitter. Finally, the DUT [3] runs and uses the setup-test-env.sh helper to handle GitLab sections, potentially using a third distinct clock. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/35222>		2025-06-05 22:32:37 +00:00
..
data	ci/lava: SSH tweaks	2025-06-04 15:43:40 +00:00
lava	ci: drop unneeded printing of pass/fail alongside the exit_code	2025-05-29 07:29:25 +00:00
utils	ci/lava: Don't fail if the section times mismatches	2025-06-05 22:32:37 +00:00
__init__.py	ci: Add unit tests for lava_job_submitter	2022-02-16 23:32:39 +00:00
conftest.py	ci: Simplify LAVA farm detection	2025-03-08 02:45:02 +00:00
test_lava_job_submitter.py	ci: drop unneeded printing of pass/fail alongside the exit_code	2025-05-29 07:29:25 +00:00