Periodic stable branch testing

Kevin Traynor ktraynor at redhat.com
Fri Jan 14 11:43:32 CET 2022


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



More information about the ci mailing list