fe722c7b02
The oomparser logic would end up stuck, unable to detect the end of a given oom trace, for any process with a name that didn't match \w+. This includes processes like 'python3.4' due to the '.', or 'docker-containerd' due to the '-'. This fix was included in pr #1544 last year, but since that PR seems dead it seems like a good idea to break this more important fix out. I've updated the tests such that they would have caught this issue. |
||
|---|---|---|
| .. | ||
| oomexample | ||
| containerOomExampleLog.txt | ||
| oomparser_test.go | ||
| oomparser.go | ||
| systemOomExampleLog.txt | ||