[Buildroot] Broken link in build notification

[Buildroot] Broken link in build notification

[Zoltan Gyarmati]

Dear Thomas &All,

On 01/21/2018 08:00 AM, Thomas Petazzoni wrote:
> Hello,
>
> This is the list of Buildroot build failures that occured on
> 2018-01-20, 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:
>
>          arm |                     proj-4.9.3 | http://autobuild.buildroot.net/results/80243a2ae19190d75e84a2ed8aa4b95a20ea9ef0
>

I received this ^^ build error notification mail yesterday.

The link redirects to
https://bugs.busybox.net/results/80243a2ae19190d75e84a2ed8aa4b95a20ea9ef0,
and ends up in a 404.

The results available here:

http://autobuild.buildroot.org/results/802/80243a2ae19190d75e84a2ed8aa4b95a20ea9ef0/

It seems there is some configuration problem here so i thought I let you
know...

In the meantime I also try to reproduce the actual build error.


Regards

Zoltan Gyarmati
https://zgyarmati.de


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180122/06030752/attachment.asc>

[Buildroot] Broken link in build notification

[Peter Korsgaard]

>>>>> "Zoltan" == Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com> writes:

 > Dear Thomas &All,
 > On 01/21/2018 08:00 AM, Thomas Petazzoni wrote:
 >> Hello,
 >> 
 >> This is the list of Buildroot build failures that occured on
 >> 2018-01-20, 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:
 >> 
 >> arm | proj-4.9.3 |
 >> http://autobuild.buildroot.net/results/80243a2ae19190d75e84a2ed8aa4b95a20ea9ef0
 >> 

 > I received this ^^ build error notification mail yesterday.

 > The link redirects to
 > https://bugs.busybox.net/results/80243a2ae19190d75e84a2ed8aa4b95a20ea9ef0,
 > and ends up in a 404.

Sorry, my fault. I am moving sources.buildroot.net to a new VM / behind
cloudflare, and DNS for autobuild.buildroot.net temporarily pointed at
the VM running bugs.busybox.net instead of the autobuild master.

There's also a few autobuilder failures because of this.

It should be fixed now, and sources.buildroot.net should be faster now.

-- 
Bye, Peter Korsgaard

[Buildroot] Broken link in build notification

[Zoltan Gyarmati]

Dear Peter,

On 01/22/2018 10:38 PM, Peter Korsgaard wrote:
>>>>>> "Zoltan" == Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com> writes:
>  > Dear Thomas &All,
>  > On 01/21/2018 08:00 AM, Thomas Petazzoni wrote:
>  >> Hello,
>  >> 
>  >> This is the list of Buildroot build failures that occured on
>  >> 2018-01-20, 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:
>  >> 
>  >> arm | proj-4.9.3 |
>  >> http://autobuild.buildroot.net/results/80243a2ae19190d75e84a2ed8aa4b95a20ea9ef0
>  >> 
>
>  > I received this ^^ build error notification mail yesterday.
>
>  > The link redirects to
>  > https://bugs.busybox.net/results/80243a2ae19190d75e84a2ed8aa4b95a20ea9ef0,
>  > and ends up in a 404.
>
> Sorry, my fault. I am moving sources.buildroot.net to a new VM / behind
> cloudflare, and DNS for autobuild.buildroot.net temporarily pointed at
> the VM running bugs.busybox.net instead of the autobuild master.
OK, thanks for the clarification.

> There's also a few autobuilder failures because of this.

I couldn't reproduce the linked build failure, so you think it's
probably because of this and it's safe to ignore?
>
> It should be fixed now, and sources.buildroot.net should be faster now.
>

Cool, thanks for the work on this!

Regards,


Zoltan Gyarmati
https://zgyarmati.de


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180125/e605cc4d/attachment.asc>

[Buildroot] Broken link in build notification

[Peter Korsgaard]

>>>>> "Zoltan" == Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com> writes:

Hi,

 >> Sorry, my fault. I am moving sources.buildroot.net to a new VM / behind
 >> cloudflare, and DNS for autobuild.buildroot.net temporarily pointed at
 >> the VM running bugs.busybox.net instead of the autobuild master.

> OK, thanks for the clarification.

 >> There's also a few autobuilder failures because of this.

 > I couldn't reproduce the linked build failure, so you think it's
 > probably because of this and it's safe to ignore?

I don't think it is because of the DNS change (which would cause E.G. a
download failure), but I do see that the error is a segfault of a host
utility, and the build happened on gcc67, which is a Ryzen based
machine. These early Ryzen CPUs had a number of problems and we saw
similar crashes, so we stopped using them for autobuilders. I got a
notification a few days ago that the CPU had been replaced, but the
problems apparently still occur, so I have stopped the autobuilder
again.

In other words, yes - You can ignore this error.

 >> It should be fixed now, and sources.buildroot.net should be faster now.
 >> 

 > Cool, thanks for the work on this!

You're welcome!

-- 
Bye, Peter Korsgaard