-
-
Notifications
You must be signed in to change notification settings - Fork 141
Open
Labels
Milestone
Description
See for instance https://github.com/dankamongmen/notcurses/actions/runs/12726507286/job/35474975934#step:6:44 (a 3.0.12-dirty buid):
est project /Users/runner/work/notcurses/notcurses/build
12 Start 1: notcurses-tester
13 1/10 Test #1: notcurses-tester .................***Timeout 1500.06 sec
14 Start 2: notcurses-info
15 2/10 Test #2: notcurses-info ................... Passed 0.06 sec
16 Start 3: ncpp_build
17 3/10 Test #3: ncpp_build ....................... Passed 0.05 sec
18 Start 4: ncpp_build_exceptions
19 4/10 Test #4: ncpp_build_exceptions ............ Passed 0.04 sec
20 Start 5: input-devnull
21 5/10 Test #5: input-devnull .................... Passed 0.31 sec
22 Start 6: input-text
23 6/10 Test #6: input-text ....................... Passed 0.36 sec
24 Start 7: sgr-direct
25 7/10 Test #7: sgr-direct ....................... Passed 0.06 sec
26 Start 8: sgr-full
27 8/10 Test #8: sgr-full ......................... Passed 0.05 sec
28 Start 9: rgb
29 9/10 Test #9: rgb .............................. Passed 0.05 sec
30 Start 10: rgbbg
3110/10 Test #10: rgbbg ............................ Passed 0.05 sec
32
33 90% tests passed, 1 tests failed out of 10
34
35 Total Test time (real) = 1501.18 sec
36
37 The following tests FAILED:
38 1 - notcurses-tester (Timeout)
39 Errors while running CTest
40 Output from these tests are in: /Users/runner/work/notcurses/notcurses/build/Testing/Temporary/LastTest.log
41 Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
42 make: *** [test] Error 8
43 Error: Process completed with exit code 2.
so there are two problems here: we ought rerun with --output-on-failure in the CI, to have more info on this kind of thing. two, we're seeing this timeout. i think i've seen it locally, too, though i thought it was one of the input test programs. maybe it's a general problem? either way, let's get this figured out.