From: "Martin Liška" <mliska@suse.cz>
To: Mark Wielaard <mark@klomp.org>,
Overseers mailing list <overseers@sourceware.org>
Subject: Re: [PATCH] buildbot: come up with vm_workers variable
Date: Wed, 25 May 2022 22:00:09 +0200 [thread overview]
Message-ID: <3539a7b4-82b7-e6e7-4c84-04703cd9628c@suse.cz> (raw)
In-Reply-To: <809aa81709d0f431d79af3db7f0b1b5b7b767c31.camel@klomp.org>
On 5/25/22 16:46, Mark Wielaard wrote:
> Hi Martin,
>
> On Wed, 2022-05-25 at 14:55 +0200, Martin Liška via Overseers wrote:
>>
>> +vm_workers = ['bb1', 'bb2', 'bb3']
>> +
>
> Thanks. Applied.
Thank you.
>
> There are probably a lot more python simplifications/cleanups to be
> done. I admit I am mostly a python copy/paster...
Sure, but overall the buildbot config looks quite nice compared to what I have :)
Btw. can one somehow run the master.cfg validation locally?
Cheers,
Martin
>
> Cheers,
>
> Mark
next prev parent reply other threads:[~2022-05-25 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 12:55 Martin Liška
2022-05-25 14:46 ` Mark Wielaard
2022-05-25 20:00 ` Martin Liška [this message]
2022-05-25 21:24 ` Mark Wielaard
2022-05-26 8:40 ` Martin Liška
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=3539a7b4-82b7-e6e7-4c84-04703cd9628c@suse.cz \
--to=mliska@suse.cz \
--cc=mark@klomp.org \
--cc=overseers@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).