From: Tanguy Le Carrour <tanguy@bioneland.org>
To: Jack Hill <jackhill@jackhill.us>
Cc: Guix <guix-devel@gnu.org>
Subject: Re: containerd fails to build
Date: Fri, 14 Feb 2020 09:38:16 +0100 [thread overview]
Message-ID: <20200214083816.zxr23tkvqctqs667@rafflesia> (raw)
In-Reply-To: <alpine.DEB.2.20.2002131404120.11123@marsh.hcoop.net>
Hi Jack,
Le 02/13, Jack Hill a écrit :
> On Thu, 13 Feb 2020, Tanguy Le Carrour wrote:
> > Hi Guix!
> > containerd fails to build on my system! :-(
>
> [content elided]
>
> > starting phase `check'
> > flag provided but not defined: -test.testlogfile
> > Usage of /tmp/guix-build-containerd-1.2.5.drv-0/go-build772692618/b001/containerd.test:
> > -address string
> > The address to the containerd socket for use in the tests (default "/run/containerd-test/containerd.sock")
> > -no-criu
> > Do not run the checkpoint tests
> > -no-daemon
> > Do not start a dedicated daemon for the tests
> > -test.root
> > enable tests that require root
> > FAIL github.com/containerd/containerd 0.004s
> > FAIL
> > command "go" "test" "github.com/containerd/containerd" failed with status 1
> > ```
> >
> > Any idea?!
>
> Oops, sorry about that. this is realated to the Go 1.13 upgrade and an
> change in how the test module works. I've submitted a patch to fix it for
> the containerd 1.2.5: https://issues.guix.gnu.org/issue/39581
>
> It seems the latest containerd release, 1.3.2, does not support go 1.13
> either, but is has landed in unreleased containerd.
No problem! Thanks for working on that!
Regards
--
Tanguy
prev parent reply other threads:[~2020-02-14 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 11:32 containerd fails to build Tanguy Le Carrour
2020-02-13 15:13 ` Tanguy Le Carrour
2020-02-13 19:07 ` Jack Hill
2020-02-14 8:38 ` Tanguy Le Carrour [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200214083816.zxr23tkvqctqs667@rafflesia \
--to=tanguy@bioneland.org \
--cc=guix-devel@gnu.org \
--cc=jackhill@jackhill.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.