mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-18 04:40:26 +01:00
de2c847c24
This week we found that the r8152 issue can happen during the boot phase, make the necessary adjustments to detect it. https://gitlab.freedesktop.org/vigneshraman/linux/-/jobs/53651940 Notes: - The kernel messages during the boot phase is being redirected to the feedback messages due to the namespaces from the SSH job. - Update the unit tests: - Add boot phase detection - Correctly set the boot phase when mocking LogFollower Reported-by: Vignesh Raman <vignesh.raman@collabora.com> Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27081>
21 lines
876 B
Python
21 lines
876 B
Python
from os import getenv
|
|
|
|
# How many attempts should be made when a timeout happen during LAVA device boot.
|
|
NUMBER_OF_ATTEMPTS_LAVA_BOOT = int(getenv("LAVA_NUMBER_OF_ATTEMPTS_LAVA_BOOT", 3))
|
|
|
|
|
|
# Supports any integers in [0, 100].
|
|
# The scheduler considers the job priority when ordering the queue
|
|
# to consider which job should run next.
|
|
JOB_PRIORITY = int(getenv("JOB_PRIORITY", 75))
|
|
|
|
# Use UART over the default SSH mechanism to follow logs.
|
|
# Caution: this can lead to device silence in some devices in Mesa CI.
|
|
FORCE_UART = bool(getenv("LAVA_FORCE_UART", False))
|
|
|
|
# How many times the r8152 error may happen to consider it a known issue.
|
|
KNOWN_ISSUE_R8152_MAX_CONSECUTIVE_COUNTER: int = 10
|
|
|
|
# This is considered noise, since LAVA produces this log after receiving a package of feedback
|
|
# messages.
|
|
LOG_DEBUG_FEEDBACK_NOISE = "Listened to connection for namespace 'dut' done"
|