linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Gal Pressman <galpress@amazon.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: Can't build rdma-core's azp image
Date: Sun, 26 Jul 2020 20:19:25 -0300	[thread overview]
Message-ID: <20200726231925.GP25301@ziepe.ca> (raw)
In-Reply-To: <221cbc21-f027-3312-5043-7622c7e854d3@amazon.com>

On Sun, Jul 26, 2020 at 10:05:59AM +0300, Gal Pressman wrote:
> On 27/05/2020 10:35, Gal Pressman wrote:
> > On 26/05/2020 22:23, Jason Gunthorpe wrote:
> >> On Tue, May 26, 2020 at 09:25:30AM +0300, Gal Pressman wrote:
> >>> On 07/04/2020 18:47, Gal Pressman wrote:
> >>>> I'm trying to build the azp image and it fails with the following error [1].
> >>>> Anyone has an idea what went wrong?
> >>>
> >>> azp build broke again :(.
> >>>
> >>> The last step
> >>> Step 4/4 : RUN apt-get update && apt-get install -y --no-install-recommends libgcc-s1:i386 libgcc-s1:ppc64el && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends abi-compliance-checker abi-dumper ca-certificates clang-10 cmake cython3 debhelper dh-python dh-systemd dpkg-dev fakeroot gcc-10 gcc-9-aarch64-linux-gnu gcc-9-powerpc64le-linux-gnu git libc6-dev libc6-dev:arm64 libc6-dev:i386 libc6-dev:ppc64el libgcc-10-dev:i386 libgcc-9-dev:arm64 libgcc-9-dev:ppc64el libnl-3-dev libnl-3-dev:arm64 libnl-3-dev:i386 libnl-3-dev:ppc64el libnl-route-3-dev libnl-route-3-dev:arm64 libnl-route-3-dev:i386 libnl-route-3-dev:ppc64el libsystemd-dev libsystemd-dev:arm64 libsystemd-dev:i386 libsystemd-dev:ppc64el libudev-dev libudev-dev:arm64 libudev-dev:i386 libudev-dev:ppc64el lintian make ninja-build pandoc pkg-config python3 python3-dev python3-docutils python3-yaml sparse valgrind && apt-get clean && rm -rf /usr/share/doc/ /usr/lib/debug /var/lib/apt/lists/
> >>>
> >>> Fails with
> >>> W: https://apt.llvm.org/focal/pool/main/l/llvm-toolchain-10/libllvm10_10.0.1~++20200519100828+f79cd71e145-1~exp1~20200519201452.38_amd64.deb: No system certificates available. Try installing ca-certificates.
> >>> E: Could not configure 'libc6:arm64'.
> >>> E: Could not perform immediate configuration on 'libgcc-s1:arm64'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
> >>
> >> couldn't reproduce
> > 
> > Maybe you have a cached image or something?
> > I just set up a clean instance and it reproduces immediately.
> 
> It was fixed at some point, and now it's back again:
> 
> Step 4/4 : RUN apt-get update && apt-get install -y --no-install-recommends libgcc-s1:i386 libgcc-s1:ppc64el && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends abi-compliance-checker abi-dumper ca-certificates clang-10 cmake cython3 debhelper dh-python dh-systemd dpkg-dev fakeroot gcc-10 gcc-9-aarch64-linux-gnu gcc-9-powerpc64le-linux-gnu git libc6-dev libc6-dev:arm64 libc6-dev:i386 libc6-dev:ppc64el libgcc-10-dev:i386 libgcc-9-dev:arm64 libgcc-9-dev:ppc64el libnl-3-dev libnl-3-dev:arm64 libnl-3-dev:i386 libnl-3-dev:ppc64el libnl-route-3-dev libnl-route-3-dev:arm64 libnl-route-3-dev:i386 libnl-route-3-dev:ppc64el libsystemd-dev libsystemd-dev:arm64 libsystemd-dev:i386 libsystemd-dev:ppc64el libudev-dev libudev-dev:arm64 libudev-dev:i386 libudev-dev:ppc64el lintian make ninja-build pandoc pkg-config python3 python3-dev python3-docutils python3-yaml sparse valgrind && apt-get clean && rm -rf /usr/share/doc/ /usr/lib/debug /var/lib/apt/lists/
> 
> [...]
> 
> W: https://apt.llvm.org/focal/pool/main/l/llvm-toolchain-10/libllvm10_10.0.1~++20200708122807+ef32c611aa2-1~exp1~20200707223407.61_amd64.deb: No system certificates available. Try installing ca-certificates.
> W: https://apt.llvm.org/focal/pool/main/l/llvm-toolchain-10/libclang1-10_10.0.1~++20200708122807+ef32c611aa2-1~exp1~20200707223407.61_amd64.deb: No system certificates available. Try installing ca-certificates.
> E: Could not configure 'libc6:arm64'.
> E: Could not perform immediate configuration on 'libgcc-s1:arm64'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
> 
> Maybe it's an issue with the llvm repo?

No idea. The reason we switched to AZP was to avoid the endless random
breakage by using pre-built containers. I think you need to do the
same..

Jason

      reply	other threads:[~2020-07-26 23:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 15:47 Can't build rdma-core's azp image Gal Pressman
2020-04-07 17:28 ` Leon Romanovsky
2020-04-07 18:06 ` Jason Gunthorpe
2020-04-08  6:35   ` Gal Pressman
2020-04-16  7:05     ` Gal Pressman
2020-04-17 16:21       ` Jason Gunthorpe
2020-04-19  6:37         ` Gal Pressman
2020-05-05  1:09           ` Jason Gunthorpe
2020-05-05  6:40             ` Gal Pressman
2020-05-05 13:21               ` Jason Gunthorpe
2020-05-05 14:05                 ` Gal Pressman
2020-05-26  6:25 ` Gal Pressman
2020-05-26 19:23   ` Jason Gunthorpe
2020-05-27  7:35     ` Gal Pressman
2020-07-26  7:05       ` Gal Pressman
2020-07-26 23:19         ` Jason Gunthorpe [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=20200726231925.GP25301@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=galpress@amazon.com \
    --cc=linux-rdma@vger.kernel.org \
    /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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).