commented on
merge request !670
"aum-rollback-bootcount: clarify steps to run the test"
at
tests / apertis-test-cases
Much better! Thank you!
commented on
merge request !670
"aum-rollback-bootcount: clarify steps to run the test"
at
tests / apertis-test-cases
Can't we fix that to avoid confusions?
commented on
merge request !670
"aum-rollback-bootcount: clarify steps to run the test"
at
tests / apertis-test-cases
Probably we should check which was the original deployment to confirm this.
commented on
merge request !670
"aum-rollback-bootcount: clarify steps to run the test"
at
tests / apertis-test-cases
@wlozano What do you thing about 7a94e678?
-
7a94e678 · aum-rollback-bootcount: clarify steps to run the test
-
2718abcf · lava/config.yaml: bump imgpath for v2026dev1
accepted
merge request
!671
"lava/config.yaml: bump imgpath for v2026dev1"
at
tests / apertis-test-cases
accepted
merge request
!672
"lava/config.yaml: bump imgpath for v2025"
at
tests / apertis-test-cases
-
18f55e88 · lava/config.yaml: bump imgpath for v2025
commented on
merge request !671
"lava/config.yaml: bump imgpath for v2026dev1"
at
tests / apertis-test-cases
Branching process fixed with infrastructure/apertis-infrastructure!233 (merged)
commented on
merge request !672
"lava/config.yaml: bump imgpath for v2025"
at
tests / apertis-test-cases
Branching process fixed with infrastructure/apertis-infrastructure!233 (merged)
opened
merge request
!671
"lava/config.yaml: bump imgpath for v2026dev1"
at
tests / apertis-test-cases
commented on
merge request !670
"aum-rollback-bootcount: clarify steps to run the test"
at
tests / apertis-test-cases
I see the intention, but I think the outcome is not as clear as we expect, since the template will use a numbered list ...
-
1c4fa9e7 · aum-rollback-bootcount: clarify steps to run the test