Bug#1015132: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function'
On Sat, 16 Jul 2022 20:55:02 +0200 Lucas Nussbaum wrote:
> Hi,
>
> The script I use to extract the failure from the log might have guessed
> badly indeed, however the build still fails, as shown by the full log
> linked in the bug:
> http://qa-logs.debian.net/2022/07/16/meson_0.63.0-1_unstable.log
> SO I wouldn't call that a "spurious failure".
>
> However looking at the log I don't really understand why the
> override_dh_auto_test target fails. Can you explain? Maybe I can improve
> my script.
>
> Lucas
The testsuite has two parts. The first part (that actually fails in this
case) is a standard python-unittest run, and presumably you have
heuristics that can catch that.
The second part is a very custom setup, you'll undoubtedly need to
manually code support for it. Since Debian includes the environment
variable $MESON_PRINT_TEST_OUTPUT for extra extra extra debug spew, it
logs full configure/build/test/install output for all tests, not just
the ones that represent test failures... including, as stated above,
passing tests that attempt to assert that certain things aren't expected
to work.
Let's take a look at run_project_tests.py which is driving these very
verbose tests:
class TestStatus(Enum):
OK = normal_green(' [SUCCESS] ')
SKIP = yellow(' [SKIPPED] ')
ERROR = red(' [ERROR] ')
UNEXSKIP = red('[UNEXSKIP] ')
UNEXRUN = red(' [UNEXRUN] ')
CANCELED = cyan('[CANCELED] ')
RUNNING = blue(' [RUNNING] ') # Should never be actually printed
LOG = bold(' [LOG] ') # Should never be actually printed
Individual test logs are always separated by lines beginning with the
string " [XXX]".
error, unexskip, and unexrun are the only failure states.
unexskip and unexrun can only happen in Meson's internal CI
($MESON_CI_JOBNAME is set and isn't "thirdparty").
So you can just filter for:
- any python-unittest matching logs (e.g. in between "===" and
"\nRan tests in s")
- anything in between " [ERROR]" and " []"
--
Eli Schwartz
Bug#1015132: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function'
On 16/07/22 at 22:17 +0300, Jussi Pakkanen wrote: > On Sat, 16 Jul 2022 at 17:04, Lucas Nussbaum wrote: > > > Relevant part (hopefully): > > > /usr/bin/ld: bobuser.p/bobuser.c.o: in function `main': > > > ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: > > > undefined reference to `hidden_function' > > > collect2: error: ld returned 1 exit status > > This is the second time (at least) that this issue has been > incorrectly reported. This is not a test failure. As you can tell the > test name has "failing build" in it, which means that failing to > compile is the correct behaviour. If this report has been done by > hand, please in the future report the thing that actually failed (if > any). If this is an automated test then please fix it to not report > spurious failures like this. Hi, The script I use to extract the failure from the log might have guessed badly indeed, however the build still fails, as shown by the full log linked in the bug: http://qa-logs.debian.net/2022/07/16/meson_0.63.0-1_unstable.log SO I wouldn't call that a "spurious failure". However looking at the log I don't really understand why the override_dh_auto_test target fails. Can you explain? Maybe I can improve my script. Lucas
Bug#1015132: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function'
On Sat, 16 Jul 2022 at 17:04, Lucas Nussbaum wrote: > Relevant part (hopefully): > > /usr/bin/ld: bobuser.p/bobuser.c.o: in function `main': > > ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: > > undefined reference to `hidden_function' > > collect2: error: ld returned 1 exit status This is the second time (at least) that this issue has been incorrectly reported. This is not a test failure. As you can tell the test name has "failing build" in it, which means that failing to compile is the correct behaviour. If this report has been done by hand, please in the future report the thing that actually failed (if any). If this is an automated test then please fix it to not report spurious failures like this. Thanks,
Bug#1015132: meson: FTBFS: ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: undefined reference to `hidden_function'
Source: meson Version: 0.63.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: bobuser.p/bobuser.c.o: in function `main': > ./b 52a78b9866/../test cases/failing build/2 hidden symbol/bobuser.c:4: > undefined reference to `hidden_function' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2022/07/16/meson_0.63.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220716=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
