From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 0/3] Fix failed repro test impact on other tests
Date: Fri, 8 Apr 2022 07:31:07 +0200 [thread overview]
Message-ID: <20220408053110.10416-1-ubely@ilbers.de> (raw)
When full set of tests is run, repro tests are run first. If there was
an error during repro tests, workdir was not cleaned and this caused
problems with the following tests.
Uladzimir Bely (3):
ci: cleanup tmp after repro test failed
ci: rename tmp in repro tests to access logs
deb-dl-dir: grep exact version when caching source package
meta/classes/deb-dl-dir.bbclass | 2 +-
testsuite/cibase.py | 3 ---
testsuite/cibuilder.py | 4 ++++
testsuite/citest.py | 10 ++++++++--
4 files changed, 13 insertions(+), 6 deletions(-)
--
2.20.1
next reply other threads:[~2022-04-08 5:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 5:31 Uladzimir Bely [this message]
2022-04-08 5:31 ` [PATCH 1/3] ci: cleanup tmp after repro test failed Uladzimir Bely
2022-04-08 5:31 ` [PATCH 2/3] ci: rename tmp in repro tests to access logs Uladzimir Bely
2022-04-08 5:31 ` [PATCH 3/3] deb-dl-dir: grep exact version when caching source package Uladzimir Bely
2022-05-04 7:49 ` [PATCH 0/3] Fix failed repro test impact on other tests Anton Mikanovich
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=20220408053110.10416-1-ubely@ilbers.de \
--to=ubely@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