Summary: | sys-process/procps-3.3.16 fails tests: FAIL: ps SCHED_BATCH scheduler | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | matoro_bugzilla_gentoo, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 916095 | ||
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tbz2 logs.tbz2 sys-process:procps-3.3.16:20200204-083947.log temp.tbz2 |
Description
Toralf Förster
2020-02-04 17:09:15 UTC
Created attachment 611570 [details]
emerge-info.txt
Created attachment 611572 [details]
emerge-history.txt
Created attachment 611574 [details]
environment
Created attachment 611576 [details]
etc.portage.tbz2
Created attachment 611578 [details]
logs.tbz2
Created attachment 611580 [details]
sys-process:procps-3.3.16:20200204-083947.log
Created attachment 611582 [details]
temp.tbz2
I only get this error when the package is emerged with SCHED_IDLE scheduling policy, i.e. via PORTAGE_IONICE_COMMAND="chrt -i -p 0 \${PID}" commenting that out / creating a seperate package.env fixes it - looks to me like the sched_batch test fails if it's not started as SCHED_RR tested with both 3.3.15-r1 and 3.3.16-r2 Update summary. [something] is used when something refers to an overlay Is there any way to restrict PORTAGE_SCHEDULING_POLICY on a per-ebuild basis? Even if it's just a bail-out in pkg_setup etc? |