Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Ross Burton <Ross.Burton@arm.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2] libssh2: Upgrade to v1.11.0
Date: Thu, 15 Jun 2023 00:38:06 +0200	[thread overview]
Message-ID: <20230614223806a87d7d51@mail.local> (raw)
In-Reply-To: <CADVatmP44NPGaUnZRLKu9Z1AmFQ1vtPwv7eKwHFsV7yC1ywcFg@mail.gmail.com>

On 14/06/2023 21:29:56+0100, Sudip Mukherjee wrote:
> On Wed, 14 Jun 2023 at 16:47, Ross Burton <Ross.Burton@arm.com> wrote:
> >
> > On 14 Jun 2023, at 16:13, Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:
> > >
> > > Hi Ross,
> > >
> > > On Wed, 14 Jun 2023 at 14:53, Ross Burton <ross.burton@arm.com> wrote:
> > >>
> > >> On 13 Jun 2023, at 21:52, Sudip Mukherjee via lists.openembedded.org <sudipm.mukherjee=gmail.com@lists.openembedded.org> wrote:
> > >>> # only one of openssl and gcrypt could be set
> 
> <snip>
> 
> > >>> mkdir -p ${D}${PTEST_PATH}/docs
> > >>> cp -r ${S}/docs/* ${D}${PTEST_PATH}/docs/
> > >>> }
> > >>
> > >> As you’ve clearly been looking at the tests, why does the ptest support need the documentation?
> > >
> > > There is a test for manpage syntax "mansyntax.sh" which needs the
> > > generated man pages in the docs folder.
> > > compile_ptest_base will not fail, but actual tests will fail.
> >
> > This is where I start to say that we should be trimming the tests and only running useful tests for integration purposes, not the complete upstream test suite.
> 
> Sure, and as confirmed over irc I will send a followup patch removing that test.
> 
> -- 
> Regards
> Sudip

Note that test_sshd.test is failing, full log here:
https://autobuilder.yocto.io/pub/non-release/20230614-11/testresults/qemux86-64-ptest/core-image-ptest-libssh2/log.do_testimage.50695.20230614084246

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2023-06-14 22:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 20:52 [PATCH v2] libssh2: Upgrade to v1.11.0 Sudip Mukherjee
2023-06-14 13:52 ` [OE-core] " Ross Burton
2023-06-14 15:13   ` Sudip Mukherjee
2023-06-14 15:47     ` Ross Burton
2023-06-14 20:29       ` Sudip Mukherjee
2023-06-14 22:38         ` Alexandre Belloni [this message]
2023-06-16 20:33           ` Sudip Mukherjee

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=20230614223806a87d7d51@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=Ross.Burton@arm.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sudipm.mukherjee@gmail.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