On 9/20/23 3:20 PM, Richard Purdie wrote:
On Wed, 2023-09-20 at 14:50 -0700, Robert Joslyn wrote:
On 9/19/23 5:54 AM, Richard Purdie wrote:
On Tue, 2023-09-19 at 05:40 -0700, Robert Joslyn wrote:
On 9/18/23 4:59 AM, Richard Purdie wrote:
On Sun, 2023-09-17 at 18:57 -0700, Robert Joslyn via
lists.openembedded.org wrote:
NSS support was removed, so adjust PACKAGECONFIG options.
The --enable-crypto-auth option was removed and split into separate
options for basic-auth, bearer-auth, digest-auth, kerberos-auth,
negotiate-auth, and aws. Enable basic, bearer, digest, and negotiate by
default as these are probably the most common.
Disable test 1279 since this requires libcurl and hangs the tests.
Signed-off-by: Robert Joslyn <robert.jos...@redrectangle.org>
---
meta/recipes-support/curl/curl/disable-tests | 1 +
.../curl/{curl_8.2.1.bb => curl_8.3.0.bb} | 14 +++++++++-----
2 files changed, 10 insertions(+), 5 deletions(-)
rename meta/recipes-support/curl/{curl_8.2.1.bb => curl_8.3.0.bb} (88%)
diff --git a/meta/recipes-support/curl/curl/disable-tests
b/meta/recipes-support/curl/curl/disable-tests
index b687b2bb76..fdac795662 100644
--- a/meta/recipes-support/curl/curl/disable-tests
+++ b/meta/recipes-support/curl/curl/disable-tests
@@ -21,6 +21,7 @@
# This test is scanning the source tree
1222
# These CRL tests need --libcurl option to be enabled
+1279
1400
1401
1402
Thanks for the patch. Unfortunately there were warnings generated on
the autobuilder test run for this:
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5452
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/5631
I'm not very familiar with the autobuilder infrastructure, but it looks
to be running something like "bitbake core-image-ptest-curl -c
testimage". When I run this, I do get a warning:
WARNING: core-image-ptest-curl-1.0-r0 do_testimage: There were failing
ptests.
Running with -v might help show a touch more information.
Unfortunately, I don't see any failing tests. When running the tests
manually (called runqemu, then ptest-runner curl in the VM) there are
some tests that print an error about not finding a library and get
skipped. I removed those test cases as well, but I still get the warning
about failing ptests.
What's the ptest code looking for to trigger a test failure? I should
have some more time to look at this later today, I'm probably just
missing something obvious.
Commands like:
resulttool report ./tmp/log/oeqa/
resulttool log --dump-ptest ./output-logs ./tmp/log/oeqa/
Might help amd/or have a look at the testimage log in core-image-ptest-
curl's WORKDIR/temp/log.do_testimage
Cheers,
Richard
In running this a few times, on my machine it's not curl but other tests
that fail. The autobuilder output only showed a curl failure, so I'm not
sure what's different in my environment. This is what resulttool shows:
s.robert@hezmana ~/yocto/poky-master/build $ resulttool report
./tmp/log/oeqa/
==============================================================================================================
Test Result Status Summary (Counts/Percentages sorted by testseries, ID)
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
Test Series | ID |
Passed | Failed | Skipped
--------------------------------------------------------------------------------------------------------------
oeqa | runtime_core-image-ptest-curl_qemux86-64_20230920012443 | 4725
(91%) | 7 (0%) | 448 (9%)
--------------------------------------------------------------------------------------------------------------
Total | 1 | 4725 | 7 | 448
--------------------------------------------------------------------------------------------------------------
==============================================================================================================
qemux86-64 PTest Result Summary
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
Recipe | Passed | Failed | Skipped | Time(s)
--------------------------------------------------------------------------------------------------------------
attr | 2 | 0 | 0 | 0
bash | 78 | 5 | 0 | 107
busybox | 619 | 0 | 88 | 7
curl | 847 | 0 | 0 | 188
openssh | 81 | 0 | 1 | 712
openssl | 0 | 0 | 0 | 0
perl | 2570 | 1 | 192 | 549
util-linux | 524 | 1 | 166 | 36
zlib | 1 | 0 | 0 | 0
--------------------------------------------------------------------------------------------------------------
==============================================================================================================
Failed test cases (sorted by testseries, ID)
==============================================================================================================
--------------------------------------------------------------------------------------------------------------
testseries | result_id : oeqa |
runtime_core-image-ptest-curl_qemux86-64_20230920012443
ptestresult.bash.run-array
ptestresult.bash.run-execscript
ptestresult.bash.run-intl
ptestresult.bash.run-read
ptestresult.bash.run-shopt
ptestresult.perl.cpan/ExtUtils-Constant/t/Constant
ptestresult.util-linux.mount:_complex
--------------------------------------------------------------------------------------------------------------
I posted the output from a manual ptest-runner call here:
https://gist.github.com/bobolopolis/e02401a87d1d6b2f48ca2d70998f13c1
If you delete or move tmp/log/oeqa/ out the way, you effectively reset
the state so if you do that, then just run the curl ptest the result
should be clearer.
I did go back and look up the autobuilder failure and tried to dig up
more logs:
http://autobuilder.yocto.io/pub/non-release/20230918-9/testresults/qemux86-64-ptest/curl.log
http://autobuilder.yocto.io/pub/non-release/20230918-9/testresults/qemux86-64-ptest/core-image-ptest-curl/log.do_testimage.4047690.20230918105238
http://autobuilder.yocto.io/pub/non-release/20230918-9/testresults/qemuarm64-ptest/curl.log
http://autobuilder.yocto.io/pub/non-release/20230918-9/testresults/qemuarm64-ptest/core-image-ptest-curl/log.do_testimage.59151.20230918103439
so it was test 1964 that failed in both cases. I know know why though
:/
Cheers,
Richard
Interestingly, that test gets skipped for me (on both x86-64 and arm64):
test 1964... 1964: IGNORED: The tool set in the test case for this:
'lib1964' does not exist
That test looks related to the aws authentication feature that is
disabled via PACKAGECONFIG and is a new flag in this version. I can send
an updated patch enabling that to see if it changes anything, although
I'm still not sure why I see different behavior than the autobuilder.
Thanks,
Robert
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187969):
https://lists.openembedded.org/g/openembedded-core/message/187969
Mute This Topic: https://lists.openembedded.org/mt/101426058/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
