Periodic stable branch testing

Periodic stable branch testing

[Kevin Traynor]

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

Re: Periodic stable branch testing

[Owen Hilyard]

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
>
>

Re: Periodic stable branch testing

[Kevin Traynor]

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.

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
>>
>>
> 

Re: Periodic stable branch testing

[Kevin Traynor]

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
>>>
>>>
>>
>