View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003651 | GNUnet | transport service | public | 2015-02-05 01:47 | 2024-03-13 22:30 |
Reporter | Christian Grothoff | Assigned To | schanzen | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | not fixable | ||
Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
Product Version | Git master | ||||
Target Version | 1.0.0 | ||||
Summary | 0003651: test_transport_address_switch testcases fail if no switching happens | ||||
Description | With the latest code, it is possible that while ATS 'tries' a switch, transport notices 'trouble' with the new address, tells ATS that the new address is 'bad' and sticks to the 'old' address. As a result, the connection is maintained with the original address throughout the testcase, causing it to fail. As the testcase fails to provoke a situation where an address switch should actually happen *for sure*, this is largely the testcases fault. The reason why the address switch fails is another issue (will be reported separately). | ||||
Tags | tng | ||||
|
I've changed the tests in SVN 35200 to then not fail, but as such they are then simply not testing what they are supposed to test. But that's a bug with the test. IMO we should use blacklisting or preferences/priorities to make the switch happen. |
|
Changing severity to 'feature', as this is now just a test that doesn't test something properly. |
|
This does does not apply/exist anymore |
Date Modified | Username | Field | Change |
---|---|---|---|
2015-02-05 01:47 | Christian Grothoff | New Issue | |
2015-02-05 01:47 | Christian Grothoff | Status | new => assigned |
2015-02-05 01:47 | Christian Grothoff | Assigned To | => Matthias Wachs |
2015-02-09 00:18 | Christian Grothoff | Priority | normal => urgent |
2015-02-09 17:07 | Christian Grothoff | Note Added: 0008848 | |
2015-02-09 17:07 | Christian Grothoff | Priority | urgent => normal |
2015-02-11 00:32 | Christian Grothoff | Relationship added | child of 0003448 |
2015-02-11 20:06 | Christian Grothoff | Priority | normal => high |
2015-02-11 20:32 | Christian Grothoff | Assigned To | Matthias Wachs => |
2015-02-11 20:32 | Christian Grothoff | Status | assigned => confirmed |
2015-02-11 20:33 | Christian Grothoff | Relationship added | related to 0001934 |
2015-02-28 18:27 | Christian Grothoff | Note Added: 0008943 | |
2015-02-28 18:27 | Christian Grothoff | Priority | high => normal |
2015-02-28 18:27 | Christian Grothoff | Severity | crash => feature |
2015-02-28 18:32 | Christian Grothoff | Relationship deleted | child of 0003448 |
2019-05-02 14:44 | Christian Grothoff | Relationship added | related to 0005710 |
2020-08-14 12:01 | schanzen | Tag Attached: tng | |
2020-10-29 10:09 | schanzen | Target Version | => 0.15.0 |
2021-06-10 19:36 | schanzen | Target Version | 0.15.0 => 0.16.0 |
2021-12-31 09:29 | schanzen | Target Version | 0.16.0 => 0.17.0 |
2021-12-31 09:32 | schanzen | Target Version | 0.17.0 => 1.0.0 |
2024-03-13 22:30 | schanzen | Assigned To | => schanzen |
2024-03-13 22:30 | schanzen | Status | confirmed => resolved |
2024-03-13 22:30 | schanzen | Resolution | open => not fixable |
2024-03-13 22:30 | schanzen | Note Added: 0021915 | |
2024-03-13 22:30 | schanzen | Status | resolved => closed |