From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-08-10
Date: Sat, 12 Aug 2017 11:56:14 +0200 [thread overview]
Message-ID: <20170812095614.GA3021@scaer> (raw)
In-Reply-To: <k9s06ex8uo.ln2@ID-313208.user.individual.net>
Bernd, All,
On 2017-08-11 16:41 +0200, Bernd Kuhls spake thusly:
> Am Fri, 11 Aug 2017 08:31:03 +0200 schrieb Thomas Petazzoni:
>
> > | ORPH arm | oracle-mysql-5.1.73 | NOK |
> > http://autobuild.buildroot.net/
> results/49377c636edf72bc68cbcecd1a787d578dba1d4e
>
> FYI: this build error, although still valid, was found by your
> autobuilder http://autobuild.buildroot.net/?submitter=Yann+E.+MORIN
> which is not testing current git master, but git master as of Jul, 29th
In fact, we identified with Thomas that the build was correctly done on
master, but the gitid is wrong only in the report.
It turned out to be a bug in a recent commit in the autobuild script,
which caused the wrong commit ID to be reported.
And in fact, all autobuilder instances that were up to date were
suffering from the issue. Only those that did not update their instances
were sending the correct gitid.
I've sent a patch, with more details in there.
Thanks! for the report! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2017-08-12 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 6:31 [Buildroot] [autobuild.buildroot.net] Build results for 2017-08-10 Thomas Petazzoni
2017-08-11 14:41 ` Bernd Kuhls
2017-08-12 9:56 ` Yann E. MORIN [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=20170812095614.GA3021@scaer \
--to=yann.morin.1998@free.fr \
--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