From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users <isar-users@googlegroups.com>
Subject: CI tests procedure
Date: Thu, 25 Apr 2019 11:25:16 +0300 [thread overview]
Message-ID: <136d22ad-cf57-e84b-4d0d-8bb7d0e40713@ilbers.de> (raw)
Hi everybody,
I see that there is a misunderstanding regarding CI test procedure.
CI tests procedure is described in section Development of
CONTRIBUTING.md (https://github.com/ilbers/isar/blob/next/CONTRIBUTING.md)
> 3. Test your code.
>
> * No regressions are introduced in the affected code.
>
> * Seemingly unaffected boards still build.
>
> * It's highly suggested to test your patchset before submitting it to the mailing
> by launching CI tests scripts. The procedure is described below:
>
> First, run "fast" CI
> ```
> scripts/ci_build.sh -q -f
> ...
> source isar-init-build-env
> scripts/vm_smoke_test -f
> ```
> Currently "fast" CI launches
> * parallel cross build of QEMU arm/arm64/amd64 Debian stretch and Raspberry Pi 1 Raspbian stretch targets
> * cross build of one of the supported boards which includes compilation of Linux kernel/U-Boot for it
> * Launches login prompt check tests for built QEMU targets
>
> Second, run standard CI
> ```
> scripts/ci_build.sh -q
> ...
> source isar-init-build-env
> scripts/vm_smoke_test -q
> ```
> Currently standard CI launches
> * parallel native build of QEMU arm/arm64/i386/amd64 Debian stretch/buster and Raspberry Pi 1 Raspbian stretch targets
> * Launches login prompt check tests for built QEMU targets
>
> Active developers may request from maintainers an account on isar-build.org
> to analyze CI logs or to launch their own CI builds there.
>
>
I hope, this paragraph eliminates further misunderstanding.
You may send patchsets not fully tested.
But patch set will be applied only if it passes the procedure above.
Anyway I encourage you to follow this procedure to avoid patchsets
iterations.
Regards,
Maxim.
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next reply other threads:[~2019-04-25 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 8:25 Maxim Yu. Osipov [this message]
2019-04-25 9:30 ` Claudius Heine
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=136d22ad-cf57-e84b-4d0d-8bb7d0e40713@ilbers.de \
--to=mosipov@ilbers.de \
--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