bfd50f72eb
We were just detecting if a log like [ 143.080663] r8152 2-1.3:1.0 eth0: Tx status -71 happened once before [ 316.389695] nfs: server 192.168.201.1 not responding, still trying But we can use a counter to be more assured that the device is struggling to recover and we can add let this detection happen during the boot phase. This mimics how other freedreno devices deal with this problem, see `cros_servo_run.py:64` for example. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27081>
18 lines
691 B
Python
18 lines
691 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
|