On Tue, Nov 22, 2022 at 9:41 AM Ævar Arnfjörð Bjarmason
<avarab@xxxxxxxxx> wrote:
> On Mon, Nov 21 2022, Eric Sunshine wrote:
> > The empty "chainlinttmp/tests" file also sounds suspicious. If you
> > haven't already done so, I would recommend following the advice in [1]
> > and running each command individually which Makefile would have run;
> > this might allow you to isolate the problematic command or shell
> > construct if such exists.
>
> I can also reproduce this on gcc202. It's the same issue with ending up
> with an empty "tests" file.
Were you able to determine why the "tests" file is empty? The creation
loop is simple enough:
for i in $(CHAINLINTTESTS); do \
echo "test_expect_success '$$i' '" && \
sed -e '/^# LINT: /d' chainlint/$$i.test && \
echo "'"; \
done >'$(CHAINLINTTMP_SQ)'/tests && \
and the file is never changed after that (or shouldn't be).
> avar@gcc202:/run/user/1632/git/t$ uname -a
> Linux gcc202 6.0.0-4-sparc64-smp #1 SMP Debian 6.0.8-1 (2022-11-11) sparc64 GNU/Linux
> avar@gcc202:/run/user/1632/git/t$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Debian
> Description: Debian GNU/Linux bookworm/sid
> Release: n/a
> Codename: bookworm
This is one of the compile-machines to which you have access?
> The change at the tip of
> https://lore.kernel.org/git/221122.86cz9fbyln.gmgdl@xxxxxxxxxxxxxxxxxxx/
> fixes it for me, i.e. getting rid of the perl threads stuff...
I'm confused. How does a change to chainlint.pl -- which only reads
the "tests" file -- fix the empty "tests" file?
> That box is built with "useithreads=define", so it's not that it doesn't
> support threading in general.
