lava merge requestshttps://gitlab.collabora.com/lava/lava/-/merge_requests2024-03-25T08:50:27Zhttps://gitlab.collabora.com/lava/lava/-/merge_requests/180device-types: add mt8195-cherry-tomato-r32024-03-25T08:50:27ZLaura Naodevice-types: add mt8195-cherry-tomato-r3Add device type for the Acer Chromebook Spin 513 tomato Chromebook
(rev 3,4).
Signed-off-by: Laura Nao <laura.nao@collabora.com>Add device type for the Acer Chromebook Spin 513 tomato Chromebook
(rev 3,4).
Signed-off-by: Laura Nao <laura.nao@collabora.com>https://gitlab.collabora.com/lava/lava/-/merge_requests/179Allow setting kernel_start_message in device templates of aaeon-UPN-EHLX4RE-A...2024-03-07T13:58:10ZIgor PonomarevAllow setting kernel_start_message in device templates of aaeon-UPN-EHLX4RE-A10-0864 and minnowboard-common typeAllow setting kernel_start_message in devices of aaeon-UPN-EHLX4RE-A10-0864 and minnowboard-common type
Because those device type templates did not use the `default()`
filter they always overwrote the value of kernel_start_message
even ...Allow setting kernel_start_message in devices of aaeon-UPN-EHLX4RE-A10-0864 and minnowboard-common type
Because those device type templates did not use the `default()`
filter they always overwrote the value of kernel_start_message
even if a derived template set it. Now the value of "Booting in blind mode"
would only be used if the device template did not set it.https://gitlab.collabora.com/lava/lava/-/merge_requests/178Enhance security in container2024-03-12T07:05:49ZPablo Vigo MasEnhance security in containerAlthough the Lava service was running with the `lavaserver` user, the user actually
running the service inside the container is `root`, which poses security issues.
This fix redefines the container to run from the outset with the non-pri...Although the Lava service was running with the `lavaserver` user, the user actually
running the service inside the container is `root`, which poses security issues.
This fix redefines the container to run from the outset with the non-privileged `lavaserver` user.
Signed-off-by: Pablo Vigo <pvigo@collabora.com>https://gitlab.collabora.com/lava/lava/-/merge_requests/128Substitute parameters within install:git-repos2023-01-21T16:46:07ZEdmund SmithSubstitute parameters within install:git-reposAt present, a parameter can only be used within install:git-repos if
it is the entire value of the target, so we need a dedicated parameter
for the specific repository URL in a test, for example. This becomes
very inconvenient in larger ...At present, a parameter can only be used within install:git-repos if
it is the entire value of the target, so we need a dedicated parameter
for the specific repository URL in a test, for example. This becomes
very inconvenient in larger test sets, for example if we need to
create a parameter for every repository, because the repository URL
needs to contain short-lived tokens that must be substituted for.
This goes to some pains to only take action on strings on which there
is a valid parameter substitution present. This is with the goal of
minimising possible regressions from introducing this syntax.
This is part of AT9261.