GNU bug report logs - #26981
Test failure in guix (commit 872a6fd98868d345443f04efdfd974d148c57f9d)

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 26981 in the body.
You can then email your comments to 26981 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Konrad Hinsen <konrad.hinsen <at> fastmail.net>
To: bug-guix <at> gnu.org
Subject: Test failure in guix (commit 872a6fd98868d345443f04efdfd974d148c57f9d)
Date: Thu, 18 May 2017 08:38:15 +0200

[Message part 1 (text/plain, inline)]

Dear Guix developers,

I just did ¨make check¨ on guix and got one test failure. The log is 
attached.

Konrad.

[test-suite.log (text/x-log, attachment)]

Message #8 received at 26981 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Konrad Hinsen <konrad.hinsen <at> fastmail.net>
Cc: 26981 <at> debbugs.gnu.org
Subject: Re: bug#26981: Test failure in guix (commit
 872a6fd98868d345443f04efdfd974d148c57f9d)
Date: Fri, 19 May 2017 10:16:35 +0200

Hi Konrad,

Konrad Hinsen <konrad.hinsen <at> fastmail.net> skribis:

> ==================================================
>    GNU Guix 0.12.0.3916-872a6: ./test-suite.log
> ==================================================
>
> # TOTAL: 706
> # PASS:  701
> # SKIP:  4
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0

[...]

> test-name: pivot-root
> location: /home/hinsen/Development/guix/tests/syscalls.scm:154
> source:
> + (test-equal
> +   "pivot-root"
> +   #t
> +   (match (pipe)
> +          ((in . out)
> +           (match (clone (logior CLONE_NEWUSER CLONE_NEWNS SIGCHLD))
> +                  (0
> +                   (dynamic-wind
> +                     (const #t)
> +                     (lambda ()
> +                       (close in)
> +                       (call-with-temporary-directory
> +                         (lambda (root)
> +                           (let ((put-old (string-append root "/real-root")))
> +                             (mount "none" root "tmpfs")
> +                             (mkdir put-old)
> +                             (call-with-output-file
> +                               (string-append root "/test")
> +                               (lambda (port) (display "testing\n" port)))
> +                             (pivot-root root put-old)
> +                             (write (file-exists? "/test") out)
> +                             (close out)))))
> +                     (lambda () (primitive-exit 0))))
> +                  (pid (close out)
> +                       (let ((result (read in)))
> +                         (close in)
> +                         (and (zero? (match (waitpid pid)
> +                                            ((_ . status)
> +                                             (status:exit-val status))))
> +                              (eq? #t result))))))))
> expected-value: #t
> actual-value: #f
> result: FAIL

What does “uname -r” report on your system?

This test is known to exercise a kernel bug on recent versions:

  ;; XXX: Skip this test when running Linux > 4.7.5 to work around
  ;; <https://bugzilla.kernel.org/show_bug.cgi?id=183461>.
  (when (or (not perform-container-tests?)
            (version>? (utsname:release (uname)) "4.7.5"))
    (test-skip 1))

(This functionality is used only by the container facilities of ‘guix
environment’ and ‘guix system’, so you shouldn’t take it as a blocker.)

Thanks for reporting the issue,
Ludo’.

Message #11 received at 26981 <at> debbugs.gnu.org (full text, mbox):

From: Konrad Hinsen <konrad.hinsen <at> fastmail.net>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 26981 <at> debbugs.gnu.org
Subject: Re: bug#26981: Test failure in guix (commit
 872a6fd98868d345443f04efdfd974d148c57f9d)
Date: Fri, 19 May 2017 11:56:51 +0200

Hi Ludo,

> What does “uname -r” report on your system?
4.4.0-78-generic

It's an up-to-date Ubuntu 16.04 installation.

> (This functionality is used only by the container facilities of ‘guix
> environment’ and ‘guix system’, so you shouldn’t take it as a blocker.)

OK, then I will just go ahead and switch to "guix from git".

Thanks,
 Konrad.

Message #16 received at 26981 <at> debbugs.gnu.org (full text, mbox):

From: "Robert Smith" <robertsmith <at> posteo.net>
To: <konrad.hinsen <at> fastmail.net>, <26981 <at> debbugs.gnu.org>
Subject: Bug report follow up
Date: Wed, 02 Dec 2020 22:31:14 -0800

Konrad, is this bug report still relevant? I suspect not, since it
seems to have been solved by switching to a more recent version
of guix 3 years ago.
The bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26981
If I don't hear back I'll assume it's safe to close this.

-Robert

Message #19 received at 26981 <at> debbugs.gnu.org (full text, mbox):

From: Konrad Hinsen <konrad.hinsen <at> fastmail.net>
To: Robert Smith <robertsmith <at> posteo.net>, 26981 <at> debbugs.gnu.org
Subject: Re: Bug report follow up
Date: Thu, 03 Dec 2020 09:11:01 +0100

Hi Robert,

> Konrad, is this bug report still relevant? I suspect not, since it
> seems to have been solved by switching to a more recent version
> of guix 3 years ago.
> The bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26981
> If I don't hear back I'll assume it's safe to close this.

Yes, it is. Thanks for doing a cleanup!

Konrad.

Message #22 received at 26981 <at> debbugs.gnu.org (full text, mbox):

From: "Robert Smith" <robertsmith <at> posteo.net>
To: "Konrad Hinsen" <konrad.hinsen <at> fastmail.net>, <26981 <at> debbugs.gnu.org>
Subject: Re: Bug report follow up
Date: Thu, 03 Dec 2020 10:23:54 -0800

On Thu Dec 3, 2020 at 9:11 AM Konrad Hinsen wrote:
> > Konrad, is this bug report still relevant? I suspect not, since it
> > seems to have been solved by switching to a more recent version
> > of guix 3 years ago.
> > The bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26981
> > If I don't hear back I'll assume it's safe to close this.
> 
> Yes, it is. Thanks for doing a cleanup!

This bug report is still relevant? Or are you saying that it is fixed?
Sorry if my email was a bit ambiguous!

-Robert

Message #25 received at 26981 <at> debbugs.gnu.org (full text, mbox):

From: Konrad Hinsen <konrad.hinsen <at> fastmail.net>
To: Robert Smith <robertsmith <at> posteo.net>, 26981 <at> debbugs.gnu.org
Subject: Re: Bug report follow up
Date: Fri, 04 Dec 2020 09:05:49 +0100

Hi Robert,

>> > The bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26981
>> > If I don't hear back I'll assume it's safe to close this.
>> 
>> Yes, it is. Thanks for doing a cleanup!
>
> This bug report is still relevant? Or are you saying that it is fixed?
> Sorry if my email was a bit ambiguous!

Right. My full answer is "Yes, it is safe to close this."

Konra.d

Message #30 received at 26981-done <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Konrad Hinsen <konrad.hinsen <at> fastmail.net>
Cc: Robert Smith <robertsmith <at> posteo.net>, 26981-done <at> debbugs.gnu.org
Subject: Re: bug#26981: Bug report follow up
Date: Fri, 4 Dec 2020 14:14:49 -0500

On Fri, Dec 04, 2020 at 09:05:49AM +0100, Konrad Hinsen wrote:
> Hi Robert,
> 
> >> > The bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26981
> >> > If I don't hear back I'll assume it's safe to close this.
> >> 
> >> Yes, it is. Thanks for doing a cleanup!
> >
> > This bug report is still relevant? Or are you saying that it is fixed?
> > Sorry if my email was a bit ambiguous!
> 
> Right. My full answer is "Yes, it is safe to close this."

Closing...

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.