| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Having these named differently than the test itself mostly creates
unecessary confusion and makes writing logic against the tests harder
so let's rename the testsuite-xx units and scripts to just use the
test name itself.
|
| |
|
|
|
|
|
| |
TEST-23 uses run_subtests_with_signals() which I forgot about when
introducing the change.
Follow-up for 0efa27bd4b.
|
| | |
|
| |
|
|
| |
To make debugging slightly easier.
|
| |
|
|
|
|
|
| |
Let's take a step back and revert back to the original behavior where we
exit on a first failing subtest. The current behavior makes fishing out the
failing test details quite unpleasant, and in certain situations the
journal may even be rotated away so we end up with no actionable logs.
|
| |
|
|
|
|
|
|
| |
Useful when debugging, e.g.:
make -C test/TEST-74-AUX-UTILS clean setup run TEST_MATCH_SUBTEST=run
Resolves: #27914
|
| |
|
|
|
|
| |
Since bash has no namespaces, let's do the second best thing and prefix
all "internal" stuff with an underscore, to minimize the chance of a name
conflict in the future.
|
| | |
|
|
|
Also, instead of bailing out on the first failed subtest, always run all
subtests and print a summary at the end (with an appropriate exit code).
|
