| Summary: | Generate bugs for failed distfile downloads | ||
|---|---|---|---|
| Product: | Gentoo Infrastructure | Reporter: | Robert Buchholz (RETIRED) <rbu> |
| Component: | Other | Assignee: | Bugzilla Admins <bugzilla> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | enhancement | CC: | qa, zmedico |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
gen-bug.py
bugcache |
||
Created attachment 131783 [details]
gen-bug.py
Created attachment 131784 [details]
bugcache
Current bug cache (in case you set this up, to avoid dupes)
This is more of a project for the bugzilla team, or a random user with EDITBUGS privs, IMO. @QA: If you're interested please take this bug, *might* be a good idea for qa-scripts/qa-reports. Otherwise I'll close it as WONT/CANTFIX because it has nothing to do with Bugzilla itself although I think it may be useful. Feel free to do this yourself, if you need an account to open bugs with, file a bug request for one and we will make you a role account for failed distfiles fetches. -A (In reply to comment #4) > @QA: If you're interested please take this bug, *might* be a good idea for > qa-scripts/qa-reports. Otherwise I'll close it as WONT/CANTFIX because it > has nothing to do with Bugzilla itself although I think it may be useful. I think this is a solid candidate for the qa-scripts/qa-reports setup. I can look into setting it up if no one else wants to. |
Based on Zac Medico's script that generates the report at [1], I created a script to file bugs for these failures. Given the failure.log and a filename for the bug cache, it will create a bug for each new entry (if one ebuild fails with several files, it will only be one bug). If a bug already exists, but is closed it will reopen the bug, mentioning the files missing in the latest run. It will not touch open bugs. To set this baby up, we need to 1) Review the script, as I'm not the Python guru Zac is. 2) Install PyBugz on the machine generating the failure.log 3) Set up an alias @gentoo.org (add me to it :-) 4) Set up a BugZilla account for that alias (or rename the account from the example bugs) 5) Enter the email / password in the script 6) Cron the script to run after an update of the failure.log Examples? Look at bug 193639, bug 193638, bug 193635. This would work great with the auto-assigning code robbat2 was creating. [1] http://dev.gentoo.org/~zmedico/infra/distfiles/failure.xml