From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2019-07-01
Date: Tue, 2 Jul 2019 22:36:16 +0200 [thread overview]
Message-ID: <20190702203614.GA4840@dell5510> (raw)
In-Reply-To: <5d1af309.1c69fb81.cf999.ba7eSMTPIN_ADDED_MISSING@mx.google.com>
Hi,
> Hello,
> This is the list of Buildroot build failures that occured on
> 2019-07-01, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches to
> fix them. Thanks!
> Results for the 'master' branch
> ===============================
> Build failures related to your packages:
> sh4 | iputils-20190515 | http://autobuild.buildroot.net/results/e2ad49ca3b59c5d4b0fb883fc3a79483ba023428
> microblazeel | iputils-20190515 | http://autobuild.buildroot.net/results/53c8354aba24ac99a532d3fc50132e4d5eeb1ff6
> mips | iputils-20190515 | http://autobuild.buildroot.net/results/cf3c2016be18882713a70baa367ef6836df207c1
> sh4 | iputils-20190515 | http://autobuild.buildroot.net/results/c891df50b2ca01c969e5275ca92d74ce861af8ee
> arm | iputils-20190515 | http://autobuild.buildroot.net/results/754179740a63d4c34480804f2b733f687a7128dd
At least some of these are fixed in next branch. What is the policy? Can be
individual commits cherrypicked? Or does it need to wait till next release?
Kind regards,
Petr
next parent reply other threads:[~2019-07-02 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d1af309.1c69fb81.cf999.ba7eSMTPIN_ADDED_MISSING@mx.google.com>
2019-07-02 20:36 ` Petr Vorel [this message]
2019-07-03 22:04 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2019-07-01 Peter Korsgaard
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=20190702203614.GA4840@dell5510 \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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