From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 1E35E138330 for ; Wed, 24 Aug 2016 22:48:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CE63421C185; Wed, 24 Aug 2016 22:47:48 +0000 (UTC) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 863CD21C104 for ; Wed, 24 Aug 2016 22:47:47 +0000 (UTC) Received: from mail-lf0-f52.google.com ([209.85.215.52]) by mrelayeu.kundenserver.de (mreue001) with ESMTPSA (Nemesis) id 0LhGKW-1aqPqb3oGW-00mYkO for ; Thu, 25 Aug 2016 00:47:45 +0200 Received: by mail-lf0-f52.google.com with SMTP id g62so22308404lfe.3 for ; Wed, 24 Aug 2016 15:47:45 -0700 (PDT) X-Gm-Message-State: AE9vXwPOBI1U20+CKnGqhgi1MnlXJ/2pCBCPZC5sTsuec+1npSsJG/IbBgPrv/KNnJkFLYFeSjgQ4lWO6JLvpg== X-Received: by 10.25.83.85 with SMTP id h82mr1328438lfb.97.1472078865321; Wed, 24 Aug 2016 15:47:45 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.25.208.78 with HTTP; Wed, 24 Aug 2016 15:47:44 -0700 (PDT) From: Marc Popp Date: Thu, 25 Aug 2016 00:47:44 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: [gentoo-dev] Reproducing a bug found by the tinderbox To: gentoo-dev@lists.gentoo.org Content-Type: multipart/alternative; boundary=001a11405a08d95b86053ad9112e X-Provags-ID: V03:K0:v9Atr+GiJSh2NizPLoaK+SjSGhpkJzyizi3Pp6ghARUgCIQ1kqk 6s2CCE71T3367KsPhWJ+lJz4/xsWzeb5fR8xgQaPB/VREYJeJntV+8ptxsoLx3HGOoCgaGA dBvxKQS5EGkJS3MZJZiH8qO6Y71JaWkTLrQTXTdce9Sex9N4GhoFQ2ADO9xjPWJWN7Nafmu ifuiL6USMqCKxh5Ad1uoA== X-UI-Out-Filterresults: notjunk:1;V01:K0:yMu9KJlEQe4=:q9QiQz+0OnQ6Ud0bw8Quae K0j+OgByVczrgnmw0JSl+HHb55wIxu+jmITUy8DMD0G39cehFaTcp+n4q6GAd3oHPy4QxdbVX T7kFhbI6OMZ65Jr1Uj/Yo655+tF/kvg2Z20LGcar7URQeqAgt7lwdVVNUQn6hzuaXgPvIsMLO soS78ONzgb5mVCrQ5YK8XMwPB+Yn4R27YAYG5XWRJct1cObkVRaF24f6D/4mqNDgRS/bNQzzI orUXbNBP5b2a4AWnzByIYvzQWdZ/X/Bfex/l5YqsHdtGlpgUFpjSuPmaa33+284gYdxNX3xCC iHu7AIB55Qrbu4LIoyrutCWTE4UXredHpBEdmdOBmMPDolTseR2KYSxFS0+0LCK08sMlwO36Q vrvedGqwu4ar9H0csYFZt144SotoTqfGlsmpsJdAwc5ZjPEv0E1E618A3Lr03bBvQF1C+VoK3 9lX8yLUjgC7cWbBobzevaNtIF95SBuRTupqrn5PgDYSBSogTgVnmGc44DrP96Xpt/oXsmcOQv 7Kr/8FxiLstzM0g+iKqdhazj2054F05OgTy6Xtx/ow5ZpFNt+i4qfnEF+8Qpiv9fS2rYMZ7ba VAfT+YkiMrYvYgb5iabtCgkqLy2U9Th+FJjs710WsuFqhVxn0YgoY9QEl4pYapkihS53zHFOo 21whE1Qrj7fimI99X5K8V9PkD17oUopm9rAtC+kXG7ZvnvX6CHvxruTjVaorUpTOv8adfICPu Q7AXDoVcIYwLBtND X-Archives-Salt: 0f86981e-ad4a-4164-976d-c2149a581640 X-Archives-Hash: d538b6954a9b3c3599cd3d80717559d0 --001a11405a08d95b86053ad9112e Content-Type: text/plain; charset=UTF-8 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. --001a11405a08d95b86053ad9112e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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 re= produce the environment (chroot) that the bug was found in. There is some n= ice 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 hel= pful in the bug.

Now I have to configure a new chr= oot 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 amd= 64-desktop-unstable_20160821-212524)" or do I have to build that too?<= /div>
What needs to be done to be able to shorten the time for reproduc= ing those bugs?

Thanks
Marc

PS: Sorry, it's 1am and I'm heading to bed now. Se= e ya tomorrow.
--001a11405a08d95b86053ad9112e--