From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <mark.jonas@de.bosch.com>, <openembedded-core@lists.openembedded.org>
Cc: <jpewhacker@gmail.com>, <raj.khem@gmail.com>,
"Ricardo Simoes" <ricardo.simoes@pt.bosch.com>
Subject: Re: [OE-core] [PATCH] dosfstools: Add ptests
Date: Fri, 11 Jul 2025 13:22:46 +0200 [thread overview]
Message-ID: <DB96QW0DBI2N.11E6ASE04WBX6@bootlin.com> (raw)
In-Reply-To: <20250710142015.174053-1-mark.jonas@de.bosch.com>
On Thu Jul 10, 2025 at 4:20 PM CEST, Mark Jonas via lists.openembedded.org wrote:
> From: Ricardo Simoes <ricardo.simoes@pt.bosch.com>
>
> Signed-off-by: Ricardo Simoes <ricardo.simoes@pt.bosch.com>
> Signed-off-by: Mark Jonas <mark.jonas@de.bosch.com>
> ---
Hi Ricardo,
Thanks for your patch!
It looks like some of the added ptests are failing:
WARNING: core-image-ptest-dosfstools-1.0-r0 do_testimage: There were failing ptests.
...
{'dosfstools': 'START: ptest-runner\n'
'2025-07-11T10:03\n'
'make test-mkfs test-fsck test-label referenceFAT12.mkfs '
'referenceFAT12.xxd referenceFAT16.mkfs referenceFAT16.xxd '
'referenceFAT32.mkfs referenceFAT32.xxd referenceFAT32mbr.mkfs '
'referenceFAT32mbr.xxd mkfs-fat32_2_res_sects.mkfs '
'mkfs-fat32_2_res_sects.xxd mkfs-fat32_4K.mkfs '
'mkfs-fat32_4K.xxd check-bad_names.fsck check-bad_names.xxd '
'check-fat12_first_cluster.fsck check-fat12_first_cluster.args '
'check-fat12_first_cluster.xxd check-fat16_first_cluster.fsck '
'check-fat16_first_cluster.args check-fat16_first_cluster.xxd '
'check-fat32_first_cluster.fsck check-fat32_first_cluster.args '
'check-fat32_first_cluster.xxd check-fat16_dos_cln_shut.fsck '
'check-fat16_dos_cln_shut.xxd check-fat32_dos_cln_shut.fsck '
'check-fat32_dos_cln_shut.xxd check-chain_to_free_cluster.fsck '
'check-chain_to_free_cluster.xxd check-chain_too_long.fsck '
'check-chain_too_long.xxd check-chain_to_other_file.fsck '
'check-chain_to_other_file.xxd check-circular_chain.fsck '
'check-circular_chain.xxd check-duplicate_names.fsck '
'check-duplicate_names.xxd check-dot_entries.fsck '
'check-dot_entries.xxd check-huge.fsck '
'check-label-different.fsck check-label-different.xxd '
'check-label-only-boot.fsck check-label-only-boot.xxd '
'check-label-only-root.fsck check-label-only-root.xxd '
'label-fat32_mkdosfs_label1_dosfslabel_empty.label '
'label-fat32_mkdosfs_label1_dosfslabel_empty.xxd '
'label-fat32_mkdosfs_label1_dosfslabel_label2.label '
'label-fat32_mkdosfs_label1_dosfslabel_label2.xxd '
'label-fat32_mkdosfs_label1_dosfslabel_NO_NAME.label '
'label-fat32_mkdosfs_label1_dosfslabel_NO_NAME.xxd '
'label-fat32_mkdosfs_label1_mlabel_erase.label '
'label-fat32_mkdosfs_label1_mlabel_erase.xxd '
'label-fat32_mkdosfs_label1_mlabel_NO_NAME.label '
'label-fat32_mkdosfs_label1_mlabel_NO_NAME.xxd '
'label-fat32_mkdosfs_label1_xp_erase.label '
'label-fat32_mkdosfs_label1_xp_erase.xxd '
'label-fat32_mkdosfs_label1_xp_label2.label '
'label-fat32_mkdosfs_label1_xp_label2.xxd '
'label-fat32_mkdosfs_label1.label '
'label-fat32_mkdosfs_label1.xxd '
'label-fat32_mkdosfs_none_dosfslabel_label1_xp_label2.label '
'label-fat32_mkdosfs_none_dosfslabel_label1_xp_label2.xxd '
'label-fat32_mkdosfs_none_dosfslabel_label1.label '
'label-fat32_mkdosfs_none_dosfslabel_label1.xxd '
'label-fat32_mkdosfs_none_dosfslabel_NO_NAME.label '
'label-fat32_mkdosfs_none_dosfslabel_NO_NAME.xxd '
'label-fat32_mkdosfs_none_xp_label1_dosfslabel_label2.label '
'label-fat32_mkdosfs_none_xp_label1_dosfslabel_label2.xxd '
'label-fat32_mkdosfs_none_xp_label1.label '
'label-fat32_mkdosfs_none_xp_label1.xxd '
'label-fat32_mkdosfs_none.label label-fat32_mkdosfs_none.xxd '
'label-fat32_xp_label1.label label-fat32_xp_label1.xxd '
'label-fat32_xp_none_dosfslabel_label1.label '
'label-fat32_xp_none_dosfslabel_label1.xxd '
'label-fat32_xp_none_mlabel_label1.label '
'label-fat32_xp_none_mlabel_label1.xxd '
'label-fat32_xp_none.label label-fat32_xp_none.xxd\n'
'make: /bin/bash: No such file or directory\n'
'make: *** [Makefile:858: check-am] Error 127\n'
'\n'
'ERROR: Exit status is 2\n'
'DURATION: 0\n'}
ptests which had no test results:
['dosfstools']
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/1880
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/201
Full ptest logs can be found here:
https://valkyrie.yocto.io/pub/non-release/20250711-49/testresults/qemux86-64-ptest/core-image-ptest-dosfstools/
https://valkyrie.yocto.io/pub/non-release/20250711-47/testresults/qemuriscv64-ptest/core-image-ptest-dosfstools/
Can you have a look at these failures please?
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-07-11 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 14:20 [PATCH] dosfstools: Add ptests mark.jonas
2025-07-11 11:22 ` Mathieu Dubois-Briand [this message]
2025-07-11 15:47 ` AW: [OE-core] " Jonas Mark (BT-FS/ENG1-Mue)
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=DB96QW0DBI2N.11E6ASE04WBX6@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=jpewhacker@gmail.com \
--cc=mark.jonas@de.bosch.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ricardo.simoes@pt.bosch.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