From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [DISCUSSIONS] CI build
Date: Thu, 23 May 2019 14:11:09 +0200 [thread overview]
Message-ID: <20190523121108.GD2441@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20190523133537.602bacbd@md1za8fc.ad001.siemens.net>
On Thu, May 23, 2019 at 01:35:37PM +0200, Henning Schild wrote:
> > - Unreliable build:
> > -> Network and other unrelated issues to the patch
> > -> Contains expected to fail tests
>
> Agreed, i stopped running the tests locally because i could never come
> up with the same errors. Actually the CI itself could never come up
> with the same ones .... but it kept failing without giving a real clue
> why.
...
> > -> Giant log file, that makes it difficult to figure out
> > exactly which command or test case caused an issue to reproduce that
> > locally
>
> When i use the CI system from Ilbers i usually carry around a few "fast
> CI" patches on top of my real changes. In there i configure CI to do
> what i want and only build one config to start with. Not elegant but
> works somehow.
Feel free to report problems and / or send patches when your encounter the
issues, otherwise we never know you have one.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-05-23 12:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 7:26 Claudius Heine
2019-05-22 8:20 ` Maxim Yu. Osipov
2019-05-22 9:10 ` Claudius Heine
2019-05-22 9:50 ` Maxim Yu. Osipov
2019-05-22 11:28 ` Claudius Heine
2019-05-23 8:10 ` Claudius Heine
2019-05-23 13:43 ` Claudius Heine
2019-05-23 13:56 ` Maxim Yu. Osipov
2019-05-23 14:36 ` Claudius Heine
2019-05-22 19:44 ` Baurzhan Ismagulov
2019-05-23 4:44 ` Jan Kiszka
2019-05-23 8:32 ` Claudius Heine
2019-05-23 8:39 ` Jan Kiszka
2019-05-23 10:58 ` Maxim Yu. Osipov
2019-05-23 11:35 ` Henning Schild
2019-05-23 12:11 ` Baurzhan Ismagulov [this message]
2019-05-30 8:29 ` Jenkins project configuration by user Maxim Yu. Osipov
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=20190523121108.GD2441@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