From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: FYI: Feasibility of CI on github
Date: Mon, 15 Feb 2021 12:30:35 +0100 [thread overview]
Message-ID: <20210215113035.GP20742@yssyq.m.ilbers.de> (raw)
In-Reply-To: <d45472b0-8290-01cf-a1dc-cc5b240a3758@siemens.com>
On Fri, Feb 12, 2021 at 05:55:23PM +0100, Jan Kiszka wrote:
> Time is not our primary issue (you can easily run the sequential parts
> of the CI script in separate jobs and gain quite a bit). It's the disk
> size. But when we want to stress the full mc: pool, there is likely no
> way around dedicated runners for the time being.
Yes, I think we might be able to improve on the parts (beyond just splitting
into steps), but the full mc seems like a challenge for the time being.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2021-02-15 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 12:53 Jan Kiszka
2021-02-12 9:16 ` Henning Schild
2021-02-12 10:01 ` Baurzhan Ismagulov
2021-02-12 10:28 ` Henning Schild
2021-02-12 10:53 ` Baurzhan Ismagulov
2021-02-12 16:55 ` Jan Kiszka
2021-02-15 11:30 ` Baurzhan Ismagulov [this message]
2021-02-12 19:20 ` Henning Schild
2021-02-15 11:27 ` Baurzhan Ismagulov
2021-02-15 13:45 ` Jan Kiszka
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=20210215113035.GP20742@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/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