Skip to content
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

ray and simd tests fail on i686 #246

Open
amigadave opened this issue Mar 21, 2022 · 1 comment
Open

ray and simd tests fail on i686 #246

amigadave opened this issue Mar 21, 2022 · 1 comment

Comments

@amigadave
Copy link

While updating the Fedora packaging for the 1.10.8 release, I came across a test failure on i686:

+ /usr/bin/meson test -C redhat-linux-build --num-processes 6 --print-errorlogs
ninja: Entering directory `/builddir/build/BUILD/graphene-1.10.8/redhat-linux-build'
ninja: no work to do.
 1/22 mutest / general            OK              0.03s
 2/22 mutest / hooks              OK              0.02s
 3/22 mutest / types              OK              0.02s
 4/22 graphene / box              OK              0.02s   65 subtests passed
 5/22 graphene / euler            OK              0.02s   10 subtests passed
 6/22 graphene / frustum          OK              0.01s   21 subtests passed
 7/22 graphene / matrix           OK              0.03s   70 subtests passed
 8/22 graphene / plane            OK              0.02s   13 subtests passed
 9/22 graphene / point            OK              0.02s   24 subtests passed
10/22 graphene / point3d          OK              0.02s   36 subtests passed
11/22 graphene / quad             OK              0.02s   12 subtests passed
12/22 graphene / quaternion       OK              0.01s   24 subtests passed
▶ 13/22 - intersection kind should be NONE FAIL          
▶ 14/22 - reciprocal() to return positive infinity in the X component FAIL          
▶ 14/22 - reciprocal() to return negative infinity in the Y component FAIL          
13/22 graphene / ray              ERROR           0.03s   exit status 1
>>> MALLOC_PERTURB_=116 MUTEST_OUTPUT=tap /builddir/build/BUILD/graphene-1.10.8/redhat-linux-build/tests/ray
――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
stderr:
(test program exited with status code 1)
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
15/22 graphene / rect             OK              0.03s   69 subtests passed
14/22 graphene / simd             ERROR           0.03s   exit status 1
>>> MALLOC_PERTURB_=122 MUTEST_OUTPUT=tap /builddir/build/BUILD/graphene-1.10.8/redhat-linux-build/tests/simd
――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
stderr:
(test program exited with status code 1)
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
16/22 graphene / size             OK              0.02s   17 subtests passed
17/22 graphene / sphere           OK              0.02s   17 subtests passed
18/22 graphene / triangle         OK              0.02s   56 subtests passed
19/22 graphene / vec2             OK              0.02s   37 subtests passed
20/22 graphene / vec3             OK              0.02s   51 subtests passed
21/22 graphene / vec4             OK              0.01s   63 subtests passed
22/22 graphene / introspection.py OK              0.08s   1 subtests passed
Summary of Failures:
13/22 graphene / ray              ERROR           0.03s   exit status 1
14/22 graphene / simd             ERROR           0.03s   exit status 1
Ok:                 20  
Expected Fail:      0   
Fail:               2   
Unexpected Pass:    0   
Skipped:            0   
Timeout:            0

The full build log is https://kojipkgs.fedoraproject.org//work/tasks/7875/84387875/build.log but I do not have an i686 machine around to test, sadly. I think that I can get access to a test system to try to get some artifacts out of a build, if that would be useful.

@ebassi
Copy link
Owner

ebassi commented Jan 23, 2024

I don't have a 32bit machine either, unfortunately, so support for 32bit architectures is similar to the support for ARM NEON: a best effort.

I also assume that this was with the scalar implementation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants