Hello, I'd like to build some F35 packages in staging infra for testing purposes, and I don't seem to be able to do it. Distgit.stg thinks that the rawhide branch is f34 (because there is no specific f34 branch, just f33), and koji.stg is not aware of any f35-related build targets and tags.
rawhide
f34
f33
When I'm on the rawhide branch in distgit.stg:
$ fedpkg-stage build Building sendKindle-3-10.fc34 for rawhide # notice **fc34** ... $ fedpkg-stage --release f35 build Could not execute build: Unknown build target: f35-candidate
Note: There are some fc35 updates in Bodhi, but I don't know how people did it, I can't make it work.
Can you please make distgit.stg and koji.stg F35-aware?
It's not critical, I'll be able to find some workarounds, if this is difficult to do or if there are no free cycles for it. But I'd be glad if you could do it :-)
Yeah, I was thinking we would want to do this soon.
I might try and start it this weekend, but if not, monday.
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-trouble, medium-gain, ops
I've started a sync.
I did a PDC sync not long ago, which means anyone should be able to create the F35 branches as they wish dist-git side
Done.
I realized after I started this I should I have checked with @nphilipp and the rpmautospec team. ;( Sorry about that and I hope I didn't mess up anything you had in flight. On the plus side stg koji is much more exactly like prod now. (Or like it will be).
I have upgraded all the builders to f34 there and the newest koji version on the hub. Hopefully I can look at doing this in prod next week sometime.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks a lot, Kevin.
The f34 branches were not created in distgit, but I can create them myself. Is that expected?
Also, my build tasks seem to time out when waiting for 2 hours for "waitrepo":
$ fedpkg-stage build Building sendKindle-3-10.fc35 for rawhide Created task: 90000279 Task info: https://koji.stg.fedoraproject.org/koji/taskinfo?taskID=90000279 Watching tasks (this may be safely interrupted)... 90000279 build (rawhide, /rpms/sendKindle.git:676b966a35a1719587a53beeab605a05b8c74ff5): free 90000279 build (rawhide, /rpms/sendKindle.git:676b966a35a1719587a53beeab605a05b8c74ff5): free -> open (buildvm-ppc64le-03.stg.iad2.fedoraproject.org) 90000280 waitrepo (37078): open (buildvm-ppc64le-03.stg.iad2.fedoraproject.org) 90000279 build (rawhide, /rpms/sendKindle.git:676b966a35a1719587a53beeab605a05b8c74ff5): open (buildvm-ppc64le-03.stg.iad2.fedoraproject.org) -> FAILED: GenericError: Unsuccessfully waited 120:13 for a new f35-build repo 0 free 1 open 0 done 1 failed 90000280 waitrepo (37078): open (buildvm-ppc64le-03.stg.iad2.fedoraproject.org) -> FAILED: GenericError: Unsuccessfully waited 120:13 for a new f35-build repo 0 free 0 open 0 done 2 failed 90000279 build (rawhide, /rpms/sendKindle.git:676b966a35a1719587a53beeab605a05b8c74ff5) failed
Looking at recent tasks it seems to affect... everyone? Should I report a separate ticket about it?
I think that was a consequence of the sync, as kojira had to make new repos for all the side tags and that took a while. ;(
My f35 python builds are finishing ok now.
Can you retry?
It seems to be working now.
Log in to comment on this ticket.