search for: lcitool

...ve of the regex itself being an otherwise forbidden string. For example: https://git.savannah.gnu.org/cgit/gnulib.git/tree/top/maint.mk#n371 And since libvirt used to use gnulib's maint.mk regex-based syntax checking, before weaning itself off gnulib, this may be why libvirt-ci (the source of lcitool) still utilizes @FOO@ regex with [@] escaping. Or, it could be because gitlab and/or Cirrus do their 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 c...

Pipeline #976539953 has failed! Project: libnbd ( https://gitlab.com/nbdkit/libnbd ) Branch: master ( https://gitlab.com/nbdkit/libnbd/-/commits/master ) Commit: 4e891bdb ( https://gitlab.com/nbdkit/libnbd/-/commit/4e891bdb37b62d3a11fc32e9170ed2a5df4a16c5 ) Commit Message: ci: Update to latest lcitool, for FreeBSD Yet ... Commit Author: Eric Blake ( https://gitlab.com/ebblake ) Pipeline #976539953 ( https://gitlab.com/nbdkit/libnbd/-/pipelines/976539953 ) triggered by Eric Blake ( https://gitlab.com/ebblake ) had 3 failed jobs. Job #4925806368 ( https://gitlab.com/nbdkit/libnbd/-/jobs/492580...

...with debug > patches. (I tried forking the project in my own space on gitlab, and > pushed a debug patch with just "set -x" onto a non-master branch *there* > -- but CI didn't start in response to that.) ci/README.rst is informative on that regards; I'm impressed at what lcitool (from the libvirt-ci) project gives us for local reproducibility of repeating various CI build failures. > > So, I only installed a new Alpine Linux virtual machine -- what a pain > *that* was --, and investigated what /usr/bin/expr was. When I found it > was a symlink to /bin/busybox...

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

On 3/21/23 15:05, Eric Blake wrote: > On Tue, Mar 21, 2023 at 07:04:59AM +0100, Laszlo Ersek wrote: >> On 3/20/23 20:41, Eric Blake wrote: >>> On Sun, Mar 19, 2023 at 10:41:37AM +0100, Laszlo Ersek wrote: >>>> This is version 4 of the following sub-series: >>>> >>>> [libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe()

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: