Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Missing autobuild daily reports
Date: Thu, 09 Jul 2020 07:33:50 +0300	[thread overview]
Message-ID: <873661joi9.fsf@tarshish> (raw)
In-Reply-To: <20200704103446.6c9215f4@windsurf.home>

Hi Thomas,

On Sat, Jul 04 2020, Thomas Petazzoni wrote:
> On Thu, 02 Jul 2020 14:29:46 +0300
> Baruch Siach <baruch@tkos.co.il> wrote:
>
>> The last autobuild report was sent on June 26:
>> 
>>   http://lists.busybox.net/pipermail/buildroot/2020-June/285725.html
>> 
>> I find these daily reports useful.
>
> I had a look: I updated my server on June 27 to a newer Ubuntu version,
> and the _mysql Python module that the script is using is no longer
> available. I haven't immediately seen if _mysql was still available in
> some other package, so I'll probably have to adjust the code to use
> another MySQL Python module.

Thanks. It looks like you fixed the issue, but it somehow broke again
after two days:

  http://lists.busybox.net/pipermail/buildroot/2020-July/286004.html
  http://lists.busybox.net/pipermail/buildroot/2020-July/286018.html

Unrelated to that, there appears to be at least one low hanging
patchwork entry that could significantly improve autobuilder stats:

  http://patchwork.ozlabs.org/project/buildroot/patch/20200623101533.1459806-1-stefan.sorensen at spectralink.com/

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

      reply	other threads:[~2020-07-09  4:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 11:29 [Buildroot] Missing autobuild daily reports Baruch Siach
2020-07-04  8:34 ` Thomas Petazzoni
2020-07-09  4:33   ` Baruch Siach [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=873661joi9.fsf@tarshish \
    --to=baruch@tkos.co.il \
    --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