public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH v1 0/4] Add developers test
Date: Tue, 29 Nov 2022 12:57:57 +0000	[thread overview]
Message-ID: <1416ceeef4ee3aa7a018f1ddca6bcff4121a204e.camel@siemens.com> (raw)
In-Reply-To: <20221129114344.19128-1-amikan@ilbers.de>

On Tue, 2022-11-29 at 14:43 +0300, Anton Mikanovich wrote:
> Add separate quick 'developers' test for fast checking new patches.

Looks like this feature is added for me :)

> It will test only general Isar logic on basic targets without dealing
> with
> all the functionality.
> To execute dev test run avocado testsuite like:
> 
> $ avocado run ../testsuite/citest.py -t dev --nrunner-max-parallel-
> tasks=1

Can we please put this into the documentation.
Otherwise nobody will find it.

Felix

> 
> Estimated execution time for dev test is ~20 min.
> 
> Anton Mikanovich (4):
>   CI: Enable downloads dir sharing
>   CI: Add IMAGE_INSTALL override
>   CI: Add developers test
>   CI: Remove duplicated target
> 
>  testsuite/cibuilder.py | 12 +++++++++++-
>  testsuite/citest.py    | 33 ++++++++++++++++++++++++++++++++-
>  2 files changed, 43 insertions(+), 2 deletions(-)
> 
> -- 
> 2.17.1
> 


      parent reply	other threads:[~2022-11-29 12:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 11:43 Anton Mikanovich
2022-11-29 11:43 ` [PATCH v1 1/4] CI: Enable downloads dir sharing Anton Mikanovich
2022-11-29 11:43 ` [PATCH v1 2/4] CI: Add IMAGE_INSTALL override Anton Mikanovich
2022-11-29 11:43 ` [PATCH v1 3/4] CI: Add developers test Anton Mikanovich
2022-11-29 11:43 ` [PATCH v1 4/4] CI: Remove duplicated target Anton Mikanovich
2022-11-29 12:57 ` Moessbauer, Felix [this message]

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=1416ceeef4ee3aa7a018f1ddca6bcff4121a204e.camel@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=amikan@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