[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

[Axel Beckert]

Hi Daniel,

Daniel Shahaf wrote:
> > > Pointer to the "other, more obscure test suite failure", please?  
> > 
> > Citing from https://salsa.debian.org/debian/zsh/-/jobs/1066149#L6632:
> > 
> > Running test: unreadable directories can be globbed (users/24619, users/24626)
[…]
> Oh, I did see both of these.  Sorry, I didn't get the reference.

Wasn't sure if I forgot it at the one place or the other.

Thanks for having looked into that.

> That test failure can be easily reproduced by adding the 'f' flag to
> any existing test case that passes, or by writing a new one such as:

Ok, I assume this just to see the effect as if it would have failed,
not the real cause of it, right?

> [lots of details and test source code]

Just skimmed through it for now, sorry. Probably too tired already.

> So, to summarize:
> 
> 1. For the failure in question, the actual stdout and stderr are equal
> to the expected ones, verbatim.

Ok, so eatmydata can't be the cause here, right?

> 2. Probable upstream bug: harness should print the actual output when
> «*» or «q» are used.

Yeah, might help to understand the issue on Salsa CI.

> 4. Upstream issue: How to clarify the "was expected to fail, but
> passed" message?

I think there's nothing to clarify at that point. In the end, it's a
"fail". Doesn't matter if there's one negation in there or not.

> (Feel free to continue the relevant parts on -workers at .)

At least no more today...

> > > > 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.  
> > 
> > Yeah, I should probably setup a chroot without eatmydata installed.
> > I'm admittedly currently too lazy to do that…
> 
> Can't we grep the config.log files that the CI build produces?

If the build doesn't succeed, the artefacts just contain that
reprotest.log file which is also shown as far as I understand.

The configure output is at
https://salsa.debian.org/debian/zsh/-/jobs/1066149#L1014, but I assume
you want that more detailed config.log file. I think that one wouldn't
be in the artefacts even if the build succeeded.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE