diff options
| author |   Sam James <sam@gentoo.org> | 2024-02-18 09:48:09 +0000 |
|---|---|---|
| committer | Sam James <sam@gentoo.org> | 2024-02-18 09:49:43 +0000 |
| commit | 7ab66de3c35d5310271b9b805543d375aea82b0d (patch) | |
| tree | dc8a6b6110a4257f469b12d04f98fb5f43da218f /app-portage/pfl/pfl-3.2.1.ebuild | |
| parent | sec-keys/openpgp-keys-libuv: update Manifest, style tweaks, missing dies (diff) | |
| download | gentoo-7ab66de3c35d5310271b9b805543d375aea82b0d.tar.gz gentoo-7ab66de3c35d5310271b9b805543d375aea82b0d.tar.bz2 gentoo-7ab66de3c35d5310271b9b805543d375aea82b0d.zip | |
dev-libs/libuv: skip part of thread_priority test
Part of the (newly-introduced) thread_priority test doesn't interact well
with PORTAGE_NICENESS, (maybe) PORTAGE_IONICE_COMMAND, and PORTAGE_SCHEDULING_POLICY.
For example, with PORTAGE_NICENESS="18", PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}",
and PORTAGE_SCHEDULING_POLICY="idle", I get:
```
not ok 354 - thread_priority
exit code 134
Output from process `thread_priority`:
Assertion failed in test/test-thread-priority.c on line 95: `priority == (0 - UV_THREAD_PRIORITY_LOWEST * 2)` (0 == 4)
```
Skip that one assertion accordingly.
And while at it, elaborate on a bit of m4 hackery we do in the ebuild.
Closes: https://bugs.gentoo.org/924653
Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'app-portage/pfl/pfl-3.2.1.ebuild')
0 files changed, 0 insertions, 0 deletions