8626a52637
To use the supported job definition depending on some Mesa CI job characteristics. The strategy here, is to use LAVA with a containerized SSH session to follow the job output, escaping from dumping data to the UART, which proves to be error prone in some devices. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/22870>
19 lines
501 B
Python
19 lines
501 B
Python
from .console_format import CONSOLE_LOG
|
|
from .gitlab_section import GitlabSection
|
|
from .lava_job import LAVAJob
|
|
from .lava_job_definition import generate_lava_job_definition
|
|
from .lava_proxy import call_proxy, setup_lava_proxy
|
|
from .log_follower import (
|
|
LogFollower,
|
|
fatal_err,
|
|
fix_lava_gitlab_section_log,
|
|
hide_sensitive_data,
|
|
print_log,
|
|
)
|
|
from .log_section import (
|
|
DEFAULT_GITLAB_SECTION_TIMEOUTS,
|
|
FALLBACK_GITLAB_SECTION_TIMEOUT,
|
|
LogSection,
|
|
LogSectionType,
|
|
)
|