From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Subject: bug#33623: Backtrace when running `guix system roll-back'
Date: Fri, 07 Dec 2018 23:23:57 +0100
Message-ID: <87o99xasci.fsf@gnu.org>
References: <87k1ko2ois.fsf@tapuakh.i-did-not-set--mail-host-address--so-tickle-me>
	<87k1ko2ois.fsf@tapuakh.i-did-not-set--mail-host-address--so-tickle-me>
	<87h8fpfmoj.fsf@gnu.org> <LT8nmD7--3-1@tutanota.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45137)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gVOYS-0007XH-Bl
	for bug-guix@gnu.org; Fri, 07 Dec 2018 17:25:04 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gVOYR-0003Lp-R4
	for bug-guix@gnu.org; Fri, 07 Dec 2018 17:25:04 -0500
Received: from debbugs.gnu.org ([208.118.235.43]:33134)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gVOYQ-0003L8-Kf
	for bug-guix@gnu.org; Fri, 07 Dec 2018 17:25:03 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gVOYQ-0001ZZ-Dq
	for bug-guix@gnu.org; Fri, 07 Dec 2018 17:25:02 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.33623.D33623.15442214515961@debbugs.gnu.org>
In-Reply-To: <LT8nmD7--3-1@tutanota.com> (znavko's message of "Fri, 7 Dec 2018
	18:55:16 +0100 (CET)")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: znavko@tutanota.com
Cc: 33623-done@debbugs.gnu.org, Diego Nicola Barbato <dnbarbato@posteo.de>

Hello,

<znavko@tutanota.com> skribis:

> Is it possible to automatize detection of this kind of problems?=20
> As I see, some PC can has crontab job to do `guix pull`, so that if 'Back=
trace' message occurs, it sends a report to developer not to rush up to pus=
h his branch to master branch.

There are lots of unit tests and system tests in Guix.  Unfortunately
this particular bit is not covered by a test.  We would need to come up
with a testing strategy for this but it can be quite challenging.

Ludo=E2=80=99.