Skip to contentSkip to conversation

strace: 6.17 -> 6.18

PATCH In review [email protected] 2 participants 10 messages Dec 16, 2025 – Dec 25, 2025

lore
Share & tools
lore
#0 lore raw

cover strace: 6.17 -> 6.18

From: Robert Yang <[email protected]>

The following changes since commit 2e10e9a50f12d5de3d22fbed59b65461afa3fa84:

Change CPAN_MIRROR to the address where it resolves. (2025-12-15 18:00:31 +0000)

are available in the Git repository at:

https://github.com/robertlinux/yocto rbt/strace
https://github.com/robertlinux/yocto/tree/rbt/strace

Robert Yang (1):
strace: 6.17 -> 6.18

 meta/recipes-devtools/strace/{strace_6.17.bb => strace_6.18.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/strace/{strace_6.17.bb => strace_6.18.bb} (96%)
Signature · 1 line
2.49.0
#1 lore raw

PATCH 1/1 strace: 6.17 -> 6.18

From: Robert Yang <[email protected]>

The 6.17 has 27 failed test cases, and 6.18 only has 2 failed ones:
FAIL: bpf.gen.test
FAIL: bpf-v.gen.test

---
 meta/recipes-devtools/strace/{strace_6.17.bb => strace_6.18.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/strace/{strace_6.17.bb => strace_6.18.bb} (96%)
meta/recipes-devtools/strace/strace_6.18.bb renamed from meta/recipes-devtools/strace/strace_6.17.bb +1 -1
similarity index 96%
rename from meta/recipes-devtools/strace/strace_6.17.bb
rename to meta/recipes-devtools/strace/strace_6.18.bb
index b6fda2b8ce..dfb07c3a73 100644
@@ -18,7 +18,7 @@ SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/strace-${PV}.tar.xz \
 SRC_URI:append:libc-musl = "\
            file://0001-Ignore-pwritev-pwrite64-tests-on-musl.patch \
            "
-SRC_URI[sha256sum] = "0a7c7bedc7efc076f3242a0310af2ae63c292a36dd4236f079e88a93e98cb9c0"
+SRC_URI[sha256sum] = "0ad5dcba973a69e779650ef1cb335b12ee60716fc7326609895bd33e6d2a7325"
 
 inherit autotools github-releases ptest
 
Signature · 1 line
2.49.0
#2 lore raw
Quoted 3 lines · Robert Yang via lists.openembedded.org

The 6.17 has 27 failed test cases, and 6.18 only has 2 failed ones:
FAIL: bpf.gen.test
FAIL: bpf-v.gen.test

This needs a bit more context. If the old version had failures, and the new version still has failures, why aren't they seen in testing? Where and how do they happen? Should they be fixed rather?

Alex

#3 lore raw

Hi Alexander,

Quoted 8 lines · Alexander Kanavin
Quoted 3 lines · Robert Yang via lists.openembedded.org

The 6.17 has 27 failed test cases, and 6.18 only has 2 failed ones:
FAIL: bpf.gen.test
FAIL: bpf-v.gen.test

This needs a bit more context. If the old version had failures, and the new version still has failures, why aren't they seen in testing?

They are ptest failures, and there is no specific test for it, so we don't see the failures. I did look into the failures, but didn't know how to fix that, the newer version has less failures than the older one, so I sent the upgrade patch.

// Robert

Quoted 2 lines

Where and how do they happen? Should they be fixed rather?

Quoted 1 line

Alex

#4 lore raw
Quoted 10 lines · Robert Yang
Quoted 6 lines
Quoted 3 lines

The 6.17 has 27 failed test cases, and 6.18 only has 2 failed ones:
FAIL: bpf.gen.test
FAIL: bpf-v.gen.test

This needs a bit more context. If the old version had failures, and the new version still has failures, why aren't they seen in testing?

They are ptest failures, and there is no specific test for it, so we don't see the failures. I did look into the failures, but didn't know how to fix that, the newer version has less failures than the older one, so I sent the upgrade patch.

But we do run strace ptests, and they do not fail, e.g. with latest nightly master:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2761/steps/14/logs/stdio

Does bitbake -c testimage core-image-ptest-strace fail for you? How did you set up and ran the tests to see them fail?

Alex

#5 lore raw

Hi Alexander,

Quoted 12 lines · Alexander Kanavin
Quoted 10 lines · Robert Yang
Quoted 6 lines
Quoted 3 lines

The 6.17 has 27 failed test cases, and 6.18 only has 2 failed ones:
FAIL: bpf.gen.test
FAIL: bpf-v.gen.test

This needs a bit more context. If the old version had failures, and the new version still has failures, why aren't they seen in testing?

They are ptest failures, and there is no specific test for it, so we don't see the failures. I did look into the failures, but didn't know how to fix that, the newer version has less failures than the older one, so I sent the upgrade patch.

Quoted 7 lines

But we do run strace ptests, and they do not fail, e.g. with latest nightly master:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2761/steps/14/logs/stdio

Does bitbake -c testimage core-image-ptest-strace fail for you? How did you set up and ran the tests to see them fail?

You didn't see the failure is because core-image-ptest has PTEST_EXPECT_FAILURE as reported by Qi:

https://lists.openembedded.org/g/openembedded-core/message/227411

I can see the failure after applied Qi's patches. Or we can manually see the failures via:

# pest-runner strace

// Robert

Quoted 2 lines

Alex

#6 lore raw
Quoted 8 lines · Robert Yang
Quoted 7 lines

But we do run strace ptests, and they do not fail, e.g. with latest nightly master:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2761/steps/14/logs/stdio

Does bitbake -c testimage core-image-ptest-strace fail for you? How did you set up and ran the tests to see them fail?

Quoted 8 lines

You didn't see the failure is because core-image-ptest has PTEST_EXPECT_FAILURE as reported by Qi:

https://lists.openembedded.org/g/openembedded-core/message/227411

I can see the failure after applied Qi's patches. Or we can manually see the failures via:

# pest-runner strace

Even without Qi's patches, if a ptest failure happens, autobuilder will report it as a warning, and for 6.17 those were not happening either in autobuilder or for me locally. But 6.18 did indeed start to fail in the two bpf tests, so we had to patch them out:

https://git.openembedded.org/openembedded-core/log/?h=master-next

So there's probably something in your configuration that triggers those fails in 6.17 that doesn't happen in standard poky.

Alex

#7 lore raw
Quoted 24 lines · Alexander Kanavin
Quoted 8 lines · Robert Yang
Quoted 7 lines

But we do run strace ptests, and they do not fail, e.g. with latest nightly master:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/2761/steps/14/logs/stdio

Does bitbake -c testimage core-image-ptest-strace fail for you? How did you set up and ran the tests to see them fail?

Quoted 8 lines

You didn't see the failure is because core-image-ptest has PTEST_EXPECT_FAILURE as reported by Qi:

https://lists.openembedded.org/g/openembedded-core/message/227411

I can see the failure after applied Qi's patches. Or we can manually see the failures via:

# pest-runner strace

Even without Qi's patches, if a ptest failure happens, autobuilder will report it as a warning, and for 6.17 those were not happening either in autobuilder or for me locally. But 6.18 did indeed start to fail in the two bpf tests, so we had to patch them out:

Quoted 4 lines

https://git.openembedded.org/openembedded-core/log/?h=master-next

So there's probably something in your configuration that triggers those fails in 6.17 that doesn't happen in standard poky.

You're right! All test cases are passed in 6.17:

# TOTAL: 1450
# PASS: 1121
# SKIP: 329
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0

So we should hold on this upgrading.

I didn't use core-image-ptest-strace in previous testing, but test it manually with core-image-sato, so I got the failures on 6.17.

// Robert

Quoted 2 lines

Alex

#8 lore raw
Quoted 10 lines · Robert Yang

You're right! All test cases are passed in 6.17:

# TOTAL: 1450
# PASS: 1121
# SKIP: 329
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0

Quoted 4 lines

So we should hold on this upgrading.

I didn't use core-image-ptest-strace in previous testing, but test it manually with core-image-sato, so I got the failures on 6.17.

The upgrade has already merged, as it was needed for the kernel updates. The two failing bpf tests were patched out so that reset can pass.

Alex

#9 lore raw
Quoted 11 lines · Alexander Kanavin
Quoted 10 lines · Robert Yang

You're right! All test cases are passed in 6.17:

# TOTAL: 1450
# PASS: 1121
# SKIP: 329
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0

Quoted 8 lines
Quoted 4 lines

So we should hold on this upgrading.

I didn't use core-image-ptest-strace in previous testing, but test it manually with core-image-sato, so I got the failures on 6.17.

The upgrade has already merged, as it was needed for the kernel updates. The two failing bpf tests were patched out so that reset can pass.

Thank you very much!

// Robert

Quoted 2 lines

Alex