DPDK CI discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Owen Hilyard <ohilyard@iol.unh.edu>
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>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: Periodic stable branch testing
Date: Fri, 21 Jan 2022 13:46:25 +0000
Message-ID: <fd1bdf3c-ec7a-7b84-bb9f-0ab0f3450649@redhat.com> (raw)
In-Reply-To: <c4998c59-6581-65ce-554f-615bb3b5637a@redhat.com>

On 14/01/2022 10:43, Kevin Traynor wrote:
> Hi Owen,
> 
> On 12/01/2022 18:36, Owen Hilyard wrote:
>> 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.
>>
> 
> Thanks for the update and for enabling 21.11. I see there is a nightly
> build now for 20.11/21.11.
> 

Is there an option for the LTS maintainers to request a run?

Periodic builds are very good but coming to release, it would be great 
for LTS maintainer to be also able to kick-off a build on a branch for a 
re-test, or check immediately for some patches just applied.

I suspect this would be handy for other branch maintainers too outside 
of LTS.

It would be just one or two maintainers per branch, so could be handled 
by having us login etc. It wouldn't need need parsing of patches as i've 
seen suggested for patch re-testing.

thanks,
Kevin.

> fyi - noticed brcm scatter test newly failing [0] last night with no
> changes to 21.11. Will keep an eye on it to see if it was just an
> isolated failure.
> 
> thanks,
> Kevin.
> 
> [0] https://dpdkdashboard.iol.unh.edu/results/dashboard/tarballs/18272/
> 
>> 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
>>>
>>>
>>
> 


      reply	other threads:[~2022-01-21 13:46 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
2022-01-14 10:43   ` Kevin Traynor
2022-01-21 13:46     ` Kevin Traynor [this message]

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=fd1bdf3c-ec7a-7b84-bb9f-0ab0f3450649@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=aconole@redhat.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=ferruh.yigit@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=ohilyard@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --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

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git