Bug 825366 – www-client/netsurf-3.10-r4 fails tests: - make: [test/Makefile:<snip>: corestrings_test] Error 1

• Product: Gentoo Linux
• Status: CONFIRMED ---

[Description Toralf Förster 2021-11-20 20:53:53 UTC]

100%: Checks: 77, Failures: 0, Errors: 0
100%: Checks: 72, Failures: 0, Errors: 0
99%: Checks: 484, Failures: 1, Errors: 0
test/corestrings.c:60:F:corestrings:corestrings_test:483: Assertion 'ires == NSERROR_OK' failed: ires == 2, NSERROR_OK == 0
make: *** [test/Makefile:200: corestrings_test] Error 1
 * ERROR: www-client/netsurf-3.10-r4::gentoo failed (test phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=www-client/netsurf-3.10-r4::gentoo'`,

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_desktop_systemd-j4_test_debug-20211117-210104

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-11.2.0 *
/usr/lib/llvm/13
13.0.0
Python 3.9.9
Available Ruby profiles:
  [1]   ruby26 (with Rubygems)
  [2]   ruby27 (with Rubygems)
  [3]   ruby30 (with Rubygems) *
Available Rust versions:
  [1]   rust-1.56.1 *
The Glorious Glasgow Haskell Compilation System, version 8.10.4
php cli:
  [1]   php7.3
  [2]   php7.4
  [3]   php8.0 *

  HEAD of ::gentoo
commit e47a1893f1e92df14787ddd897cad1df0fa143c0
Author: Repository mirror & CI <[e-mail]>
Date:   Sat Nov 20 17:06:40 2021 +0000

    2021-11-20 17:06:39 UTC

emerge -qpvO www-client/netsurf
[ebuild  N    ] www-client/netsurf-3.10-r4  USE="duktape gif gtk javascript jpeg mng png psl svg svgtiny truetype webp -bmp -fbcon -gtk2 -rosprite"

[Comment 1 Toralf Förster 2021-11-20 20:53:55 UTC]

Created attachment 754030 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2021-11-20 20:53:57 UTC]

Created attachment 754034 [details]
emerge-history.txt

[Comment 3 Toralf Förster 2021-11-20 20:53:59 UTC]

Created attachment 754038 [details]
environment

[Comment 4 Toralf Förster 2021-11-20 20:54:00 UTC]

Created attachment 754042 [details]
etc.portage.tar.bz2

[Comment 5 Toralf Förster 2021-11-20 20:54:01 UTC]

Created attachment 754046 [details]
temp.tar.bz2

[Comment 6 Toralf Förster 2021-11-20 20:54:03 UTC]

Created attachment 754050 [details]
www-client:netsurf-3.10-r4:20211120-172617.log

[Comment 7 Agostino Sarubbo 2022-02-13 10:12:58 UTC]

Update summary. [something] is used when something refers to an overlay

[Comment 8 Michael Orlitzky 2023-08-15 01:21:54 UTC]

This is a malloc() test that should be succeeding but instead returned "no memory."

This number,

  #define CORESTRING_TEST_COUNT 483

in the test is set to exactly the number of malloc() calls needed to run corestrings_init(). The test first loops 483 times, setting a limit of between 0 and 482 malloc calls before trying to call corestrings_init(). They all fail with "no memory," because we aren't allowed to run the real malloc() enough times and the wrapper is designed to fail when the limit is exceeded.

But then the last iteration of the test (the 484th) allows 483 mallocs. The call to corestrings_init() should then succeed, because the fake malloc limit shouldn't get in the way. Except in your case it still failed somehow.

>  Assertion 'ires == NSERROR_OK' failed: ires == 2, NSERROR_OK == 0

2 is NSERROR_NOMEM


I guess you could have run out of memory at a very bad time? If the real malloc() fails, the test would fail in that way. Anyway, that's what's happening, but who knows why.