From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 0/3] Add skeleton dir option
Date: Thu, 1 Aug 2019 18:10:11 +0200 [thread overview]
Message-ID: <20190801161010.GM14716@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20190731164904.4f316119@md1za8fc.ad001.siemens.net>
On Wed, Jul 31, 2019 at 04:49:04PM +0200, Henning Schild wrote:
> Did you run the test at least 5 times? That CI is random and can not be
> trusted. Just rebuild master or next ... you are very likely to fail.
The connection is flaky at random moments. While we troubleshoot the problem,
I've ordered a server at the ISP premises, will migrate ci.i-b.o there and let
you know.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-08-01 16:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 12:36 Quirin Gylstorff
2019-07-19 12:38 ` [PATCH 1/3] image-account-extension: " Quirin Gylstorff
2019-07-19 12:38 ` [PATCH 2/3] meta-isar: Add example for user settings Quirin Gylstorff
2019-07-23 8:08 ` Henning Schild
2019-07-23 12:00 ` Quirin Gylstorff
2019-07-23 12:03 ` [PATCH 0/3] Add skeleton dir option Quirin Gylstorff
2019-07-23 12:06 ` Quirin Gylstorff
2019-07-23 12:06 ` [PATCH v2 1/3] image-account-extension: " Quirin Gylstorff
2019-07-23 12:06 ` [PATCH v2] ubifs-img: Correct function name Quirin Gylstorff
2019-07-23 12:06 ` [PATCH v2 2/3] meta-isar: Add example for user settings Quirin Gylstorff
2019-07-23 12:06 ` [PATCH v2 3/3] image-account-extension:Move configure_accounts to postprocess Quirin Gylstorff
2019-07-29 21:25 ` [PATCH 0/3] Add skeleton dir option Baurzhan Ismagulov
2019-07-31 11:44 ` Quirin Gylstorff
2019-07-31 12:40 ` Baurzhan Ismagulov
2019-07-31 14:49 ` Henning Schild
2019-07-31 17:23 ` Baurzhan Ismagulov
2019-08-01 16:10 ` Baurzhan Ismagulov [this message]
2019-08-01 7:02 ` Quirin Gylstorff
2019-08-01 9:50 ` Baurzhan Ismagulov
2019-08-01 14:23 ` Quirin Gylstorff
2019-07-19 12:38 ` [PATCH 3/3] image-account-extension:Move configure_accounts to postprocess Quirin Gylstorff
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=20190801161010.GM14716@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