View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005117 | GNUnet | build process | public | 2017-08-09 23:12 | 2018-06-07 00:55 |
| Reporter | nikita | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | won't fix | ||
| Platform | x86_64 | OS | GuixSD | OS Version | git HEAD |
| Product Version | Git master | ||||
| Fixed in Version | 0.11.0pre66 | ||||
| Summary | 0005117: FAIL: test_ats_api_mlp | ||||
| Description | During build this test fails. | ||||
| Steps To Reproduce | With Guix: git clone https://gitweb.krosos.org/ng0_guix/packages.git/ and set it up accordingly to README. Happens with a run of "guix build gnunetgft" which builds a full gnunet with all dependencies and tests. | ||||
| Tags | No tags attached. | ||||
| Attached Files | test-suite.log (2,329 bytes)
=========================================== gnunet 0.10.1: src/ats/test-suite.log =========================================== # TOTAL: 4 # PASS: 3 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test_ats_api_mlp ====================== Aug 09 21:01:44-806134 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-806197 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-812909 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-812947 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-821709 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-821748 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-834447 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-834486 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-855276 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-855317 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-892071 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-892111 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-960900 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:44-960946 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:45-094411 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:45-094448 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:45-355394 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:45-355435 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:45-872614 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:45-872656 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:46-902287 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:46-902328 test-ats-api-19079 ERROR Connection to ATS died, likely a crash! Aug 09 21:01:47-786257 test-ats-api-19079 ERROR Test failed at stage 18 FAIL test_ats_api_mlp (exit status: 2) | ||||
| related to | 0005076 | closed | Matthias Wachs | Test failure: test_ats_api_mlp |
|
|
As of 87ecda14a0c2a643c4f814b6603ae2cad207a218 this is still the case: FAIL: test_ats_api_mlp ====================== Sep 27 08:18:16-043274 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-043350 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-049943 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-049980 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-058695 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-058737 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-071524 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-071567 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-092412 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-092454 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-129280 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-129324 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-198114 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-198159 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-331028 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-331071 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-591969 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:16-592006 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:17-109257 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:17-109294 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:18-138832 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:18-138870 test-ats-api-19291 ERROR Connection to ATS died, likely a crash! Sep 27 08:18:19-023611 test-ats-api-19291 ERROR Test failed at stage 18 FAIL test_ats_api_mlp (exit status: 2) |
|
|
Does this by any chance assume that a connection or any network interaction can happen? If this is the case, I can simply work on skipping the relevant tests in ATS for Guix (OT: It would be really good if there would be a way to check for guix, so we know that certain tests can only fail. Right now this is impossible within Guix.). Working on this would be much easier with an "how to debug GNUnet tests" in some place (hint: documentation). At the moment I just read code. Assigning this to you Christian as only you have been active in 'src/ats/'. |
|
|
Well, this 'mlp' solver has not been working for a very long time. I'm pretty sure it is simply a bug in the code, and not the network connectivity. Anyway, I consider 'mlp' experimental (at best) and not release-critical. |
|
|
Okay. Since this is known to fail, shouldn't we write a case in src/ats/Makefile.am which needs to be passed to run this specific test (or all like it)? Like: if HAVE_TESTING TESTING_TESTS = \ test_ats_api_proportional \ test_ats_reservation_api_proportional if HAVE_EXPERIMENTAL TESTING_TESTS += \ test_ats_api_ril if HAVE_BROKEN_TESTCASES if HAVE_LIBGLPK TESTING_TESTS += \ test_ats_api_mlp endif endif endif endif with the if HAVE_BROKENTESTCASES I'm not yet that safe in autotools, but the idea is to configure with --enable-brokentestcases and you'd get the tests which are known to be failing, otherwise you don't. This makes us build experimental features, but also makes it possible to isolate and stress out which ones have problems we need to fix, excluding them from the default set of tests. WDYT? |
|
|
Well, actually that is the point of the --enable-experimental option ;-) |
|
|
Okay. (I just forgot that 'experimental' is supposed to fail, regarded it from an "experimental content, not tests" perspective) |
|
|
Changing to won't fix, as ATS subsystem will need a major rewrite first anyway. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-08-09 23:12 | nikita | New Issue | |
| 2017-08-09 23:12 | nikita | File Added: test-suite.log | |
| 2017-08-11 15:55 | nikita | Steps to Reproduce Updated | |
| 2017-09-27 10:21 | nikita | Note Added: 0012440 | |
| 2017-09-27 10:29 | nikita | Note Added: 0012441 | |
| 2017-09-27 10:30 | nikita | Note Edited: 0012441 | |
| 2017-09-27 10:32 | nikita | Note Edited: 0012441 | |
| 2017-09-27 10:33 | nikita | Assigned To | => Christian Grothoff |
| 2017-09-27 10:33 | nikita | Status | new => assigned |
| 2017-09-27 10:33 | nikita | Note Edited: 0012441 | |
| 2017-09-27 10:38 | nikita | Note Edited: 0012441 | |
| 2017-09-27 11:33 | Christian Grothoff | Note Added: 0012442 | |
| 2017-09-27 11:34 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2017-09-27 11:34 | Christian Grothoff | Status | assigned => confirmed |
| 2017-09-27 16:27 | nikita | Note Added: 0012450 | |
| 2017-09-27 16:38 | nikita | Note Edited: 0012450 | |
| 2017-09-27 16:57 | Christian Grothoff | Note Added: 0012451 | |
| 2017-09-27 17:03 | nikita | Note Added: 0012452 | |
| 2017-09-27 17:43 | nikita | Note Edited: 0012452 | |
| 2017-09-27 17:44 | nikita | Note Edited: 0012452 | |
| 2017-09-27 19:40 | nikita | Relationship added | related to 0005076 |
| 2018-06-07 00:55 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2018-06-07 00:55 | Christian Grothoff | Status | confirmed => closed |
| 2018-06-07 00:55 | Christian Grothoff | Resolution | open => won't fix |
| 2018-06-07 00:55 | Christian Grothoff | Fixed in Version | => 0.11.0pre66 |
| 2018-06-07 00:55 | Christian Grothoff | Note Added: 0012995 |
