Hello, The Eclair step is now the dominating aspect of wallclock time. While the recent changes were a step in the right direction, we need some adjustments.
First, we have *-testing running in all cases, but my understanding was that that was supposed to be for deploying a new version of Eclair. Can we make this be generally off? Next, jobs are scheduled in the order they appear in the yaml file, which means the general ARM one goes ahead of the safety target. Just something to bear in mind as changes are being made. While the x86 runs are non-fatal, having them fail is still gets in the way of trivially telling that the pipeline is green. The names, -safety and no suffix are a little problematic, seeing as everything here is for safety use. Overall, what I think we want is something more like this: Jobs named as *-all and *-amd. After all, it's AMD's safety target specifically, not necessarily someone elses. The *-all targets want everything possible enabling. Ideally we want something like Linux's COMPILE_TEST, but in the short term we can just adjust the input Kconfig. Like we had with the common configuration and the per-arch configuration, I think we want to express the clean rules as common, with a wider (a.k.a stricter) set used for the *-amd target. The longterm goal is to get the *-all targets as strict as the *-amd targets, but right now because there are no blocking clean rules, it's easier for regressions to slip in. This brings us back to the debate about the excluded files from external sources. They still need fixing one way or another. Do we see about including them for analysis in the *-all targets, or leave them excluded knowing that whomever need to unpack that can of worms needs to do a lot of fixing anyway? Does this sound sensible? Thanks, ~Andrew
