search for: cirrus_vm_instance_typ

...own @FOO@ expansions at job kickoff, borrowing from the earlier practice of autoconf. I don't see any other @FOO@ listings in .gitlab-ci.yml or ci/gitlab.yml, but I do see that the resulting ci/cirrus/$NAME.yml produced by the sed substitution during gitlab time DOES contain other things like @CIRRUS_VM_INSTANCE_TYPE@ that we are NOT touching on the gitlab side, so it seems fairly certain that Cirrus does some @FOO@ expansion, and timing which part of the job does which expansions may matter. At this point, erring on the side of caution and coding by copy/paste is simpler than determining if dropping the quot...

I took the easy route of crippling what I couldn't get working, on the grounds that partial coverage is better than none now that we have Cirrus CI checking commits on additional platforms. This series got me to a green checkmark: https://gitlab.com/ebblake/nbdkit/-/pipelines/793156983 but depends on an as-yet uncommitted patch in libvirt-ci:

On 3/1/23 17:54, Eric Blake wrote: > I took the easy route of crippling what I couldn't get working, on the > grounds that partial coverage is better than none now that we have > Cirrus CI checking commits on additional platforms. > > This series got me to a green checkmark: > https://gitlab.com/ebblake/nbdkit/-/pipelines/793156983 > > but depends on an as-yet