From: Ross Burton <Ross.Burton@arm.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [OE-core] [PATCH v2] libssh2: Upgrade to v1.11.0
Date: Wed, 14 Jun 2023 15:47:20 +0000 [thread overview]
Message-ID: <ADAC057F-4754-4451-B00A-FB1090212A72@arm.com> (raw)
In-Reply-To: <CADVatmN=x=5VAUZUU1if+SrX19dg7h-pBiD-B7u1PrX7wHOnBg@mail.gmail.com>
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
>>> PACKAGECONFIG ??= "openssl"
>>> @@ -41,9 +42,13 @@ do_install_ptest() {
>>> install -d ${D}${PTEST_PATH}/tests
>>> install -m 0755 ${S}/test-driver ${D}${PTEST_PATH}/
>>> cp -rf ${B}/tests/.libs/* ${D}${PTEST_PATH}/tests/
>>> - cp -rf ${S}/tests/mansyntax.sh ${D}${PTEST_PATH}/tests/
>>> - cp -rf ${S}/tests/ssh2.sh ${D}${PTEST_PATH}/tests/
>>> - cp -rf ${S}/tests/etc ${D}${PTEST_PATH}/tests/
>>> + cp -rf ${B}/tests/test_simple ${D}${PTEST_PATH}/tests/
>>> + cp -rf ${S}/tests/mansyntax.sh ${D}${PTEST_PATH}/tests/
>>> + cp -rf ${S}/tests/test_sshd.test ${D}${PTEST_PATH}/tests/
>>> + cp -rf ${S}/tests/openssh_server ${D}${PTEST_PATH}/tests/
>>> + cp -rf ${S}/tests/key* ${D}${PTEST_PATH}/tests/
>>> +# Makefile.inc required as test_sshd.test generates the list of test from this
>>> + cp -rf ${S}/tests/Makefile.inc ${D}${PTEST_PATH}/tests/
>>> 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.
Ross
next prev parent reply other threads:[~2023-06-14 15:47 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 [this message]
2023-06-14 20:29 ` Sudip Mukherjee
2023-06-14 22:38 ` Alexandre Belloni
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=ADAC057F-4754-4451-B00A-FB1090212A72@arm.com \
--to=ross.burton@arm.com \
--cc=alexandre.belloni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.