[MDBF-34] Fix intermittent SIGPIPE killing MTR Created: 2020-04-30 Updated: 2022-02-05 Due: 2020-07-15 Resolved: 2022-02-05 |
|
| Status: | Closed |
| Project: | MariaDB Foundation Development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Task | Priority: | Major |
| Reporter: | Kaj Arnö | Assignee: | Vlad Bogolin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | buildbot, foundation | ||
| Remaining Estimate: | 4.25d | ||
| Time Spent: | 0.75d | ||
| Original Estimate: | 5d | ||
| Issue Links: |
|
||||||||||||
| Description |
|
SIGPIPE sometimes issued for unknown reason, killing MTR MariaDB Test Run There are some cases when SIGPIPE kills the buildbot processes. May be related to special characters produced by MTR for which Vlad found a buildbot issue (https://github.com/buildbot/buildbot/issues/4267). Otherwise, adding a signal handler to MTR needs to be done (as Marko suggested) |
| Comments |
| Comment by Vlad Bogolin [ 2020-05-04 ] |
|
This is a tricky bug to catch which would be probably easy to solve once the problem is clear. At this point I have two ways to go through: 1) assure no special characters appear in MTR log; 2) add some signal handles to see who sends the SIGPIPE and build from there. If you have any other suggestions please share. |
| Comment by Michael Widenius [ 2020-06-18 ] |
|
I have a hard time to think that special characters could cause that. If that would be the case, you have always the logs from failing tests that you can check for any special characters. |