View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009814 | Taler | taler-harness | public | 2025-04-29 15:34 | 2025-06-08 20:21 |
| Reporter | Florian Dold | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | confirmed | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0009814: harness tests should clean up processes more thoroughly after test failure | ||||
| Description | This must be done in the test runner. Due to limitations of NodeJS, the test worker can't reliably SIGKILL processes when SIGTERM doesn't end them. Maybe with the following approach: * harness worker writes PIDs of running processes to the test directory * harness test runner cleans up those processes | ||||
| Tags | debt | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-04-29 15:34 | Florian Dold | New Issue | |
| 2025-04-29 16:14 | Florian Dold | Summary | harness tests should clean better after test failure => harness tests should clean up processes better after test failure |
| 2025-04-29 16:14 | Florian Dold | Description Updated | |
| 2025-04-29 16:15 | Florian Dold | Summary | harness tests should clean up processes better after test failure => harness tests should clean up processes more thoroughly after test failure |
| 2025-04-30 16:14 | Christian Grothoff | Status | new => confirmed |
| 2025-05-08 21:54 | Christian Grothoff | Target Version | 1.0 stretch goals => post-1.0 |
| 2025-06-08 20:21 | Christian Grothoff | Tag Attached: debt |
