From: Adam Hassick <ahassick@iol.unh.edu>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: Konstantin Ushakov <Konstantin.Ushakov@oktetlabs.ru>,
Patrick Robb <probb@iol.unh.edu>,
ci@dpdk.org
Subject: Re: Setting up DPDK PMD Test Suite
Date: Tue, 7 Nov 2023 15:30:20 -0500 [thread overview]
Message-ID: <CAC-YWqhdzAbO+45GdE61DWTroHOqPCH_R0ZphHZaYnatMAf_+g@mail.gmail.com> (raw)
In-Reply-To: <8e26b8e6-8d8b-4925-9b30-3fbc5e103e18@oktetlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]
Hi Andrew,
The runner machine was missing a dependency for one of the scripts, "pixz".
After installing that, it appears to have worked. I can see the results
listed on the ts-factory Bublik instance.
In the latest revision of ts-rigs, there appears to be a syntax error at
line 42 within the script located at
"ts-rigs/scripts/publish_logs/prj/ts-factory/publish", within the if
condition. I fixed it locally to get it to run.
Taking a quick look at a comparison against your most recent X710 run, it
looks like we're NOK on around ~400 more test cases. By percentage of
tests, we're 1% off, however, it looks like whole subsets of the test suite
that contain low numbers of tests are failing. I wonder if this is due to
differences between the Intel X710 and XL710 or issues in our dev testbed.
Thanks,
Adam
On Tue, Nov 7, 2023 at 11:58 AM Andrew Rybchenko <
andrew.rybchenko@oktetlabs.ru> wrote:
> Hi Adam,
>
> I see no attempt to publish logs, so I guess something went wrong. Please,
> let me know if you need any help from me. Hopefully there is no need to
> rerun tests and publish could be debugged using ./scripts/publish_logs.
>
> Andrew.
>
> On 11/7/23 02:16, Adam Hassick wrote:
>
> Hi Andrew,
>
> I've started a test run, it should finish at some point overnight. I
> tested the authentication and it seems to work, fingers crossed that we see
> some results appear tomorrow.
>
> Thanks,
> Adam
>
> On Fri, Oct 27, 2023 at 3:13 PM Andrew Rybchenko <
> andrew.rybchenko@oktetlabs.ru> wrote:
>
>> Hi Adam,
>>
>> fresh ts-rigs-sample has all required bindings to publish logs to
>> ts-factory.io. See the top-most commit.
>> So, you just need tune SSH to use correct user, port and key for
>> ts-factory.io. You can add below settings
>> to corresponding user .ssh/config or add corresponding options to sftp
>> command in scripts/publish_logs/prj/ts-factory/publish:
>>
>> Host ts-factory.io
>> User unh-iol
>> Port 56777
>> IdentitiesOnly yes
>> IdentityFile <path-to-private-key>
>>
>> The publishing is asynchronous in ts-factory case. i.e. user puts logs
>> and cron job checks incoming directory every 10 minutes and publish found
>> logs.
>>
>> You can request publishing when you start testing using --publish option
>> or publish previous run testing results using ./scripts/publish_logs from
>> dpdk-ethdev-ts sources. PWD should be the directory you run tests from.
>>
>> Please, let me know how it goes.
>>
>> Regards,
>> Andrew.
>>
>> (dropped history, since it became too big and require moderation)
>>
>
>
[-- Attachment #2: Type: text/html, Size: 4553 bytes --]
next prev parent reply other threads:[~2023-11-07 20:28 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAC-YWqiQfH4Rx-Et1jGHhGK9i47d0AArKy-B2P77iYbbM+Lpig@mail.gmail.com>
[not found] ` <C3B08390-DA6D-4BDC-BBD7-98561F92FE33@oktetlabs.ru>
[not found] ` <35340484-1d7e-7e5f-cad4-c965ba541397@oktetlabs.ru>
2023-08-17 17:03 ` Adam Hassick
2023-08-18 18:40 ` Andrew Rybchenko
2023-08-20 8:40 ` Andrew Rybchenko
2023-08-21 14:19 ` Adam Hassick
2023-08-23 14:45 ` Adam Hassick
2023-08-24 8:22 ` Andrew Rybchenko
2023-08-24 14:30 ` Adam Hassick
2023-08-24 18:34 ` Andrew Rybchenko
2023-08-24 20:29 ` Adam Hassick
2023-08-24 20:54 ` Andrew Rybchenko
2023-08-25 13:57 ` Andrew Rybchenko
2023-08-25 14:06 ` Adam Hassick
2023-08-25 14:41 ` Andrew Rybchenko
2023-08-25 17:35 ` Andrew Rybchenko
2023-08-28 15:02 ` Adam Hassick
2023-08-28 21:05 ` Andrew Rybchenko
2023-08-29 12:07 ` Andrew Rybchenko
2023-08-29 14:02 ` Adam Hassick
2023-08-29 20:43 ` Andrew Rybchenko
2023-08-31 19:38 ` Adam Hassick
2023-09-01 7:59 ` Andrew Rybchenko
2023-09-05 15:01 ` Adam Hassick
2023-09-06 11:36 ` Andrew Rybchenko
2023-09-06 15:00 ` Adam Hassick
2023-09-08 14:57 ` Adam Hassick
2023-09-13 15:45 ` Andrew Rybchenko
2023-09-18 6:15 ` Andrew Rybchenko
2023-09-18 6:23 ` Konstantin Ushakov
2023-09-18 6:26 ` Andrew Rybchenko
2023-09-18 14:44 ` Adam Hassick
2023-09-18 15:04 ` Andrew Rybchenko
2023-10-04 13:48 ` Adam Hassick
2023-10-05 10:25 ` Andrew Rybchenko
2023-10-10 14:09 ` Adam Hassick
2023-10-11 11:46 ` Andrew Rybchenko
2023-10-23 11:11 ` Andrew Rybchenko
2023-10-25 20:27 ` Adam Hassick
2023-10-26 12:19 ` Andrew Rybchenko
2023-10-26 17:44 ` Adam Hassick
2023-10-27 8:01 ` Andrew Rybchenko
2023-10-27 19:13 ` Andrew Rybchenko
2023-11-06 23:16 ` Adam Hassick
2023-11-07 16:57 ` Andrew Rybchenko
2023-11-07 20:30 ` Adam Hassick [this message]
2023-11-08 7:20 ` Andrew Rybchenko
2023-11-16 20:03 ` Adam Hassick
2023-11-16 20:38 ` DPDK Coverity test run Mcnamara, John
2023-11-16 20:43 ` Patrick Robb
2023-11-16 20:56 ` Mcnamara, John
2023-11-20 17:18 ` Setting up DPDK PMD Test Suite Andrew Rybchenko
2023-12-01 14:39 ` Andrew Rybchenko
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=CAC-YWqhdzAbO+45GdE61DWTroHOqPCH_R0ZphHZaYnatMAf_+g@mail.gmail.com \
--to=ahassick@iol.unh.edu \
--cc=Konstantin.Ushakov@oktetlabs.ru \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=ci@dpdk.org \
--cc=probb@iol.unh.edu \
/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;
as well as URLs for NNTP newsgroup(s).