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
gdimagecopyresampled/bug00201 fails on some arch #364
Comments
|
Can you please post the _out and _diff images and the log entry? |
|
Not easily, I need a real computer (these build are run in Fedora infra, and I don't have access to the build tree) |
|
I have an access to porter boxes on Debian, but it seems that Debian is ok on all archs: https://buildd.debian.org/status/package.php?p=libgd2 Perhaps again related to the underlying libraries versions? |
|
Fixed by b7b66ea (don't know why this wasn't applied in 2.2...) |
|
Hello, FAIL: gdimagecopyresampled/bug00201 gdimagecopyresampled/bug00201;echo $?gdimagecopyresampled/bug00201.c:68: Total pixels changed: 199 with a maximum channel difference of 255. Bye |
|
@rainer-tammer I don't have PPC64 to test sadly and sorry for the delay, I missed that comment. Would it be possible to have an access to debug? Or even better, to have our CI github action using it :) |
|
@remicollet would it be possible to run the gh action runner on this PPC64? ARM is covered now (Graviton/Neon) |
|
I filled a request at OSUSL initiative, let see. Power9. That could help :) |
|
i might be able to get you an acct on a Gentoo box for ppc. hopefully i'll have info in the next week. if it comes up, i can get you access to an s390 system at any time. |
|
@vapier excellent! Thank you! I can then add the github action bots on it and we will have it as part of our CI :) |
|
some of the issues on aarch64, for what I see are:
|
|
i don't think we can use it for hosting GH actions. i meant more as a dev box for you to debug reports and experiment and such. |
|
that's already very good then :).
especially for the standard floating to int/chat and other fp modes.
…On Sun, Sep 12, 2021, 10:55 AM Mike Frysinger ***@***.***> wrote:
i don't think we can use it for hosting GH actions. i meant more as a dev
box for you to debug reports and experiment and such.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#364 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACE6KEF6GH5REWYHULUDPDUBQQBVANCNFSM4C44HC7Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Thanks to openpower@unicamp, it looks like we will have a ppc64 for debugging and ci soon, just got the credentials |
|
Hello, Currently there is unfortunately no direct access from the Internet. Bye |
|
Hi Rainer
thank you :))
As far as I can see, the gh agent pull the jobs from gh and does not need
to be accessible from internet. Is it something that could be done?
…On Mon, Sep 13, 2021, 8:52 PM rainer-tammer ***@***.***> wrote:
Hello,
I can run some tests on AIX 7.2 / 7.1.
Currently there is unfortunately no direct access from the Internet.
I might be able to setup a AIX 7.1 LPAR in needed. I could provide limited
access to this LPAR.
Bye
Rainer
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#364 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACE6KGLKIIYEIIABDGEKRTUBX6YBANCNFSM4C44HC7Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Ok on i386, x86_64, armv7hl
Fails on ppc64, ppc64le, aarch64
(probably, yet another rouding issue)
The text was updated successfully, but these errors were encountered: