From: "qiutt@fujitsu.com" <qiutt@fujitsu.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V1] e2fsprogs: fix ptest bug for second running
Date: Thu, 04 May 2023 19:30:42 -0700 [thread overview]
Message-ID: <5798.1683253842910945486@lists.openembedded.org> (raw)
In-Reply-To: <CAMKF1soZiL82M5y14agXb=OBU4Y3EeqUp=nzpD-kWO95q_z+3Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 124 bytes --]
Hi, Khem Raj
It may be mangled by my mailer.
Could you use the attachments and try again?
Thanks,
Qiu Tingting
[-- Attachment #1.2: Type: text/html, Size: 6232 bytes --]
[-- Attachment #2: 0001-e2fsprogs-fix-ptest-bug-for-second-running.patch --]
[-- Type: application/octet-stream, Size: 1572 bytes --]
From db4b5e31703e4143450b1e7239b2502a89ed042a Mon Sep 17 00:00:00 2001
From: Qiu Tingting <qiutt@fujitsu.com>
Date: Thu, 27 Apr 2023 15:29:14 +0800
Subject: [PATCH V1] e2fsprogs: fix ptest bug for second running
At second running, there are four new failed case:
d_loaddump f_bigalloc_badinode f_bigalloc_orphan_list f_dup_resize
The test_data.tmp is necessary, but it is deleted by run-ptest.
So it should be restored after testing.
Signed-off-by: Qiu Tingting <qiutt@fujitsu.com>
---
meta/recipes-devtools/e2fsprogs/e2fsprogs/run-ptest | 1 +
meta/recipes-devtools/e2fsprogs/e2fsprogs_1.47.0.bb | 3 +++
2 files changed, 4 insertions(+)
diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs/run-ptest b/meta/recipes-devtools/e2fsprogs/e2fsprogs/run-ptest
index c97c0377e9..279923db8e 100644
--- a/meta/recipes-devtools/e2fsprogs/e2fsprogs/run-ptest
+++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs/run-ptest
@@ -8,3 +8,4 @@ rm -f *.tmp
rm -f *.ok
rm -f *.failed
rm -f *.log
+cp ../data/test_data.tmp ./
diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.47.0.bb b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.47.0.bb
index a2eb4f8f8f..87e13d744b 100644
--- a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.47.0.bb
+++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.47.0.bb
@@ -143,4 +143,7 @@ do_install_ptest() {
install -d ${D}${PTEST_PATH}/lib
install -m 0644 ${B}/lib/config.h ${D}${PTEST_PATH}/lib/
+
+ install -d ${D}${PTEST_PATH}/data
+ install -m 0644 ${B}/tests/test_data.tmp ${D}${PTEST_PATH}/data/
}
--
2.25.1
prev parent reply other threads:[~2023-05-05 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 8:26 [PATCH V1] e2fsprogs: fix ptest bug for second running qiutt
2023-05-04 16:24 ` [OE-core] " Khem Raj
2023-05-05 1:05 ` qiutt
2023-05-05 2:30 ` qiutt [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=5798.1683253842910945486@lists.openembedded.org \
--to=qiutt@fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
/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