All the stack is at https://github.com/gentoo/tboxanalysis
The opening of the bug report is done by a piece of meatware called "me". The UI displays a link that I can click to pre-fill the bug report. The rest of the information is filled in manually and submitted. Also remember that the linked logs might be too big for Bugzilla to attach uncompressed... and some of them even compressed. I take it that at least one person (you) will object at me keeping the process as is, so for the moment I won't be wasting my time on this. Call me back if you find a way to fix that without requiring more of my time. Diego Elio Pettenò — Flameeyes flamee...@flameeyes.eu — http://blog.flameeyes.eu/ On 18 October 2014 17:55, Pacho Ramos <pa...@gentoo.org> wrote: > El sáb, 18-10-2014 a las 14:15 +0100, Diego Elio Pettenò escribió: > > If you write the code for that, be my guest. But the code is in Ruby > > and does not open the bug directly (only links to a pre-filled bug > > form). > > > > > > When I wrote it, Python was definitely not among my strong languages. > > While I can probably write it now, I don't have the time. > > > > > > As I said I'm happy to volunteer my time to run the tinderbox and file > > the bugs. But I won't do so if all I'm going to get back is bitching. > > It seems a fair proposal to me. > > > > Diego Elio Pettenò — Flameeyes > > flamee...@flameeyes.eu — http://blog.flameeyes.eu/ > > What do you use to open the bug reports? Maybe could be easily be done > at that step :| (or even run some small script after the bug if filled > simply re-fetching the file from amazon and attaching to the bug it's > being processed) > > > >
