From: Andrew Geissler <geissonator@gmail.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: snowyang <SnowYang@linux.alibaba.com>,
openbmc <openbmc@lists.ozlabs.org>,
Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: Change in ...meta-alibaba[master]: thor: initial machine creation
Date: Mon, 8 Feb 2021 15:06:44 -0600 [thread overview]
Message-ID: <35675947-5C93-4D51-AE6D-2BD178956213@gmail.com> (raw)
In-Reply-To: <YCGjdU3N6bHS/A1a@heinlein>
> On Feb 8, 2021, at 2:47 PM, Patrick Williams <patrick@stwcx.xyz> wrote:
>
> On Mon, Feb 08, 2021 at 09:44:46AM -0500, Brad Bishop wrote:
>>
>> This is an intermittant bug in the os-release recipe that we haven't
>> been able to track down. You can ignore this failure. I'll remove the
>> verified -1.
>
> I thought I had fixed all the known os-release recipe issues not too
> long ago. This one seems new to me:
>
> ERROR: Task (/home/jenkins-slave/workspace/ci-openbmc/distro/ubuntu/label/docker-builder/target/romulus/openbmc/meta/recipes-core/os-release/os-release.bb:do_package_qa) failed with exit code '134'
>
> https://jenkins.openbmc.org/job/ci-openbmc/1758/distro=ubuntu,label=docker-builder,target=romulus/console
>
> Andrew, have you seen this issue very often? Next time we see it, is
> there any way to get to the full build tree from bitbake? There should
> be a log buried somewhere under /tmp that will give us the details of
> what really happened here.
Yeah, I’ve been seeing this one intermittently for a while. There was such
limited data, I’ve just been retriggering when I see it.
The docker builds are setup to use $WORKSPACE as a build dir
so it is persistent after the docker container exits butI had to configure
the jenkins jobs to delete the workspaces when done due to space
issues on the nodes.
Best bet may be to try and identify the file(s) we need and I can
have the jenkins job archive them.
>
> --
> Patrick Williams
prev parent reply other threads:[~2021-02-08 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gerrit.1605682495000.I03f07f9e29b4ec19b5b169f14489e8d7ed786600@gerrit.openbmc-project.xyz>
[not found] ` <4ufnKrB2SUu3u1SbJu709Q@ismtpd0004p1sjc2.sendgrid.net>
[not found] ` <94c8af34-dcae-e33d-a0f0-a5540ef518fd@linux.alibaba.com>
[not found] ` <YAneI7zHQx217lmu@heinlein>
[not found] ` <5841da60f00cade13d87d5b8795f8a25021c2e44.camel@fuzziesquirrel.com>
[not found] ` <f8678061-4662-4445-a4d0-016040f00979@linux.alibaba.com>
[not found] ` <0008fa42-2a5c-b092-8da6-7eaa91e775f7@linux.alibaba.com>
[not found] ` <0FC93EA6-AE09-46A6-9BF2-36471B85755B@fuzziesquirrel.com>
[not found] ` <fe3fef11-56c7-85a4-b3fc-35ab29e99f60@linux.alibaba.com>
2021-02-02 13:51 ` Change in ...meta-alibaba[master]: thor: initial machine creation Brad Bishop
2021-02-03 9:36 ` snowyang
2021-02-06 13:16 ` snowyang
2021-02-08 7:11 ` Snowyang@linux.alibaba-inc.com
2021-02-08 14:44 ` Brad Bishop
2021-02-08 20:47 ` Patrick Williams
2021-02-08 21:06 ` Andrew Geissler [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=35675947-5C93-4D51-AE6D-2BD178956213@gmail.com \
--to=geissonator@gmail.com \
--cc=SnowYang@linux.alibaba.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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).