-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ppc64le: Tests failed (2): <no-mmap-inval.t> <reg-fd-only.t> #1207
Comments
Also, the same version suddenly got on
|
Test for IORING_FEAT_RECVSEND_BUNDLE before setting up the connection thread, or we could be tearing down pthread data at inopportune moments leading to odd behavior. Link: #1207 Fixes: 184e6ec ("test/accept-non-empty: add accept IORING_CQE_F_SOCK_NONEMPTY test") Signed-off-by: Jens Axboe <[email protected]>
Pushed a fix for accept-non-empty, that was a bug in the test. For ppc64, the -ENOENT for mmap-no-inval is very (very) odd. For reg-fd-only, I'll push a commit to dump 'ret'. Can you try and re-run it? I'm wondering what it's returning. Maybe both are the same arch odditiy and it'll be -ENOENT?! |
Link: #1207 Signed-off-by: Jens Axboe <[email protected]>
Thanks. Now with ebd6c8f it failed only on ppc64le (and i586 where is usually exclude
|
...
It's UDP for which we "expect" 65536 bytes in a datagram, more than usually supported by UDP. Looks the test wasn't prepared for 16K pages.
|
JFYI, two tests fail on ppc64 on Linux v6.6.46 for liburing-2.7. They succeed or skipped on x86_64.
On x86_64:
The text was updated successfully, but these errors were encountered: