adt-matrix: Include main linux package version in triggers for retry
For dkms modules that do not have any specific tests, the matrix will run
`dkms-autopkgtest` (part of dkms source) which consists of building the
module only. The test will run only if the `trigger` parameter contains
the linux main package version because it expects the following version
format:
linux-<derivative>/<kernel_version>-<abi_version>.<upload_version>
For retry, the `trigger` param consists of only meta version which has the
following format:
linux-<derivative>/<kernel_version>.<abi_version>.<upload_version>
which contains a dot instead of a '-' and prevents the test from
running and it marks it as 'Passed'.
Fix this by including the main version for retries too.
Note: When the test is triggered for the first time, the main version is
included, that's why the first run is always correct. The problem appears
only for retries. This broken logic prevents dkms builds failures from
being properly detected if the test is rerun (which usually happens because
people try the test 1-2 times before confirming if there's an issue)
If a parent annotations sets a config rule for `arch-flavour` and a child annotations overrides the same config with an `arch` rule, the child rule should override the parent also for `arch-flavour`.
This fix allows to properly handle this particular case.
Moreover, add a proper unit test for this particular case, to make sure that we are not breaking this behavior in the future.
Acked-by: Andrei Gherzan <email address hidden>
Acked-by: Andrei Gherzan <email address hidden>
Signed-off-by: Andrea Righi <email address hidden>
Remove duplication and error between on-boarding documentations - reflects changes made to kteam-docs as well (Cranky Tutorial and New Starter Tasks).
Acked-by: Agathe Porte <email address hidden>
cranky: docs: remove duplication amongst new starter docs
I removed the 'Add builders' section from Crank Turning Setup because that was hosted in 3
locations with different info (Newstarter Tasks, Crank Turning Setup, Cranky Tutorial) - now
builder info is only in Newstarter Tasks
I moved descriptive paragraphs for each env setup file from Cranky Tutorial to Crank Turning
Setup because I also removed the env setup section from Cranky Tutorial (env setup only lives
in Crank Turning Setup now).
I moved some 'Get cranky tools' info from Cranky Tutorial to Crank Turning Setup because I
removed that section from Cranky Tutorial to consolidate it.
Add support for bumping lrm, signed and meta package versions so that all the version mangling is in one place. Handling old meta versions is not yet fully complete, there's sure to be some backports and such that are not yet supported.
This patchset is a prereq for pulling the countless update-version scripts out of the various trees.
Acked-by: Thadeu Lima de Souza Cascardo <email address hidden>
Acked-by: Dimitri John Ledkov <email address hidden>
Acked-by: Thadeu Lima de Souza Cascardo <email address hidden>
Acked-by: Dimitri John Ledkov <email address hidden>
Signed-off-by: Dimitri John Ledkov <email address hidden>
