From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Autobnuilders timeouts [was: Re: autobuilder flock hangs]
Date: Sat, 25 Aug 2018 15:31:16 +0200 [thread overview]
Message-ID: <20180825133116.GC2419@scaer> (raw)
In-Reply-To: <CANQCQpb6Cgt+YoniwLCd8jGhLdrzCCJDcAyXjcSAWbETrZ=mUQ@mail.gmail.com>
Matthew, Julien, All,
On 2018-08-24 18:54 -0500, Matthew Weber spake thusly:
> On Fri, Aug 24, 2018 at 2:02 AM Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Now, I also had a look at all the timeouts, and I also noticed a single
> > other pattern. Julien's and Matthew's autobuilder would always choke on
> > host-libsodium, and it happens only on those two autobuilders:
> > http://autobuild.buildroot.org/?reason=host-libsodium
> > All failing at the same point:
> > checking whether segmentation violations can be caught when using the C compiler...
>
> Tried a few things...
> 1) Setup this config and did a make host-libsodium. No hang.
> 2) Took the test code from that configure test and could execute it without hang
> 3) Doing a full build now and we'll see if there is a sequencing/file
> configuration driving this.
>
> Any other ideas?
I found the commit that added this check:
https://github.com/jedisct1/libsodium/commit/c3045e2cb02dc1dae29cdb0dafd6cdb6469b8de8
So, does your host compiler runs asan by default? If so, do you have
ASAN_OPTIONS set in your environment?
(just throwing random guesses at it to see if any sticks...)
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-08-25 13:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-11 Thomas Petazzoni
2018-08-12 20:36 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-08-13 11:33 ` Romain Naour
2018-08-13 14:15 ` Matthew Weber
2018-08-13 22:43 ` Arnout Vandecappelle
2018-08-14 2:21 ` Matthew Weber
2018-08-13 14:36 ` Matthew Weber
2018-08-13 15:30 ` Matthew Weber
2018-08-13 18:10 ` [Buildroot] host-libselinux atomics with GCC 4.4 Hollis Blanchard
2018-08-13 18:25 ` Matthew Weber
2018-08-13 19:43 ` Hollis Blanchard
2018-08-16 9:43 ` Thomas Petazzoni
2018-08-13 18:18 ` [Buildroot] autobuilder flock hangs Hollis Blanchard
2018-08-13 21:18 ` Thomas Petazzoni
2018-08-13 21:28 ` Yann E. MORIN
2018-08-16 9:10 ` Thomas Petazzoni
2018-08-24 7:02 ` [Buildroot] Autobnuilders timeouts [was: Re: autobuilder flock hangs] Yann E. MORIN
2018-08-24 23:45 ` Hollis Blanchard
2018-08-25 13:05 ` Yann E. MORIN
2018-09-27 17:18 ` Hollis Blanchard
2018-08-24 23:54 ` Matthew Weber
2018-08-25 13:31 ` Yann E. MORIN [this message]
2018-08-25 13:58 ` Romain Naour
2018-08-26 13:00 ` Matthew Weber
2018-08-27 16:31 ` Julien Boibessot
2018-08-28 9:03 ` Thomas Petazzoni
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=20180825133116.GC2419@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