[Pkg-zsh-devel] zsh FTBFS under Salsa CI's reprotest: 'KEY_EVENT' undeclared / blhc CI check disabled / bullseye freeze: zsh is considered a key package

[Daniel Shahaf]

Axel Beckert wrote on Mon, 12 Oct 2020 20:48 +0200:
> Running test: unreadable directories can be globbed (users/24619, users/24626)
> Test ../../Test/D02glob.ztst failed: test was expected to fail, but passed.
> Was testing: unreadable directories can be globbed (users/24619, users/24626)
> 
> This might be an test environment issue, maybe some kernel features
> not available or so? Not sure.

Not an answer to your question: Note that
zsh-5.7.1-test-2-67-gedc04bd94 changed this test from "expected
failure" to "expected pass" in upstream master post 5.8.

> P.S.: I wonder if the other, more obscure test suite failure — which
> only happens inside the reprotest check on Salsa CI, too — is also
> related to eatmydata. Unfortunately the debug output is not as verbose
> as in P01privileged.ztst. Like maybe like it is just checked for some
> empty output, but it actually contains "ERROR: ld.so: object
> 'libeatmydata.so' from LD_PRELOAD cannot be preloaded (cannot open
> shared object file): ignored." and the test suite thinks the test
> failed because there was any output from some globbing routine.

Pointer to the "other, more obscure test suite failure", please?

> P.P.S.: I also wonder if that missing KEY_EVENT thingy could also be
> triggered by not being able to load some arbitrary .so file.

I don't see how, but I suppose it won't hurt to grep «configure &&
make»'s log/debug output for eatmydata errors.

And note that once the upstream commit you cherry-picked to your branch
is merged (whether by being cherry-picked or by packaging 5.9), the
failure mode will change: the added «#ifdef KEY_EVENT» will silently
evaluate to false, with little consequence.

Cheers,

Daniel