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 <[email protected]>
> > > ---
> > >   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

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187862): 
https://lists.openembedded.org/g/openembedded-core/message/187862
Mute This Topic: https://lists.openembedded.org/mt/101426058/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to