libuv: disable thread_affinity test #378448
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Please don't delete the template. |
|
@ofborg build libuv |
|
Should I rebase to staging? I'm not sure why label-pr did not mark this as a large rebuild as in #364055. This change does cause most of my system to rebuild. |
|
yes please |
Pleune
force-pushed
the
libuv-no-thread-afffinity
branch
from
e0e95df to
dab4611
Compare
ofborg
bot
added
2.status: merge conflict
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #378438
libuv includes a test which specifically requires thread-affinity to be unset, or else you get an error:
# Assertion failed in test/test-thread-affinity.c on line 73: cpumask[0] && "test must be run with cpu 0 affinity"I assume that packages should be able to be built regardless of affinity, so this test should not be run.
Add a 👍 reaction to pull requests you find important.