diff options
| author | Florian Weimer <fweimer@redhat.com> | 2024-09-19 15:40:05 +0200 |
|---|---|---|
| committer | Florian Weimer <fweimer@redhat.com> | 2024-09-21 00:29:55 +0200 |
| commit | d5a3ca4061f7adc59196fa58e34eacebbebcbcfe (patch) | |
| tree | 66ab4540001cbe3db8296a7c53f05ef2a44986f8 /stdio-common/Xprintf_buffer_flush.c | |
| parent | 83fd4149ffdae86c8864a6828f39dd942956636f (diff) | |
| download | glibc-d5a3ca4061f7adc59196fa58e34eacebbebcbcfe.zip glibc-d5a3ca4061f7adc59196fa58e34eacebbebcbcfe.tar.gz glibc-d5a3ca4061f7adc59196fa58e34eacebbebcbcfe.tar.bz2 | |
Implement run-built-tests=no for make xcheck, always build xtests
Previously, the second occurrence of the xtests target
expected all xtests to run (as the result of specifying
$(xtests)), but these tests have not been run due to
the the first xtests target is set up for run-built-tests=no:
it only runs tests in $(xtests-special). Consequently,
xtests are reported as UNSUPPORTED with “make xcheck
run-built-tests=no”. The xtests were not built, either.
After this change always, xtests are built regardless
of the $(run-built-tests) variable (except for xtests listed
in $(tests-unsupported)). To fix the UNSUPPORTED issue,
introduce xtests-expected and use that manage test
expectations in the second xtests target.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Diffstat (limited to 'stdio-common/Xprintf_buffer_flush.c')
0 files changed, 0 insertions, 0 deletions