i've tried running the tests, and regressions from 829 onwards are timing out
it works fine for me here
https://hastebin.com/ejokomojaf
hmm... ok, then the error is on my end. thanks
i tried running the tests, and the rtwizard regressions fail (853 to 859, from A to F + edge only)
yes, and I confirmed they fail too a while back. they look like genuine regressions that somehow only affect mac
are you referring to our previous discussion? because then, only D was failing. the others were fine
ah, good point -- the disease is spreading
the new ones may be unrelated, will have to check them
I still have those regression failures from months ago and I'm on Linux
rtwizard regressions? or others? also, what linux + compiler?
$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/8.1.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release --enable-default-pie --enable-default-ssp Thread model: posix gcc version 8.1.1 20180531 (GCC)
The following tests FAILED: 1 - NOTE: some 'test' tests are expected to fail, 'regress' must pass (Failed) 824 - regress-solids (Failed) 828 - regress-weight (Failed) 831 - regress-usage (Timeout) 853 - regress-rtwizard-rtwiz_m35_A (Timeout) 854 - regress-rtwizard-rtwiz_m35_B (Timeout) 855 - regress-rtwizard-rtwiz_m35_C (Timeout) 856 - regress-rtwizard-rtwiz_m35_D (Timeout) 857 - regress-rtwizard-rtwiz_m35_E (Timeout) 858 - regress-rtwizard-rtwiz_m35_F (Timeout) 859 - regress-rtwizard-rtwiz_m35_edge_only (Timeout) 860 - regress-rtwizard-rtwiz_m35_edge_only_color (Timeout)
i could try it with Clang if necessary
you can try to ctest -V -I 831,831
for example, to get more info on why 831 is timing out
in r71347, rt
was made to return 0 when (extended?) usage is printed, causing regress-usage
to fail (it expects rt -?
to have exit code 1). i changed rt
to return 1 when the extended usage is printed, but i'm not sure if this is the way to go (if i should've changed the test instead)
some tests are failing on my computer (814, 817, 822). i've traced the problem to running make sph sph
inside mged
. i've traced the problem to mged/chgmodel.c:f_make
, which expands the command to make -o -0 -0 -0 -s 1000 sph sph
. after that, ged_make
tries to parse -o
and expects an argument to -o
, but then sees that -0
starts with a minus and thinks that -o
received no arguments
i don't know why the tests are failing now (a few weeks ago they did not), and i don't know what the proper fix is. what i did was to remove the -
from sprintf
in f_make
, but there are other places in the code which also put the minus there, and i think minus goes in the opposite direction, so it changes the logic if you remove it
in r71347,
rt
was made to return 0 when (extended?) usage is printed, causingregress-usage
to fail (it expectsrt -?
to have exit code 1). i changedrt
to return 1 when the extended usage is printed, but i'm not sure if this is the way to go (if i should've changed the test instead)
I think the test should be updated. The user requested help and the tool did exactly that, no error. Non-zero is supposed to imply something went wrong, not just whenever usage is printed.
some tests are failing on my computer (814, 817, 822). i've traced the problem to running
make sph sph
insidemged
. i've traced the problem tomged/chgmodel.c:f_make
, which expands the command tomake -o -0 -0 -0 -s 1000 sph sph
. after that,ged_make
tries to parse-o
and expects an argument to-o
, but then sees that-0
starts with a minus and thinks that-o
received no arguments
@Cezar that failure is my fault, I'm working on it -- support was added for optional commands but it affected other behavior.
unit tests are doing their job :)
just FYI, looks like I'm finally getting to the bottom of the apparent rabbit hole fixing the integration issues of recent. there's still an issue that affects my testing on linux, but I should have the regression failures knocked back out soon, this week.
:tada:
@Sean I know there's been a lot going on - just curious where the regression fixes are in the queue?
@starseeker they're top of the queue now that last week is done, so my fingers are crossed for knocking them out
Last updated: Jan 09 2025 at 00:46 UTC