[release-process] File FTBFS Bug post Mass Rebuild #13426
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
release-process
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets#13426
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the issue
After every mass rebuild, we file FTBFS bugs for the packages that failed to build during mass rebuild.
This should be run after the mass rebuild builds are merged into main tag.
When do you need this? (YYYY/MM/DD)
Post F45 Mass Rebuild
When is this no longer needed or useful? (YYYY/MM/DD)
F45 EOL
If we cannot complete this, what is the impact? [Dependencies/Blocker]
oh no, can't happen :D We need to tell maintainers for failing packages so that can fix it before we do freezes
ref: #13406
Checklist
I have hunspell-* packages which are still in need-rebuild status. What will happen to them, as I consider them as not FTBFS packages, how to know reason about why they not submitted to koji?
Ok might be a problem with need-rebuild script:
I see mostly all of them are build
the logs are much bigger sharing some, can you list down specific packages please so i can check
I tried to query koji for failed buildSRPMFromSCM tasks that happened during the mass rebuild:
Results (54 packages):
I read the output of https://kojipkgs.fedoraproject.org/mass-rebuild/f45-need-rebuild.html with my username pnemade
Yeah, those seem to have failed due to some kind of infrastructure issue where they couldn't clone the git repo.
You should be able to just do 'fedpkg build' in all of them and they should disappear from the needs-rebuild page.
@kevin wrote in #13426 (comment):
Thanks. Will be building now.
I've gone ahead and resubmitted all builds where tasks failed in buildSRPMFromSCM that didn't already have a new build or changes newer than the mass rebuild.
Most failures were due to git clone / fedpkg sources flukes, but some are caused by actual broken spec files or broken / missing sources. All of these are actual issues so they should get FTBFS bugs filed for them:
Name: charliecloudin their spec. I suppose the capitalized version should be retired? koji is confused about both existing too.Name: python-prctlSome of the packages I resubmitted are now proper FTBFS, not sure if they'll show up on the f45-failures list now - these should also get FTBFS bugs:
I'll need to check, but for starters, two new bugzilla tickets have been opened:
PR for adding to tooling before I start filing bugs: releng/tooling#13047
The bugs for failures were filed, I'll manually look for filing the one @decathorpe mentioned now.
That too is now done, thanks. Closing these one now.