From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Daily results for 2022-03-19
Date: Wed, 23 Mar 2022 20:13:47 +0100 [thread overview]
Message-ID: <20220323191347.GA3631434@scaer> (raw)
In-Reply-To: <pan$6077$b8209ef6$6f8a81d5$e9ac7c56@ID-313208.user.individual.net>
Bernd, All,
On 2022-03-23 19:06 +0100, Bernd Kuhls spake thusly:
> Am Sun, 20 Mar 2022 08:21:56 -0000 schrieb Thomas Petazzoni via buildroot:
> > Autobuild statistics for 2022-03-19
> it seems that there could be a problem with mails sent by the autobuilders.
> Since the beginning of March many days went by without the daily results:
> https://lore.kernel.org/buildroot/?q=Daily+results
Yes, we are aware of the issue. The script is more often than not killed
by OOM...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-03-23 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220320082201.6612060B1F__26257.1082961344$1647764544$gmane$org@smtp3.osuosl.org>
2022-03-23 18:06 ` [Buildroot] [autobuild.buildroot.net] Daily results for 2022-03-19 Bernd Kuhls
2022-03-23 19:13 ` Yann E. MORIN [this message]
2022-03-20 8:21 Thomas Petazzoni via buildroot
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=20220323191347.GA3631434@scaer \
--to=yann.morin.1998@free.fr \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@uclibc.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.