fix TestSetOOMScoreBoundaries and replace missing busybox image in CI#5321
fix TestSetOOMScoreBoundaries and replace missing busybox image in CI#5321crosbymichael merged 2 commits intocontainerd:masterfrom
Conversation
```bash curl -s https://mirror.gcr.io//v2/library/busybox/tags/list | jq '[.tags ]' [ [ "1.26.2", "1.27.2", "1.28", "1.29", "1.29.2", "1.30", "1.30.1", "1.31", "1.31.0", "1.31.1", "1.32.0" ] ] ``` The latest is gone. I think we should setup image in github container registry for CI if possible. Signed-off-by: Wei Fu <[email protected]>
|
@fuweid @AkihiroSuda @mxpv ptal |
|
I think CI will unhappy 😂 @thaJeztah Would you mind to add my commit from #5320 in this pr? Thanks |
|
Build succeeded.
|
Yeah... no surprise |
Ah, yes, I anticipated that; let me rebase my PR on top of yours |
(this was introduced in 4424011) Setting the oom-score-adj to -1000 is only possible if the parent process either has no score set, or if the score is set to -1000. However, the current implementation of GetOOMScoreAdj conflates situations where either _no_ oom-score is set, _or_ oom-score is set, but set to 0. In the latter case, the test would fail: --- FAIL: TestSetOOMScoreBoundaries (0.01s) oom_linux_test.go:79: assertion failed: 0 (adjustment int) != -1000 (OOMScoreAdjMin int) FAIL To prevent failures in this situation, skip that part of the test in the above situation. Also update the description of GetOOMScoreAdj to clarify its behavior. Signed-off-by: Sebastiaan van Stijn <[email protected]>
1cc3b72 to
3d20fa9
Compare
|
Rebased to include #5320 (merging this PR will merge both) |
|
Build succeeded.
|
|
And now it's failing on the next image 😞
Update: ☝️ is a known flaky / race condition, and not related to the gcr.io image |
|
Build succeeded.
|
|
Another flaky? (is it state not cleaned up somewhere?) details below Details |
|
Build succeeded.
|
|
yay! green now |
Sorry; missed both of those comments; I'll try to think of fixing that separately (or wait for a contributor to open a "fix typo" PR); getting CI working is the important bit 👍 |
updates / closes #5320
Introduced in 4424011 / #5253
To address the failure described in #5320 (comment)
Setting the oom-score-adj to -1000 is only possible if the parent process
either has no score set, or if the score is set to -1000.
However, the current implementation of GetOOMScoreAdj conflates situations
where either no oom-score is set, or oom-score is set, but set to 0.
In the latter case, the test would fail:
To prevent failures in this situation, skip that part of the test in the
above situation.
Also update the description of GetOOMScoreAdj to clarify its behavior.
Signed-off-by: Sebastiaan van Stijn [email protected]