public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH v2 1/3] ci: run vm_start tests right after targets that built it
Date: Fri, 24 Jul 2026 11:50:22 +0200	[thread overview]
Message-ID: <843c93d8-4a94-4940-840e-716b00fd9397@ilbers.de> (raw)
In-Reply-To: <20260720073703.3782697-2-felix.moessbauer@siemens.com>


On 7/20/26 09:37, 'Felix Moessbauer' via isar-users wrote:
> As a preparation to reduce the parsing effort, we need to order the
> vm_start tests right after the target that built the corresponding
> image. This is needed to ensure we still have the cache data for the
> to-be-booted configuration.

I was testing this series with the 2 KFAIL patches but did not notice
for this part. I put one KFAIL between a build and a corresponding
vm_start, then the vm_start failed as the ccache data was lost. Let me
reorganize the KFAILs and test again.

Zhihang

> Technically, this was already incorrect before, as the vm_start tests
> are related to a specific target that has to be built before execution.
> If other targets are built in-between, the vm that is executed for the
> test is likely not what was intended to be tested.
>

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/843c93d8-4a94-4940-840e-716b00fd9397%40ilbers.de.

  reply	other threads:[~2026-07-24  9:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20  7:37 [PATCH v2 0/3] speedup testsuite execution execution 'Felix Moessbauer' via isar-users
2026-07-20  7:37 ` [PATCH v2 1/3] ci: run vm_start tests right after targets that built it 'Felix Moessbauer' via isar-users
2026-07-24  9:50   ` Zhihang Wei [this message]
2026-07-20  7:37 ` [PATCH v2 2/3] testsuite: speedup execution by limiting mc parsing to selected targets 'Felix Moessbauer' via isar-users
2026-07-24 14:56   ` Zhihang Wei
2026-07-24 15:27     ` 'MOESSBAUER, Felix' via isar-users
2026-07-20  7:37 ` [PATCH v2 3/3] testsuite: remove duplicated cross test 'Felix Moessbauer' via isar-users

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=843c93d8-4a94-4940-840e-716b00fd9397@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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