[gentoo-dev] Reproducing a bug found by the tinderbox

[gentoo-dev] Reproducing a bug found by the tinderbox

[Marc Popp]

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

Hi All,

sorry, if this has been asked or explained before, but google and the
gentoo wiki couldn't find any answers.

I just got my first bug found by the tinderbox and would like to reproduce
the environment (chroot) that the bug was found in. There is some nice info
about it in the bug, but I was actually expecting a single command or some
kind of metadata file, that will rebuild exactly this environment. Or even
easier the tar-ed chroot after the emerge failed.

Furthermore the info about the exact emerge call would be very helpful in
the bug.

Now I have to configure a new chroot and then for the rest of the night
I'll compile GCC5 and QT just to be able to reproduce the bug. All this
could be replaced by a tar command for the tinderbox and a download and
untar for me.

What am I missing here?
How do other developers do that?
Where can I find "This is an unstable amd64 chroot image (named
amd64-desktop-unstable_20160821-212524)" or do I have to build that too?
What needs to be done to be able to shorten the time for reproducing those
bugs?

Thanks
Marc

PS: Sorry, it's 1am and I'm heading to bed now. See ya tomorrow.

[-- Attachment #2: Type: text/html, Size: 1402 bytes --]

Re: [gentoo-dev] Reproducing a bug found by the tinderbox

[Andrew Savchenko]

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]

Hi,

On Thu, 25 Aug 2016 00:47:44 +0200 Marc Popp wrote:
> Hi All,
> 
> sorry, if this has been asked or explained before, but google and the
> gentoo wiki couldn't find any answers.
> 
> I just got my first bug found by the tinderbox and would like to reproduce
> the environment (chroot) that the bug was found in. There is some nice info
> about it in the bug, but I was actually expecting a single command or some
> kind of metadata file, that will rebuild exactly this environment. Or even
> easier the tar-ed chroot after the emerge failed.
> 
> Furthermore the info about the exact emerge call would be very helpful in
> the bug.
> 
> Now I have to configure a new chroot and then for the rest of the night
> I'll compile GCC5 and QT just to be able to reproduce the bug. All this
> could be replaced by a tar command for the tinderbox and a download and
> untar for me.
> 
> What am I missing here?
> How do other developers do that?
> Where can I find "This is an unstable amd64 chroot image (named
> amd64-desktop-unstable_20160821-212524)" or do I have to build that too?
> What needs to be done to be able to shorten the time for reproducing those
> bugs?

Usually tinderbox logs are sufficient to reproduce an issue. If you
need a tinderbox image, try to contact Toralf for details.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]