From Fedora Project Wiki
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Work Queue ==
== Work Queues ==
This is the central point where work on build failures is organized, you can find here a list of failed builds, list of actual tasks and who works on them.
This is the central point where work on build failures is organized. You can find on following specific pages a list of failed builds, list of actual tasks and who works on them.


== Failed builds ==
PowerPC Work Queue for [[Architectures/PowerPC/WorkQueue_for_Fedora_21|Fedora 21]].
* failed builds between 2014-06-23 and 2014-07-04 = http://fedora.danny.cz/ppc/20140704-ppc-failed.txt


== Tracker bugs ==
PowerPC Work Queue for [[Architectures/PowerPC/WorkQueue_for_Fedora_22|Fedora 22]].  
* ppc/ppc64 = https://bugzilla.redhat.com/show_bug.cgi?id=1071880
* ppc64le = https://bugzilla.redhat.com/show_bug.cgi?id=1051573
* alpha blocker = https://bugzilla.redhat.com/show_bug.cgi?id=1140359
* alpha freeze exception = https://bugzilla.redhat.com/show_bug.cgi?id=1043122
* beta blocker = https://bugzilla.redhat.com/show_bug.cgi?id=1146697
* final blocker = https://bugzilla.redhat.com/show_bug.cgi?id=1146698
*
* test matrix = https://fedoraproject.org/wiki/F21PPC_Install_Results


== Tasks ==
PowerPC Work Queue for [[Architectures/PowerPC/WorkQueue_for_EPEL_7|EPEL 7]].
 
[[PowerPC Fedora 21 Tasks]]
[[PowerPC Fedora 22 Tasks]]
 
[[PowerPC EPEL Tasks]]
 
== Detailed plans ==
=== python (DONE) ===
* http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=1962223 which uses latest gcc-4.9.1-2.fc21 and glibc-2.19.90-30.fc21, but still fails on setegid test
* plan agreed with Siddhesh
** (DONE as glibc-2.19.90-31.fc22) he builds new glibc in rawhide and assures there is no problem in primary (i686), no builds in f21 until we are sure it works on all platforms
** (DONE) we rebuild this one in f21 as scratch build - http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=1964230
** then rebuild python with it, mean a local mock build, on both ppc64 and ppc64le and wait for the result
*** if all OK, I'll forward the info to Siddhesh
*** if BAD, then we will work on isolating the failing test and give him access to the machine
*** isolating the test could mean rebuild without test suite to have the python binaries that can be then used to execute the test
 
== Various notes ==
* recently I have seen a stuck guile process (during build of graphviz-2.38.0-8.fc21 on ppc-le-builder2), very likely due the threading issue (waiting in futex), after attaching strace to the hung process, the process got unblocked

Latest revision as of 09:56, 12 March 2015

Work Queues

This is the central point where work on build failures is organized. You can find on following specific pages a list of failed builds, list of actual tasks and who works on them.

PowerPC Work Queue for Fedora 21.

PowerPC Work Queue for Fedora 22.

PowerPC Work Queue for EPEL 7.