From: Owen Hilyard <ohilyard@iol.unh.edu>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: ci@dpdk.org, Luca Boccassi <bluca@debian.org>,
"Xueming(Steven) Li" <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Lincoln Lavoie <lylavoie@iol.unh.edu>,
Aaron Conole <aconole@redhat.com>
Subject: Re: Periodic stable branch testing
Date: Wed, 12 Jan 2022 13:36:55 -0500 [thread overview]
Message-ID: <CAHx6DYCR7PbXxf8fhpd5XshbZPrUThSWoKaPGZq12twWwYtyow@mail.gmail.com> (raw)
In-Reply-To: <849d066d-7308-994d-4d04-52aeed222c12@redhat.com>
Hello Kevin,
19.11 was not being tested due to issues with DTS. 20.11 appears to have
stopped running testing due to a failed job not releasing .git/index.lock.
This seems to have caused a timeout in a place where our automated alerts
had not been initalized, so they were never sent. You should see 20.11
nightly builds going forward.
Owen Hilyard
On Wed, Jan 12, 2022 at 1:16 PM Kevin Traynor <ktraynor@redhat.com> wrote:
> Hello LTS maintainers and Lincoln,
>
> Lincoln let me know that UNH can do periodic testing on stable branches.
>
> When I looked at the public dashboard [0] i'm confused with what is
> running as there doesn't seem to have been runs for a long time and
> there are many failures.
>
> So I'm wondering if/how they are being used by LTS maintainers and what
> exactly they are testing?
>
> thanks,
> Kevin.
>
> [0]
> 20.11 :
>
> https://dpdkdashboard.iol.unh.edu/results/dashboard/periodic_testing/?branch_id=13&page=0
>
> 19.11 :
>
> https://dpdkdashboard.iol.unh.edu/results/dashboard/periodic_testing/?branch_id=14&page=0
>
>
next prev parent reply other threads:[~2022-01-12 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 18:15 Kevin Traynor
2022-01-12 18:36 ` Owen Hilyard [this message]
2022-01-14 10:43 ` Kevin Traynor
2022-01-21 13:46 ` Kevin Traynor
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=CAHx6DYCR7PbXxf8fhpd5XshbZPrUThSWoKaPGZq12twWwYtyow@mail.gmail.com \
--to=ohilyard@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=ci@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=lylavoie@iol.unh.edu \
--cc=xuemingl@nvidia.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).