Date   

Re: YP Autobuilder/SwatBoart Enhancement

Alexandre Belloni
 

On 01/10/2021 12:52:46+0000, Naveen Saini wrote:
Ahh..right !! Thanks.

But still I think, in case of build cancellation, this provision can make debugging easier. If still this does not make much sense, I can close this bug.
I agree, this would meake it easier and I'm not dismissing the idea but
it is not simple to implement in the current architecture. Let's leave
it open and discuss on Thursday

Regards,
Naveen

-----Original Message-----
From: swat@lists.yoctoproject.org <swat@lists.yoctoproject.org> On Behalf
Of Alexandre Belloni
Sent: Friday, October 1, 2021 6:46 PM
To: swat@lists.yoctoproject.org
Subject: Re: [swat] YP Autobuilder/SwatBoart Enhancement

Hello,

On 01/10/2021 09:02:07+0000, Naveen Saini wrote:
Hi Team,

I created a bug#14584 to enhance Autobuilder/SwatBoat process.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14584

Description:
Currently when user cancel a build, there is no provision to enter reason,
why it was cancelled. If there is no need to triage such cancelled builds then
allow to enable 'Not for SWAT'

Sometime it becomes difficult to analyse the build failures, when mater-
next branch is force rebased (drop conflict patch). In that case, there is no
way to know which commits were included in cancelled builds.
I explained on
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team how to
get that:

$ git clone git://git.yoctoproject.org/poky $ cd poky $ git fetch origin
47482eff9897ccde946e9247724babc3a586d318
$ git log FETCH_HEAD

This should work unless the git garbage collector ran.


--
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel
engineering https://bootlin.com







--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


Re: YP Autobuilder/SwatBoart Enhancement

Naveen Saini
 

Ahh..right !! Thanks.

But still I think, in case of build cancellation, this provision can make debugging easier. If still this does not make much sense, I can close this bug.

Regards,
Naveen

-----Original Message-----
From: swat@lists.yoctoproject.org <swat@lists.yoctoproject.org> On Behalf
Of Alexandre Belloni
Sent: Friday, October 1, 2021 6:46 PM
To: swat@lists.yoctoproject.org
Subject: Re: [swat] YP Autobuilder/SwatBoart Enhancement

Hello,

On 01/10/2021 09:02:07+0000, Naveen Saini wrote:
Hi Team,

I created a bug#14584 to enhance Autobuilder/SwatBoat process.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14584

Description:
Currently when user cancel a build, there is no provision to enter reason,
why it was cancelled. If there is no need to triage such cancelled builds then
allow to enable 'Not for SWAT'

Sometime it becomes difficult to analyse the build failures, when mater-
next branch is force rebased (drop conflict patch). In that case, there is no
way to know which commits were included in cancelled builds.
I explained on
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team how to
get that:

$ git clone git://git.yoctoproject.org/poky $ cd poky $ git fetch origin
47482eff9897ccde946e9247724babc3a586d318
$ git log FETCH_HEAD

This should work unless the git garbage collector ran.


--
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel
engineering https://bootlin.com




Re: YP Autobuilder/SwatBoart Enhancement

Alexandre Belloni
 

Hello,

On 01/10/2021 09:02:07+0000, Naveen Saini wrote:
Hi Team,

I created a bug#14584 to enhance Autobuilder/SwatBoat process.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14584

Description:
Currently when user cancel a build, there is no provision to enter reason, why it was cancelled. If there is no need to triage such cancelled builds then allow to enable 'Not for SWAT'

Sometime it becomes difficult to analyse the build failures, when mater-next branch is force rebased (drop conflict patch). In that case, there is no way to know which commits were included in cancelled builds.
I explained on
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team how to
get that:

$ git clone git://git.yoctoproject.org/poky
$ cd poky
$ git fetch origin 47482eff9897ccde946e9247724babc3a586d318
$ git log FETCH_HEAD

This should work unless the git garbage collector ran.


--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


YP Autobuilder/SwatBoart Enhancement

Naveen Saini
 

Hi Team,

 

I created a bug#14584 to enhance Autobuilder/SwatBoat process.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=14584

 

Description:

Currently when user cancel a build, there is no provision to enter reason, why it was cancelled. If there is no need to triage such cancelled builds then allow to enable 'Not for SWAT'

 

Sometime it becomes difficult to analyse the build failures, when mater-next branch is force rebased (drop conflict patch). In that case, there is no way to know which commits were included in cancelled builds.

 

Regards,

Naveen

 

 

 

 


The postinstall intercept hook failures on master-next

Naveen Saini
 

Hi Richard,

 

I can see a number of postinstall intercept hook failures on master-next on oe-selftest builds on all distros and reproducible builds.

 

Error log:

do_rootfs: The postinstall intercept hook 'update_pixbuf_cache' failed

 

do_rootfs: The postinstall intercept hook 'update_font_cache' failed

 

do_rootfs: The postinstall intercept hook 'update_gio_module_cache' failed

 

do_rootfs: The postinstall intercept hook 'update_udev_hwdb' failed

 

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2678

 

https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/2646

https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/2636

https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/2617

https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/2611

 

I already raised a bug for  'update_udev_hwdb'

https://bugzilla.yoctoproject.org/show_bug.cgi?id=14583

 

I can not see more logs to look deeper, should I raise bugs for all of them ?

 

Regards,

Naveen

 

 


Re: SWAT Rotation schedule

Naveen Saini
 

Acknowledged.

Regards,
Naveen

-----Original Message-----
From: swat@lists.yoctoproject.org <swat@lists.yoctoproject.org> On Behalf
Of Alexandre Belloni
Sent: Thursday, September 30, 2021 7:13 AM
To: Saini, Naveen Kumar <naveen.kumar.saini@intel.com>
Cc: swat@lists.yoctoproject.org
Subject: Re: [swat] SWAT Rotation schedule

Hello Naveen,

It is a quick reminder that you will be on SWAT duty starting Friday October
1st.

On 16/09/2021 23:29:50+0200, Alexandre Belloni wrote:
Hello,

Following the summer break, I would like to organize SWAT duty rotation.
This time, I've prepared a semi randomized schedule so it is easier
for each one of you to plan for SWAT duty.

Please check the table and let me know if you are not available for
the selected week. SWAT duty will be from Friday to Thursday and the
goal is to triage all the failures on swatbot before the weekly triage
call happening at 2:30pm UTC.

┌──────┬────────────┐
│ Week │ Start │
┌───────────────────────────────┼──────┼────────────┤
│ Alejandro Hernandez Samaniego │ 37 │ 17/09/2021 │
│ Oleksiy Obitotskyy │ 38 │ 24/09/2021 │
│ Naveen Saini │ 39 │ 01/10/2021 │
│ Thomas Perrot │ 40 │ 08/10/2021 │
│ Paul Eggleton │ 41 │ 15/10/2021 │
│ Christopher Larson │ 42 │ 22/10/2021 │
│ Jon Mason │ 43 │ 29/10/2021 │
│ Lee Chee Yang │ 44 │ 05/11/2021 │
│ Minjae Kim │ 45 │ 12/11/2021 │
│ Jaga │ 46 │ 19/11/2021 │
│ Leo Sandoval │ 47 │ 26/11/2021 │
│ Ross Burton │ 48 │ 03/12/2021 │
│ Köry Maincent │ 49 │ 10/12/2021 │
│ Anibal Limon │ 50 │ 17/12/2021 │
│ Saul Wold │ 51 │ 24/12/2021 │
└───────────────────────────────┴──────┴────────────┘

Alejandro you would be the next one on the list, starting this Friday,
can you confirm you are available?

There are currently 8 failures to triage on swatbot, I'm going to take
care of those.

Thanks!

--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com




--
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel
engineering https://bootlin.com




Re: SWAT Rotation schedule

Alexandre Belloni
 

Hello Naveen,

It is a quick reminder that you will be on SWAT duty starting Friday
October 1st.

On 16/09/2021 23:29:50+0200, Alexandre Belloni wrote:
Hello,

Following the summer break, I would like to organize SWAT duty rotation.
This time, I've prepared a semi randomized schedule so it is easier for
each one of you to plan for SWAT duty.

Please check the table and let me know if you are not available for the
selected week. SWAT duty will be from Friday to Thursday and the goal is
to triage all the failures on swatbot before the weekly triage call
happening at 2:30pm UTC.

┌──────┬────────────┐
│ Week │ Start │
┌───────────────────────────────┼──────┼────────────┤
│ Alejandro Hernandez Samaniego │ 37 │ 17/09/2021 │
│ Oleksiy Obitotskyy │ 38 │ 24/09/2021 │
│ Naveen Saini │ 39 │ 01/10/2021 │
│ Thomas Perrot │ 40 │ 08/10/2021 │
│ Paul Eggleton │ 41 │ 15/10/2021 │
│ Christopher Larson │ 42 │ 22/10/2021 │
│ Jon Mason │ 43 │ 29/10/2021 │
│ Lee Chee Yang │ 44 │ 05/11/2021 │
│ Minjae Kim │ 45 │ 12/11/2021 │
│ Jaga │ 46 │ 19/11/2021 │
│ Leo Sandoval │ 47 │ 26/11/2021 │
│ Ross Burton │ 48 │ 03/12/2021 │
│ Köry Maincent │ 49 │ 10/12/2021 │
│ Anibal Limon │ 50 │ 17/12/2021 │
│ Saul Wold │ 51 │ 24/12/2021 │
└───────────────────────────────┴──────┴────────────┘

Alejandro you would be the next one on the list, starting this Friday,
can you confirm you are available?

There are currently 8 failures to triage on swatbot, I'm going to take
care of those.

Thanks!

--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com




--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


Re: SWAT Rotation schedule

Alexandre Belloni
 

On 23/09/2021 05:15:06+0000, Oleksiy Obitotskyy via lists.yoctoproject.org wrote:
Hi,

I will start as planned from 24/09/2021.
Thanks, there are currently 7 failures that are not triaged. The two
reproducible issues may already be fixed and we'll know that once the
nightly builds have finished.

Unfortunately, the logs for the qemuarm64 failure are already gone are
there is already a (failing) qemuarm64 build running on the same worker.
The four other ones are one off issues that didn't repeat, I'll discuss
with Richard what to do with them.

Regards,

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


Re: SWAT Rotation schedule

Oleksiy Obitotskyy
 

Hi,

I will start as planned from 24/09/2021.

Regards,
Oleksiy

________________________________________
From: swat@lists.yoctoproject.org <swat@lists.yoctoproject.org> on behalf of Alexandre Belloni <alexandre.belloni@bootlin.com>
Sent: Friday, September 17, 2021 00:29
To: Alejandro Hernandez Samaniego; swat@lists.yoctoproject.org
Subject: [swat] SWAT Rotation schedule

Hello,

Following the summer break, I would like to organize SWAT duty rotation.
This time, I've prepared a semi randomized schedule so it is easier for
each one of you to plan for SWAT duty.

Please check the table and let me know if you are not available for the
selected week. SWAT duty will be from Friday to Thursday and the goal is
to triage all the failures on swatbot before the weekly triage call
happening at 2:30pm UTC.

┌──────┬────────────┐
│ Week │ Start │
┌───────────────────────────────┼──────┼────────────┤
│ Alejandro Hernandez Samaniego │ 37 │ 17/09/2021 │
│ Oleksiy Obitotskyy │ 38 │ 24/09/2021 │
│ Naveen Saini │ 39 │ 01/10/2021 │
│ Thomas Perrot │ 40 │ 08/10/2021 │
│ Paul Eggleton │ 41 │ 15/10/2021 │
│ Christopher Larson │ 42 │ 22/10/2021 │
│ Jon Mason │ 43 │ 29/10/2021 │
│ Lee Chee Yang │ 44 │ 05/11/2021 │
│ Minjae Kim │ 45 │ 12/11/2021 │
│ Jaga │ 46 │ 19/11/2021 │
│ Leo Sandoval │ 47 │ 26/11/2021 │
│ Ross Burton │ 48 │ 03/12/2021 │
│ Köry Maincent │ 49 │ 10/12/2021 │
│ Anibal Limon │ 50 │ 17/12/2021 │
│ Saul Wold │ 51 │ 24/12/2021 │
└───────────────────────────────┴──────┴────────────┘

Alejandro you would be the next one on the list, starting this Friday,
can you confirm you are available?

There are currently 8 failures to triage on swatbot, I'm going to take
care of those.

Thanks!

--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


Re: [EXTERNAL] [swat] SWAT Rotation schedule

Alejandro Hernandez Samaniego
 

Hello Alex,

Sadly I'm not available this week, I apologize for the late reply but I've been out, can you reschedule me for a different week?

Alejandro


From: swat@... <swat@...> on behalf of Alexandre Belloni via lists.yoctoproject.org <alexandre.belloni=bootlin.com@...>
Sent: Thursday, 16 September 2021, 5:16 pm
To: Alejandro Hernandez Samaniego; swat@...
Subject: [EXTERNAL] [swat] SWAT Rotation schedule

Hello,

Following the summer break, I would like to organize SWAT duty rotation.
This time, I've prepared a semi randomized schedule so it is easier for
each one of you to plan for SWAT duty.

Please check the table and let me know if you are not available for the
selected week. SWAT duty will be from Friday to Thursday and the goal is
to triage all the failures on swatbot before the weekly triage call
happening at 2:30pm UTC.

                                ┌──────┬────────────┐
                                │ Week │   Start    │
┌───────────────────────────────┼──────┼────────────┤
│ Alejandro Hernandez Samaniego │   37 │ 17/09/2021 │
│ Oleksiy Obitotskyy            │   38 │ 24/09/2021 │
│ Naveen Saini                  │   39 │ 01/10/2021 │
│ Thomas Perrot                 │   40 │ 08/10/2021 │
│ Paul Eggleton                 │   41 │ 15/10/2021 │
│ Christopher Larson            │   42 │ 22/10/2021 │
│ Jon Mason                     │   43 │ 29/10/2021 │
│ Lee Chee Yang                 │   44 │ 05/11/2021 │
│ Minjae Kim                    │   45 │ 12/11/2021 │
│ Jaga                          │   46 │ 19/11/2021 │
│ Leo Sandoval                  │   47 │ 26/11/2021 │
│ Ross Burton                   │   48 │ 03/12/2021 │
│ Köry Maincent                 │   49 │ 10/12/2021 │
│ Anibal Limon                  │   50 │ 17/12/2021 │
│ Saul Wold                     │   51 │ 24/12/2021 │
└───────────────────────────────┴──────┴────────────┘

Alejandro you would be the next one on the list, starting this Friday,
can you confirm you are available?

There are currently 8 failures to triage on swatbot, I'm going to take
care of those.

Thanks!

--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbootlin.com%2F&amp;data=04%7C01%7CAlejandro.Hernandez%40microsoft.com%7C5d12ddae8d8a43bf0e2208d9796806ed%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637674309971395320%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=QTq%2FDzzYKP0TblZjXG4q3i1x2DRXUY6JwkHJGmjkylU%3D&amp;reserved=0







Re: SWAT Rotation schedule

Alexandre Belloni
 

On 17/09/2021 08:55:10-0700, Saul Wold wrote:


On 9/16/21 2:29 PM, Alexandre Belloni wrote:
Hello,

Following the summer break, I would like to organize SWAT duty rotation.
This time, I've prepared a semi randomized schedule so it is easier for
each one of you to plan for SWAT duty.

Please check the table and let me know if you are not available for the
selected week. SWAT duty will be from Friday to Thursday and the goal is
to triage all the failures on swatbot before the weekly triage call
happening at 2:30pm UTC.
Hi Alexandre,

Great work on creating a schedule that might be more predictable! Just a
heads up, the date you have me is right over the Christmas break. I am not
saying drop me as I might be working anyway, but when things get closer I
will let you know if I have other plans (going skiing!).
Sure, I realize that and I was thinking probably there will be less
builds at that time anyway!

Sau!

┌──────┬────────────┐
│ Week │ Start │
┌───────────────────────────────┼──────┼────────────┤
│ Alejandro Hernandez Samaniego │ 37 │ 17/09/2021 │
│ Oleksiy Obitotskyy │ 38 │ 24/09/2021 │
│ Naveen Saini │ 39 │ 01/10/2021 │
│ Thomas Perrot │ 40 │ 08/10/2021 │
│ Paul Eggleton │ 41 │ 15/10/2021 │
│ Christopher Larson │ 42 │ 22/10/2021 │
│ Jon Mason │ 43 │ 29/10/2021 │
│ Lee Chee Yang │ 44 │ 05/11/2021 │
│ Minjae Kim │ 45 │ 12/11/2021 │
│ Jaga │ 46 │ 19/11/2021 │
│ Leo Sandoval │ 47 │ 26/11/2021 │
│ Ross Burton │ 48 │ 03/12/2021 │
│ Köry Maincent │ 49 │ 10/12/2021 │
│ Anibal Limon │ 50 │ 17/12/2021 │
│ Saul Wold │ 51 │ 24/12/2021 │
└───────────────────────────────┴──────┴────────────┘

Alejandro you would be the next one on the list, starting this Friday,
can you confirm you are available?

There are currently 8 failures to triage on swatbot, I'm going to take
care of those.

Thanks!
--
Sau!




--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


Re: SWAT Rotation schedule

Saul Wold
 

On 9/16/21 2:29 PM, Alexandre Belloni wrote:
Hello,
Following the summer break, I would like to organize SWAT duty rotation.
This time, I've prepared a semi randomized schedule so it is easier for
each one of you to plan for SWAT duty.
Please check the table and let me know if you are not available for the
selected week. SWAT duty will be from Friday to Thursday and the goal is
to triage all the failures on swatbot before the weekly triage call
happening at 2:30pm UTC.
Hi Alexandre,

Great work on creating a schedule that might be more predictable! Just a heads up, the date you have me is right over the Christmas break. I am not saying drop me as I might be working anyway, but when things get closer I will let you know if I have other plans (going skiing!).

Sau!

┌──────┬────────────┐
│ Week │ Start │
┌───────────────────────────────┼──────┼────────────┤
│ Alejandro Hernandez Samaniego │ 37 │ 17/09/2021 │
│ Oleksiy Obitotskyy │ 38 │ 24/09/2021 │
│ Naveen Saini │ 39 │ 01/10/2021 │
│ Thomas Perrot │ 40 │ 08/10/2021 │
│ Paul Eggleton │ 41 │ 15/10/2021 │
│ Christopher Larson │ 42 │ 22/10/2021 │
│ Jon Mason │ 43 │ 29/10/2021 │
│ Lee Chee Yang │ 44 │ 05/11/2021 │
│ Minjae Kim │ 45 │ 12/11/2021 │
│ Jaga │ 46 │ 19/11/2021 │
│ Leo Sandoval │ 47 │ 26/11/2021 │
│ Ross Burton │ 48 │ 03/12/2021 │
│ Köry Maincent │ 49 │ 10/12/2021 │
│ Anibal Limon │ 50 │ 17/12/2021 │
│ Saul Wold │ 51 │ 24/12/2021 │
└───────────────────────────────┴──────┴────────────┘
Alejandro you would be the next one on the list, starting this Friday,
can you confirm you are available?
There are currently 8 failures to triage on swatbot, I'm going to take
care of those.
Thanks!
--
Sau!


SWAT Rotation schedule

Alexandre Belloni
 

Hello,

Following the summer break, I would like to organize SWAT duty rotation.
This time, I've prepared a semi randomized schedule so it is easier for
each one of you to plan for SWAT duty.

Please check the table and let me know if you are not available for the
selected week. SWAT duty will be from Friday to Thursday and the goal is
to triage all the failures on swatbot before the weekly triage call
happening at 2:30pm UTC.

┌──────┬────────────┐
│ Week │ Start │
┌───────────────────────────────┼──────┼────────────┤
│ Alejandro Hernandez Samaniego │ 37 │ 17/09/2021 │
│ Oleksiy Obitotskyy │ 38 │ 24/09/2021 │
│ Naveen Saini │ 39 │ 01/10/2021 │
│ Thomas Perrot │ 40 │ 08/10/2021 │
│ Paul Eggleton │ 41 │ 15/10/2021 │
│ Christopher Larson │ 42 │ 22/10/2021 │
│ Jon Mason │ 43 │ 29/10/2021 │
│ Lee Chee Yang │ 44 │ 05/11/2021 │
│ Minjae Kim │ 45 │ 12/11/2021 │
│ Jaga │ 46 │ 19/11/2021 │
│ Leo Sandoval │ 47 │ 26/11/2021 │
│ Ross Burton │ 48 │ 03/12/2021 │
│ Köry Maincent │ 49 │ 10/12/2021 │
│ Anibal Limon │ 50 │ 17/12/2021 │
│ Saul Wold │ 51 │ 24/12/2021 │
└───────────────────────────────┴──────┴────────────┘

Alejandro you would be the next one on the list, starting this Friday,
can you confirm you are available?

There are currently 8 failures to triage on swatbot, I'm going to take
care of those.

Thanks!

--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


Re: SWAT Rotation

Saul Wold
 

On 8/30/21 1:26 AM, Alexandre Belloni wrote:
Hello Saul,
As we discussed las Thursday, I count on you to take care of SWAT this
week.
ACK

I'll take care of 211545 and earlier when I'll be back so you don't
necessarily have to spend time on those.
I will look at the newer ones later this morning.

Sau!

Thanks!
--
Sau!


SWAT Rotation

Alexandre Belloni
 

Hello Saul,

As we discussed las Thursday, I count on you to take care of SWAT this
week.
I'll take care of 211545 and earlier when I'll be back so you don't
necessarily have to spend time on those.

Thanks!

--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


[swatbot] [PATCH] models/serializers: triage exception automatically

Alexandre Belloni
 

Most of the cancelled builds are actually exceptions, tirage them
automatically.

Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
---
swatapp/serializers.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/swatapp/serializers.py b/swatapp/serializers.py
index cba4fa482079..e5ca25e4442f 100644
--- a/swatapp/serializers.py
+++ b/swatapp/serializers.py
@@ -28,7 +28,7 @@ class StepFailureSerializer(serializers.ModelSerializer):
attrs['triage'] = TriageStatus.NOTFORSWAT

# Cancelled builds with only stdio (no errors/warnings) aren't interesting
- if attrs['status'] == Status.CANCELLED:
+ if attrs['status'] == Status.CANCELLED or attrs['status'] == Status.EXCEPTION:
if "/errors" not in attrs['urls'] and "/warnings" not in attrs['urls']:
attrs['triage'] = TriageStatus.CANCELLEDNOERR
return attrs
--
2.31.1


Re: SWAT Rotation

Anibal Limon
 

Hi Alexandre,

Unfortunately I will be out next two weeks for summer vacation. 

Sorry for the inconvenience.

Best regards!,
Anibal

On Fri, 13 Aug 2021 at 09:14, Alexandre Belloni <alexandre.belloni@...> wrote:
Hello Anibal,

You are the next one on the SWAT Team members list
(https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team#Members)

Are you available next week for SWAT duty?

Thanks!

--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


SWAT Rotation

Alexandre Belloni
 

Hello Anibal,

You are the next one on the SWAT Team members list
(https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team#Members)

Are you available next week for SWAT duty?

Thanks!

--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


Re: glibc 2.34 tests

Randy MacLeod
 

Add  Tony who has been working on valgrind so he and Khem keep in sync.

../Randy

On 2021-07-06 5:01 a.m., Khem Raj wrote:
On Sat, Jul 3, 2021 at 2:29 PM Alexandre Belloni
<alexandre.belloni@bootlin.com> wrote:
Hello,

I've been testing multiple versions of Khem's branch for glibc2.34
Everything apart from non-gpl3 builds fine. There is a patch from Khem
to solve this issue, I didn't apply/test yet:

[yocto] [meta-gplv2] [PATCH] coreutils_6.9.bb: Fix build with glibc 2.34

On the tests side, systemd-journal was crashing, the last patch on
Khem's branch is solving the issue, thanks!

The remaining issues are on the ptests side:

https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2233/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1946/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2236/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1949/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2244/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1957/steps/12/logs/stdio

Issues happen both on qemux86-64 and qemuarm64 and they reproduced
every time:

'elfutils': ['run-backtrace-native.sh', 'run-backtrace-native-core.sh']

'strace': ['prlimit64.gen.test',
'xet_robust_list.gen.test',
'xet_robust_list--pidns-translation.gen.test'],

For valgrind, it is all over the place:

ARM has:
'valgrind': ['gdbserver_tests/hginfo',
'helgrind/tests/hg02_deadlock',
'drd/tests/boost_thread',
'drd/tests/pth_cond_race3',
'drd/tests/pth_create_chain',
'drd/tests/pth_detached',
'drd/tests/std_list',
'drd/tests/std_mutex',
'drd/tests/swapcontext',
'drd/tests/tc24_nonzero_sem',
'drd/tests/thread_name',
'drd/tests/thread_name_xml',
'drd/tests/threaded-fork-vcs',
'drd/tests/threaded-fork',
'drd/tests/tls_threads',
'massif/tests/deep-D']

x86 has:

'valgrind': ['gdbserver_tests/hginfo',
'memcheck/tests/supp_unknown',
'helgrind/tests/annotate_smart_pointer',
'helgrind/tests/bar_bad',
'helgrind/tests/hg01_all_ok',
'helgrind/tests/hg02_deadlock',
'helgrind/tests/pth_destroy_cond',
'helgrind/tests/rwlock_test',
'helgrind/tests/tc05_simple_race',
'helgrind/tests/tc06_two_races',
'helgrind/tests/tc06_two_races_xml',
'helgrind/tests/tc14_laog_dinphils',
'helgrind/tests/tc17_sembar',
'helgrind/tests/tc19_shadowmem',
'helgrind/tests/tc21_pthonce',
'helgrind/tests/tc22_exit_w_lock',
'helgrind/tests/tc23_bogus_condwait',
'helgrind/tests/tls_threads',
'drd/tests/annotate_barrier',
'drd/tests/annotate_barrier_xml',
'drd/tests/annotate_hb_race',
'drd/tests/annotate_hbefore',
'drd/tests/annotate_ignore_read',
'drd/tests/annotate_ignore_rw',
'drd/tests/annotate_ignore_rw2',
'drd/tests/annotate_ignore_write',
'drd/tests/annotate_ignore_write2',
'drd/tests/annotate_order_1',
'drd/tests/annotate_order_2',
'drd/tests/annotate_order_3',
'drd/tests/annotate_rwlock',
'drd/tests/annotate_sem',
'drd/tests/annotate_smart_pointer',
'drd/tests/annotate_smart_pointer2',
'drd/tests/annotate_spinlock',
'drd/tests/annotate_static',
'drd/tests/atomic_var',
'drd/tests/bar_bad',
'drd/tests/bar_bad_xml',
'drd/tests/bar_trivial',
'drd/tests/boost_thread',
'drd/tests/bug-235681',
'drd/tests/bug322621',
'drd/tests/circular_buffer',
'drd/tests/concurrent_close',
'drd/tests/dlopen',
'drd/tests/fork-parallel',
'drd/tests/fork-serial',
'drd/tests/fp_race',
'drd/tests/fp_race2',
'drd/tests/fp_race_xml',
'drd/tests/free_is_write',
'drd/tests/free_is_write2',
'drd/tests/hg01_all_ok',
'drd/tests/hg02_deadlock',
'drd/tests/hg03_inherit',
'drd/tests/hg04_race',
'drd/tests/hg05_race2',
'drd/tests/hg06_readshared',
'drd/tests/linuxthreads_det',
'drd/tests/matinv',
'drd/tests/monitor_example',
'drd/tests/pth_barrier',
'drd/tests/pth_barrier2',
'drd/tests/pth_barrier3',
'drd/tests/pth_barrier_race',
'drd/tests/pth_barrier_thr_cr',
'drd/tests/pth_broadcast',
'drd/tests/pth_cancel_locked',
'drd/tests/pth_cleanup_handler',
'drd/tests/pth_cond_race',
'drd/tests/pth_cond_race2',
'drd/tests/pth_cond_race3',
'drd/tests/pth_create_chain',
'drd/tests/pth_detached',
'drd/tests/pth_detached2',
'drd/tests/pth_detached3',
'drd/tests/pth_detached_sem',
'drd/tests/pth_inconsistent_cond_wait',
'drd/tests/pth_once',
'drd/tests/pth_spinlock',
'drd/tests/read_and_free_race',
'drd/tests/rwlock_race',
'drd/tests/rwlock_test',
'drd/tests/sem_as_mutex',
'drd/tests/sem_as_mutex2',
'drd/tests/sem_as_mutex3',
'drd/tests/sem_open',
'drd/tests/sem_open2',
'drd/tests/sem_open3',
'drd/tests/sem_open_traced',
'drd/tests/sigalrm',
'drd/tests/std_atomic',
'drd/tests/std_list',
'drd/tests/std_mutex',
'drd/tests/std_string',
'drd/tests/std_thread',
'drd/tests/swapcontext',
'drd/tests/tc01_simple_race',
'drd/tests/tc02_simple_tls',
'drd/tests/tc03_re_excl',
'drd/tests/tc05_simple_race',
'drd/tests/tc06_two_races',
'drd/tests/tc07_hbl1',
'drd/tests/tc08_hbl2',
'drd/tests/tc09_bad_unlock',
'drd/tests/tc11_XCHG',
'drd/tests/tc16_byterace',
'drd/tests/tc17_sembar',
'drd/tests/tc18_semabuse',
'drd/tests/tc19_shadowmem',
'drd/tests/tc21_pthonce',
'drd/tests/tc22_exit_w_lock',
'drd/tests/tc23_bogus_condwait',
'drd/tests/tc24_nonzero_sem',
'drd/tests/thread_name',
'drd/tests/thread_name_xml',
'drd/tests/threaded-fork-vcs',
'drd/tests/threaded-fork',
'drd/tests/tls_threads',
'massif/tests/deep-D']


It seems that
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2233
was under more load has it had python3 fail and more strace failures.

I'll triage the remaining intermittent ptest failures

thanks, the good thing is that these packages are quite sticky to
glibc internals so usually an upgrade if available
for them will sort things out, glibc is merging libpthread/librt etc
into libc so lot of valgrind failures could be due to that
I will see what I can find.

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
--
# Randy MacLeod
# Wind River Linux


Re: glibc 2.34 tests

Khem Raj <raj.khem@...>
 

On Sat, Jul 3, 2021 at 2:29 PM Alexandre Belloni
<alexandre.belloni@bootlin.com> wrote:

Hello,

I've been testing multiple versions of Khem's branch for glibc2.34
Everything apart from non-gpl3 builds fine. There is a patch from Khem
to solve this issue, I didn't apply/test yet:

[yocto] [meta-gplv2] [PATCH] coreutils_6.9.bb: Fix build with glibc 2.34

On the tests side, systemd-journal was crashing, the last patch on
Khem's branch is solving the issue, thanks!

The remaining issues are on the ptests side:

https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2233/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1946/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2236/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1949/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2244/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1957/steps/12/logs/stdio

Issues happen both on qemux86-64 and qemuarm64 and they reproduced
every time:

'elfutils': ['run-backtrace-native.sh', 'run-backtrace-native-core.sh']

'strace': ['prlimit64.gen.test',
'xet_robust_list.gen.test',
'xet_robust_list--pidns-translation.gen.test'],

For valgrind, it is all over the place:

ARM has:
'valgrind': ['gdbserver_tests/hginfo',
'helgrind/tests/hg02_deadlock',
'drd/tests/boost_thread',
'drd/tests/pth_cond_race3',
'drd/tests/pth_create_chain',
'drd/tests/pth_detached',
'drd/tests/std_list',
'drd/tests/std_mutex',
'drd/tests/swapcontext',
'drd/tests/tc24_nonzero_sem',
'drd/tests/thread_name',
'drd/tests/thread_name_xml',
'drd/tests/threaded-fork-vcs',
'drd/tests/threaded-fork',
'drd/tests/tls_threads',
'massif/tests/deep-D']

x86 has:

'valgrind': ['gdbserver_tests/hginfo',
'memcheck/tests/supp_unknown',
'helgrind/tests/annotate_smart_pointer',
'helgrind/tests/bar_bad',
'helgrind/tests/hg01_all_ok',
'helgrind/tests/hg02_deadlock',
'helgrind/tests/pth_destroy_cond',
'helgrind/tests/rwlock_test',
'helgrind/tests/tc05_simple_race',
'helgrind/tests/tc06_two_races',
'helgrind/tests/tc06_two_races_xml',
'helgrind/tests/tc14_laog_dinphils',
'helgrind/tests/tc17_sembar',
'helgrind/tests/tc19_shadowmem',
'helgrind/tests/tc21_pthonce',
'helgrind/tests/tc22_exit_w_lock',
'helgrind/tests/tc23_bogus_condwait',
'helgrind/tests/tls_threads',
'drd/tests/annotate_barrier',
'drd/tests/annotate_barrier_xml',
'drd/tests/annotate_hb_race',
'drd/tests/annotate_hbefore',
'drd/tests/annotate_ignore_read',
'drd/tests/annotate_ignore_rw',
'drd/tests/annotate_ignore_rw2',
'drd/tests/annotate_ignore_write',
'drd/tests/annotate_ignore_write2',
'drd/tests/annotate_order_1',
'drd/tests/annotate_order_2',
'drd/tests/annotate_order_3',
'drd/tests/annotate_rwlock',
'drd/tests/annotate_sem',
'drd/tests/annotate_smart_pointer',
'drd/tests/annotate_smart_pointer2',
'drd/tests/annotate_spinlock',
'drd/tests/annotate_static',
'drd/tests/atomic_var',
'drd/tests/bar_bad',
'drd/tests/bar_bad_xml',
'drd/tests/bar_trivial',
'drd/tests/boost_thread',
'drd/tests/bug-235681',
'drd/tests/bug322621',
'drd/tests/circular_buffer',
'drd/tests/concurrent_close',
'drd/tests/dlopen',
'drd/tests/fork-parallel',
'drd/tests/fork-serial',
'drd/tests/fp_race',
'drd/tests/fp_race2',
'drd/tests/fp_race_xml',
'drd/tests/free_is_write',
'drd/tests/free_is_write2',
'drd/tests/hg01_all_ok',
'drd/tests/hg02_deadlock',
'drd/tests/hg03_inherit',
'drd/tests/hg04_race',
'drd/tests/hg05_race2',
'drd/tests/hg06_readshared',
'drd/tests/linuxthreads_det',
'drd/tests/matinv',
'drd/tests/monitor_example',
'drd/tests/pth_barrier',
'drd/tests/pth_barrier2',
'drd/tests/pth_barrier3',
'drd/tests/pth_barrier_race',
'drd/tests/pth_barrier_thr_cr',
'drd/tests/pth_broadcast',
'drd/tests/pth_cancel_locked',
'drd/tests/pth_cleanup_handler',
'drd/tests/pth_cond_race',
'drd/tests/pth_cond_race2',
'drd/tests/pth_cond_race3',
'drd/tests/pth_create_chain',
'drd/tests/pth_detached',
'drd/tests/pth_detached2',
'drd/tests/pth_detached3',
'drd/tests/pth_detached_sem',
'drd/tests/pth_inconsistent_cond_wait',
'drd/tests/pth_once',
'drd/tests/pth_spinlock',
'drd/tests/read_and_free_race',
'drd/tests/rwlock_race',
'drd/tests/rwlock_test',
'drd/tests/sem_as_mutex',
'drd/tests/sem_as_mutex2',
'drd/tests/sem_as_mutex3',
'drd/tests/sem_open',
'drd/tests/sem_open2',
'drd/tests/sem_open3',
'drd/tests/sem_open_traced',
'drd/tests/sigalrm',
'drd/tests/std_atomic',
'drd/tests/std_list',
'drd/tests/std_mutex',
'drd/tests/std_string',
'drd/tests/std_thread',
'drd/tests/swapcontext',
'drd/tests/tc01_simple_race',
'drd/tests/tc02_simple_tls',
'drd/tests/tc03_re_excl',
'drd/tests/tc05_simple_race',
'drd/tests/tc06_two_races',
'drd/tests/tc07_hbl1',
'drd/tests/tc08_hbl2',
'drd/tests/tc09_bad_unlock',
'drd/tests/tc11_XCHG',
'drd/tests/tc16_byterace',
'drd/tests/tc17_sembar',
'drd/tests/tc18_semabuse',
'drd/tests/tc19_shadowmem',
'drd/tests/tc21_pthonce',
'drd/tests/tc22_exit_w_lock',
'drd/tests/tc23_bogus_condwait',
'drd/tests/tc24_nonzero_sem',
'drd/tests/thread_name',
'drd/tests/thread_name_xml',
'drd/tests/threaded-fork-vcs',
'drd/tests/threaded-fork',
'drd/tests/tls_threads',
'massif/tests/deep-D']


It seems that
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2233
was under more load has it had python3 fail and more strace failures.

I'll triage the remaining intermittent ptest failures

thanks, the good thing is that these packages are quite sticky to
glibc internals so usually an upgrade if available
for them will sort things out, glibc is merging libpthread/librt etc
into libc so lot of valgrind failures could be due to that
I will see what I can find.

--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

21 - 40 of 225