Guix build of guix package fails due to some graph tests failing

  • Done
  • quality assurance status badge
Details
3 participants
  • Andrew Patterson
  • Tobias Geerinckx-Rice
  • Simon Tournier
Owner
unassigned
Submitted by
Andrew Patterson
Severity
normal
A
A
Andrew Patterson wrote on 12 Dec 2022 07:36
(address . bug-guix@gnu.org)
878rjd3y79.fsf@gmail.com
The `guix` package currently fails to build. Looking at the build
log, this is because some tests in tests/graph.scm fail, and the
actual test log complains about a wrong arg type to
scm_to_utf8_stringn for both failing tests. I did recently have a
transient `guix pull` issue with a similar error, but guix is now
functioning as usual.

Both the build log and tests/graph.scm test log are attached below
Attachment: file
Attachment: file
--
Andrew Patterson
S
S
Simon Tournier wrote on 26 Jan 2023 18:25
86zga5p5r2.fsf@gmail.com
Hi,

On Mon, 12 Dec 2022 at 01:36, Andrew Patterson <andrewpatt7@gmail.com> wrote:

Toggle quote (7 lines)
> The `guix` package currently fails to build. Looking at the build
> log, this is because some tests in tests/graph.scm fail, and the
> actual test log complains about a wrong arg type to
> scm_to_utf8_stringn for both failing tests. I did recently have a
> transient `guix pull` issue with a similar error, but guix is now
> functioning as usual.

Thanks for the report. I have not seen this error about
tests/graph.scm.

Are you running plain “make check” or do you pass an argument as “make
check -j 123”?


Cheers,
simon
A
A
Andrew Patterson wrote on 26 Jan 2023 22:38
(name . Simon Tournier)(address . zimon.toutoune@gmail.com)(address . 59987@debbugs.gnu.org)
87fsbxm08r.fsf@gmail.com
guix has been building fine recently, so either it's something
unpredictable or it was inadvertently fixed at some point. Feel
free to close the bug report unless you want to hunt down what
actually happened.

Toggle quote (3 lines)
> Are you running plain “make check” or do you pass an argument as
> “make
> check -j 123”?
The build error was from `guix build guix`, so make check was
running with whatever that calls it with. In case it's relevant,
the build error was on a pinebook pro, so 6-core aarch64.

Otherwise, the issue hasn't resurfaced and it's been a month, so
the original report and attached build log are gonna be about as
good a source of information as what I remember.

Thanks,
--
Andrew Patterson
S
S
Simon Tournier wrote on 27 Jan 2023 12:39
(name . Andrew Patterson)(address . andrewpatt7@gmail.com)(address . 59987@debbugs.gnu.org)
877cx8p5og.fsf@gmail.com
Hi,

On jeu., 26 janv. 2023 at 16:38, Andrew Patterson <andrewpatt7@gmail.com> wrote:

Toggle quote (8 lines)
>> Are you running plain “make check” or do you pass an argument as
>> “make
>> check -j 123”?
>
> The build error was from `guix build guix`, so make check was
> running with whatever that calls it with. In case it's relevant,
> the build error was on a pinebook pro, so 6-core aarch64.

Well, for reproducing, the usual requirements are your Guix revision
(guix describe) when you see the issue. Also the architecture and if it
cross-compiled (--target=aarch64-linux-gnu) from which host, often help.

I am in favour of closing if no objection.

Cheers,
simon
A
A
Andrew Patterson wrote on 27 Jan 2023 23:05
(name . Simon Tournier)(address . zimon.toutoune@gmail.com)(address . 59987@debbugs.gnu.org)
87bkmjmxli.fsf@gmail.com
I'm also in favor of closing. (I'm pretty sure I've garbage
collected the closest generation to it, anyways).

Thanks for the help!
--
Andrew Patterson
T
T
Tobias Geerinckx-Rice wrote on 28 Jan 2023 00:00
(name . Andrew Patterson)(address . andrewpatt7@gmail.com)(address . 59987-close@debbugs.gnu.org)
87bkmjlgw6.fsf@nckx
Andrew Patterson ???
Toggle quote (2 lines)
> I'm also in favor of closing.

Done!

You can close any bug yourself by editing the reply address in the
CC header, as I did here.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCY9RYOg0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15s/0BAI/xiJoeDHA1igy050We2q4XNawbVqYDiHF6pCNm
kq1OAQDGdtNaTQJksjC4Ns+KUXr3C/s8mg9WoH6kTxeeeNe6CA==
=r6I5
-----END PGP SIGNATURE-----

?