From: David Marchand <david.marchand@redhat.com>
To: Joshua Washington <joshwash@google.com>
Cc: Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>,
dev@dpdk.org, Rushil Gupta <rushilg@google.com>,
dpdklab <dpdklab@iol.unh.edu>
Subject: Re: [PATCH v5] app/testpmd: txonly multiflow port change support
Date: Tue, 25 Apr 2023 08:56:15 +0200 [thread overview]
Message-ID: <CAJFAV8wgUCBU6-mCtFvnFKU2N2iydNkWXOc0-NJ1wN=NU685fw@mail.gmail.com> (raw)
In-Reply-To: <CALuQH+XHRVpGqYWYjmDA1nHEpu2Hti1uD5=Q1RbZOoSfTr5_9Q@mail.gmail.com>
Hello Joshua,
On Mon, Apr 24, 2023 at 7:56 PM Joshua Washington <joshwash@google.com> wrote:
>
> After updating the patch, it seems that the `lcores_autotest` unit test now times out on Windows Server 2019. I looked at the test logs, but they were identical as far as I could tell, with the timed out test even printing "Test OK" to stdout. Is this a flake? Or is there any other way to get extra information about why the test timed out or run the test with extra debugging information?
In general, the UNH dashboard provides an archive with logs for each
report, like for example:
https://lab.dpdk.org/results/dashboard/patchsets/26090/
https://lab.dpdk.org/results/dashboard/results/results-uploads/test_runs/b5a6a2743665426b937603587850aa6d/log_upload_file/2023/4/dpdk_5f34cc454df4_26090_2023-04-22_02-36-52_NA.zip
This timeout is something I did not notice so far, Ccing UNH guys, for info.
Regarding your patch, the CI passes fine on the current main branch.
And there is no relation between testpmd and the EAL unit tests.
So this report is very likely a false positive.
I triggered a retest on your patch.
--
David Marchand
next prev parent reply other threads:[~2023-04-25 6:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 20:17 [PATCH v2] " Joshua Washington
2023-04-11 20:24 ` [PATCH v3] " Joshua Washington
2023-04-12 18:16 ` [PATCH v4] " Joshua Washington
2023-04-19 12:21 ` Singh, Aman Deep
2023-04-19 14:38 ` Stephen Hemminger
2023-04-21 23:20 ` [PATCH v5] " Joshua Washington
2023-04-24 17:55 ` Joshua Washington
2023-04-25 6:56 ` David Marchand [this message]
2023-04-26 7:24 ` Singh, Aman Deep
2023-05-15 18:11 ` Joshua Washington
2023-05-15 22:26 ` Ferruh Yigit
2023-05-16 17:32 ` Joshua Washington
2023-05-17 10:10 ` Ferruh Yigit
2023-05-17 10:34 ` Ferruh Yigit
2023-05-19 0:22 ` [PATCH v6] " Joshua Washington
2023-05-19 11:23 ` Ferruh Yigit
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='CAJFAV8wgUCBU6-mCtFvnFKU2N2iydNkWXOc0-NJ1wN=NU685fw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=joshwash@google.com \
--cc=rushilg@google.com \
--cc=yuying.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).