From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 0/5] Run tests in CI
Date: Wed, 30 Jun 2021 00:20:12 +0200 [thread overview]
Message-ID: <YNucnE+N98zmKmWN@pevik> (raw)
In-Reply-To: <20210629214808.18760-1-pvorel@suse.cz>
Hi,
> Hi all,
> changes v2->v3:
> * going back to simplest changes in make
> * adding lib/newlib_tests/runtest.sh (instead fighting with our build
> system I concentrated on runtest.sh)
> * removing tst_fuzzy_sync01 as it sporadically fails
> Tested:
> https://github.com/pevik/ltp/actions/runs/984224611
> TODO: Not what's wrong with PATH on CentOS 7:
> /__w/ltp/ltp/lib/newlib_tests/runtest.sh: line 78: ./test05: No such file or directory
> ./shell/net/../../../../testcases/lib/tst_test.sh: line 149: tst_rod: command not found
> Maybe it's in different directory?
> It uses old make 3.82, there is something incompatible.
OK, whole out-of-tree build is broken. There are 2 issues:
1) probably PATH ../../testcases/lib/ points to srcdir instead of build dir).
It's just older make exit properly with 2, newer don't, not sure why.
2) The same issue with non-zero exit not being propagated on newer make
is also when runtest.sh quits with:
runtest TFAIL: shell/net/tst_ipaddr_un.sh failed with TFAIL
I guess I need to use @set -e; in Makefile (I didn't want to use set -e in the
runtest.sh itself, it would break printing printing what failed).
Kind regards,
Petr
prev parent reply other threads:[~2021-06-29 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 21:48 [LTP] [PATCH v3 0/5] Run tests in CI Petr Vorel
2021-06-29 21:48 ` [LTP] [PATCH v3 1/5] tst_device: Require root Petr Vorel
2021-06-29 21:48 ` [LTP] [PATCH v3 2/5] lib: Add script for running tests Petr Vorel
2021-06-29 21:48 ` [LTP] [PATCH v3 3/5] make: Add make test{, -c, -shell} targets Petr Vorel
2021-06-29 21:48 ` [LTP] [PATCH v3 4/5] build.sh: Add support for make test Petr Vorel
2021-06-29 21:48 ` [LTP] [PATCH v3 5/5] CI: Run also " Petr Vorel
2021-06-29 22:20 ` Petr Vorel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YNucnE+N98zmKmWN@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox