cancel PR builds early. currently set to 500 builds. reduce to e.g., 20?
split multi dwq inctances, e.g., “riotbuild” into “riotbuild0” … “riotbuild7”
“final” location of these markdown documents?
Building a subset
riotdocker for Pi fleet?
consider using bors
if there are queued PRs, at build start, all queued PRs will be tested together. If that build fails, bors does some smart bisecting (build one half, …). The still failing PR’s get notified, the passing ones merged. => potential huge reduction in queue times.
all PR’s are always tested either together or in series => avoids semantic incompatibilites (e.g., individual PRs passing but combination breaks things)
some CI config necessary
PR’s get closed by bors after merge (don’t show as “merged” anymore)
PR’s don’t get distinct merge commit anymore (there’s one per batch saying “merging #123, #236, #252”)
maybe a blocker: batched builds cannot compare code size / any differences between just master and a single PR
configure usual CI workflow to build/test only a subset (like, one per architecture)
optionally build all (set via CI: tag)
configure bors to require that build to have succeeded, in addition to the other static test results
use bors to do final full compile test & merge
From matrix channel:
I think that "-- skipping test due to positive cache hit" should be parsed out and shown in the final result. even better would be to have the previous results still available so they can be linked.
+1 for linking positive test result
a) saving intermediate PR results, is that feasible?
b) show skipped tests in total output
c) either link those skipped test results to a) or store somewhere else
document infra, maintainers, reduce bus factors
Put names and where to get info
Forum would not be the first place to look
Documentation is not prominent
At some point we should make a PR to the RIOT repo
Mostly links to murdock, github actions, hil jenkins
Human action for restarting workers
Part of the infra, there should be at least 2 names
Sort out the names of who is responsible for what
Use a tree (murdock, github actions, hil jenkins), include infra (KS)
ICC needs a HAW account
From murdock, we should document so anyone can shutdown a node that may cause failing
Web interface for control murdock (someone other than KS should implement it)?