All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: build failures due to pigz host tool
Date: Thu, 4 Jul 2019 10:27:09 -0400	[thread overview]
Message-ID: <20190704142709.GA3410@linux-uys3> (raw)
In-Reply-To: <1008b3f46332ba67abe67586b176bc7f565b11ad.camel@linuxfoundation.org>

On Wed 2019-07-03 @ 05:10:14 PM, Richard Purdie wrote:
> Is there any way you could try pigz 2.4 on your machine, see if the
> problem still occurred there? If you do rebuild pigz, could you apply
> the debug patch in master-next?

I've updated the pigz in the $PATH jenkins sees to pigz-2.4.

However, my builds are always updated automatically and always build from
master; there's no way to insert ad-hoc patches into a build.

The job of my overnight builds is to keep tabs on master branches and ensure
they continue to build, not to test groups of patches in anticipation of
pushing new things into the repository. Therefore my Jenkins build flow has
been structured this specific way on purpose.

Since these failures only occur for me from builds kicked off by Jenkins, I
won't be able to easily help test patches unless I were to create a new
Jenkins workflow.


  reply	other threads:[~2019-07-04 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03 15:04 build failures due to pigz host tool Trevor Woerner
2019-07-03 16:02 ` Mikko.Rapeli
2019-07-03 16:10 ` Richard Purdie
2019-07-04 14:27   ` Trevor Woerner [this message]
2019-07-04 15:57     ` Richard Purdie
2019-07-04 22:28       ` Richard Purdie
2019-07-06  8:14         ` Richard Purdie
2019-07-06 17:02           ` Richard Purdie

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=20190704142709.GA3410@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 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.