Bug 1424433
| Summary: | shiboken: flaky test on armv7hl (FTBFS in F26) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
| Component: | shiboken | Assignee: | Felix Schwarz <fschwarz> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 26 | CC: | fschwarz, jreznik, rdieter, than | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-07-08 13:44:23 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 1320653, 1423041 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Fedora Release Engineering
2017-02-17 17:06:37 UTC
Created attachment 1254567 [details]
build.log
Created attachment 1254568 [details]
root.log
Created attachment 1254569 [details]
state.log
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'. This really bugs me: I get regular koschei notifications. It seems like the build (more precisely: "the test suite") is a bit flaky on armv7hl. The problem is always 40/168 Test #40: other_collector_external_operator..................***Failed The most problematic thing is that the test sometimes passes (even on armv7hl): fail (June 2017): https://koji.fedoraproject.org/koji/taskinfo?taskID=19670320 pass (May 2017): https://koji.fedoraproject.org/koji/taskinfo?taskID=19670320 Not sure how we should tackle this best. PySide 1.x (and shiboken) are mostly unmaintained. A PySide developer from the QT company mentioned to me that PySide 2 contains fewer bugs than 1.x even though there is not even a beta release. Also switching to PySide 2 means users must switch to QT 5 which might not be so easy. As the arm platform seems to be a bit problematic for shiboken/PySide and I never read a bug report about ARM-specific bugs I tend to either just disable tests for PySide on ARM. However this means we basically pretend everything should be working on ARM (which I did not test at all) so the more honest thing might be to remove PySide/shiboken from Fedora on ARM... I guess I'll take one more stab at fixing the test and if I fail I'll just go ahead fixing the build - even if this means no PySide on ARM. Ah, our friends at Debian found the root cause (integer overflow) in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856133. I was able to apply that patch successfully for F26+F27 and push it this weekend. |