#2825 Is there a way to grab the failed builds that are failed in srpm building phase
Closed: Fixed by tkopecek. Opened by mohanboddu.

Coming from the releng ticket https://pagure.io/releng/issue/8601, current listBuilds (state =3 for failed builds) only returns the failed builds that are failed in rpm build phase, but if a build fails in srpm phase it wont be returned.

Is there a way to find these builds so that we can file ftbfs for those packages as well?


At this point there is no build entry because we do not yet have the SRPM to determine the NVR from.

You can find the failed build tasks with something like listTasks(opts={"method": "build", "state": [5], "createdAfter": "2021-04-20"}). I would highly recommend a time limited query here.

Metadata Update from @mikem:
- Custom field Size adjusted to None

You might consider only querying the tasks actually.

Note that this will include scratch builds.

I have a proof-of-concept script that runs very similar query

opts['createdAfter'] = args.date
opts['method'] = "buildSRPMFromSCM"
opts['state'] = [ koji.TASK_STATES['FAILED'] ]
opts['owner'] = [ kojisession.getUser(userInfo='releng')['id'] ]
  • args.date is the mass-rebuild start
  • find failed buildSRPMFromSCM tasks
  • started by the releng user
    The output is package names extracted from the dist-git URLs.

see list-failed-tasks.py

Awesome, I will update the ftbfs script.

Thanks @mikem and @sharkcz

Also, @mikem it would be super useful to update the koji api to provide what state numerical values means what.

>>> import koji
>>> koji.BUILD_STATES
{'BUILDING': 0, 'COMPLETE': 1, 'DELETED': 2, 'FAILED': 3, 'CANCELED': 4}
>>> koji.TASK_STATES
{'FREE': 0, 'OPEN': 1, 'CLOSED': 2, 'CANCELED': 3, 'ASSIGNED': 4, 'FAILED': 5}

These are custom enum classes. They convert either way

>>> koji.TASK_STATES[0]
'FREE'
>>> koji.TASK_STATES['FREE']
0

I've added simple PR with example on API page and link to constants/exceptions: #2828

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.26

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.25 (was: 1.26)

Metadata Update from @jcupova:
- Issue tagged with: testing-ready

Metadata Update from @jobrauer:
- Issue tagged with: testing-done

Commit df09be48 fixes this issue

Commit d87e6847 relates to this ticket

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/2825

Please continue any further discussion there.

Metadata
Related Pull Requests