public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/8] Cleanup rootfs creation
Date: Thu, 25 Apr 2019 11:51:09 +0200	[thread overview]
Message-ID: <20190425095109.GH21981@yssyq.m.ilbers.de> (raw)
In-Reply-To: <6f41982e-7b01-d02c-7785-297061eb8cd4@siemens.com>

On Thu, Apr 25, 2019 at 11:11:21AM +0200, Claudius Heine wrote:
> That is not a CI test procedure. That is a test procedure for local testing,
> if someone wants to use the ci scripts to do so. I don't since my
> environment is different from what you have on your CI server.

The CI server doesn't have any magic environment. It's set up according to
doc/user_manual.md#getting-started. scripts/ci_build.sh and
scripts/vm_smoke_test are expected to be able to run locally or on the server.
Of course, you can run any part of that manually if you are not comfortable
running the whole. This is the motivation of moving to Avocado -- to break the
big script into more maintainable and short pieces, so one could directly see
which particular test case has failed and restart just that one.


> > The problem that if we include all the features into single CI run it
> > will takes hours to test single patch.
> 
> Right. "abysmal slow". But in your 'CONTRIBUTERS' you state that everyone
> should do that anyway. Manually.

This is what the maintainer does for every series. Isar supports many features
on a number of platforms; testing all does cost time. We don't ask that every
developer does that routinely (though that is in your interest to get the patch
applied quickly); responding to a specific failure is enough.


With kind regards,
Baurzhan.

  parent reply	other threads:[~2019-04-25  9:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  9:27 claudius.heine.ext
2019-04-24  9:27 ` [PATCH v3 1/8] isar-boostrap-helper: move 'HOST_ARCH' and 'HOST_DISTRO' to base.bbclass claudius.heine.ext
2019-04-25 11:25   ` Claudius Heine
2019-04-24  9:27 ` [PATCH v3 2/8] move 'HOST_DISTRO_APT_SOURCES' from bootstrap-helper to isar-bootstrap claudius.heine.ext
2019-04-24  9:27 ` [PATCH v3 3/8] buildchroot.bbclass: only cross build if HOST_ARCH != DISTRO_ARCH claudius.heine.ext
2019-04-24  9:27 ` [PATCH v3 4/8] isar-bootstrap/buildchroot/sdkchroot: refactor PF and WORKDIR claudius.heine.ext
2019-04-24  9:27 ` [PATCH v3 5/8] bitbake.conf: remove unneeded and differently used variables claudius.heine.ext
2019-04-24  9:27 ` [PATCH v3 6/8] image.bbclass: make IMAGE_ROOTFS overwritable claudius.heine.ext
2019-04-24  9:27 ` [PATCH v3 7/8] bitbake.conf: set default QEMU_ARCH variables claudius.heine.ext
2019-04-24  9:27 ` [PATCH v3 8/8] buildchroot/configscript: make creation of builder uid/gid idempotent claudius.heine.ext
2019-04-25  6:03 ` [PATCH v3 0/8] Cleanup rootfs creation Maxim Yu. Osipov
2019-04-25  6:40   ` Claudius Heine
2019-04-25  7:55     ` Maxim Yu. Osipov
2019-04-25  8:01       ` Claudius Heine
2019-04-25  8:07         ` Maxim Yu. Osipov
2019-04-25  8:27           ` Claudius Heine
2019-04-25  8:39             ` Maxim Yu. Osipov
2019-04-25  9:11               ` Claudius Heine
2019-04-25  9:33                 ` Maxim Yu. Osipov
2019-04-25  9:51                 ` Baurzhan Ismagulov [this message]
2019-04-25 10:32                 ` Baurzhan Ismagulov
2019-04-25 11:18                   ` Claudius Heine
2019-04-25 11:22                     ` Claudius Heine
2019-04-25  8:52     ` 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=20190425095109.GH21981@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