Yocto Build Failure Swat Team - Revision history

Oleksiy Obitotskyy at 10:35, 5 October 2021

2021-10-05T10:35:49Z

← Older revision		Revision as of 10:35, 5 October 2021
Line 119:		Line 119:

	* [[User:Jagadheesan \| Jaga]]		* [[User:Jagadheesan \| Jaga]]

			* [[User:Valerii Chernous \| Valerii Chernous]]

SaulWold: /* Tips */

2021-09-02T21:48:14Z

Tips

← Older revision		Revision as of 21:48, 2 September 2021
Line 79:		Line 79:

	In the stdio logs window, clicking on the looking glass icon will load the full log in the browser, allowing you to use the search feature of the browser. Quite often, you'll start by looking for "error:".		In the stdio logs window, clicking on the looking glass icon will load the full log in the browser, allowing you to use the search feature of the browser. Quite often, you'll start by looking for "error:".

			Be sure to check all log files, especially the testimage logs that are available for qemu_boot_log (for example in: /tmp/work/qemux86_64-poky-linux/core-image-sato-sdk/1.0-r0/testimage/qemu_boot_log.20210902120413)

	== Handoff ==		== Handoff ==

Thomas Perrot at 07:21, 15 March 2021

2021-03-15T07:21:08Z

← Older revision		Revision as of 07:21, 15 March 2021
Line 36:		Line 36:
	* A link to the build failure. Either a link to the [http://errors.yoctoproject.org/ error reports] page (such as http://errors.yoctoproject.org/Errors/Details/199667/) or a link to the autobuilder build log (such as https://autobuilder.yoctoproject.org/typhoon/#/builders/34/builds/168).		* A link to the build failure. Either a link to the [http://errors.yoctoproject.org/ error reports] page (such as http://errors.yoctoproject.org/Errors/Details/199667/) or a link to the autobuilder build log (such as https://autobuilder.yoctoproject.org/typhoon/#/builders/34/builds/168).

	When filing bugs, always search Bugzilla first to see if the issue is already known. For example, there are some bugs that occur intermittently and are already filed with ''AB-INT'' in the whiteboard field. They are listed here: [https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT&list_id=~~620110~~ Autobuilder issues]		When filing bugs, always search Bugzilla first to see if the issue is already known. For example, there are some bugs that occur intermittently and are already filed with ''AB-INT'' in the whiteboard field. They are listed here: [https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=whiteboard%3AAB-INT&list_id=640327 Autobuilder issues]

	The exact progress depends on whether the branch is an official branch or a staging branch.		The exact progress depends on whether the branch is an official branch or a staging branch.

Oleksiy Obitotskyy: /* Members */

2021-03-12T14:22:25Z

Members

← Older revision		Revision as of 14:22, 12 March 2021
Line 97:		Line 97:

	* [[User:SaulWold \| Saul Wold]]		* [[User:SaulWold \| Saul Wold]]

			* [[User:Oleksiy Obitotskyy \| Oleksiy Obitotskyy]]

	* [[User:Alejandro Enedino Hernandez Samaniego \| Alejandro Hernandez Samaniego]]		* [[User:Alejandro Enedino Hernandez Samaniego \| Alejandro Hernandez Samaniego]]

Thomas Perrot at 15:52, 8 March 2021

2021-03-08T15:52:52Z

← Older revision		Revision as of 15:52, 8 March 2021
Line 92:		Line 92:
	* [[User:Anibal Limon \| Anibal Limon]]		* [[User:Anibal Limon \| Anibal Limon]]

	* Köry Maincent		* [[User:Köry maincent \| Köry Maincent]]

			* [[User:Thomas Perrot \| Thomas Perrot]]

	* [[User:SaulWold \| Saul Wold]]		* [[User:SaulWold \| Saul Wold]]

Alexandre Belloni: /* Members */

2021-03-05T22:21:59Z

Members

← Older revision		Revision as of 22:21, 5 March 2021
Line 91:		Line 91:

	* [[User:Anibal Limon \| Anibal Limon]]		* [[User:Anibal Limon \| Anibal Limon]]

			* Köry Maincent

	* [[User:SaulWold \| Saul Wold]]		* [[User:SaulWold \| Saul Wold]]

Alexandre Belloni: /* Process */

2021-03-03T20:56:27Z

Process

← Older revision		Revision as of 20:56, 3 March 2021
Line 40:		Line 40:
	The exact progress depends on whether the branch is an official branch or a staging branch.		The exact progress depends on whether the branch is an official branch or a staging branch.

	==== ~~Official~~ Branches ====		==== Staging Branches ====

			For builds against staging branches which contain patches under test for integration (such as master-next, stable/dunfell-nut, ross/mut, etc), first attempt to identify if there is a patch in the branch that is likely to be responsible for the failure. For example, if <tt>wget</tt> fails with <tt>libgnutls</tt> errors and there is a GnuTLS upgrade in the branch, then that is a likely candidate. If a patch can be identified that hasn't yet been merged into an official branch, then reply to the patch on the mailing list with the details. If it isn't obvious which patch is responsible for the failure, or a patch can be identified but it has already been merged to the release branch, then file a bug and ensure the branch maintainer (see the [[Releases]] page for names) is on the CC list.

	~~For builds~~ of ~~official~~ branches, that is ~~master~~ or ~~a release branch~~, ~~'''all failures or warnings are critical''' and must be [~~[#~~Filing_bugs \| filed in Bugzilla]~~]. ~~Remember to check~~ that ~~the issue isn't already filed. Where an issue is already filed~~, ~~please do add a comment so we~~ can ~~assess how frequently different issues are occurring.~~		Most of the failures will be for staging branches as master-next is the branch that is tested the most. However, it is rebased quite frequently so it is not always easy to find which patchs were included. In that case, you have to get the actual commit hash, for example in the build properties, the variable is <tt>yp_build_revision</tt> or in the build configuration at the beginning of the stdio log. For example, this qemux86 build [https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/3120] was master-next at revision 47482eff9897ccde946e9247724babc3a586d318.
			With that information, you can then clone poky (or any other layer of interest) and fetch the proper commit and see the git log:

	~~==== Staging Branches ====~~		<pre>
			$ git clone git://git.yoctoproject.org/poky
			$ cd poky
			$ git fetch origin 47482eff9897ccde946e9247724babc3a586d318
			$ git log FETCH_HEAD
			</pre>

	For builds against staging branches which contain patches under test for integration (such as master-next, stable/dunfell-nut, ross/mut, etc), first attempt to identify if there is a patch in the branch that is likely to be responsible for the failure. For example, if <tt>wget</tt> fails with <tt>libgnutls</tt> errors and there is a GnuTLS upgrade in the branch, then that is a likely candidate. If a patch can be identified that hasn't yet been merged into an official branch, then reply to the patch on the mailing list with the details. If it isn't obvious which patch is responsible for the failure, or a patch can be identified but it has already been merged to the release branch, then file a bug and ensure the branch maintainer (see the [[Releases]] page for names) is on the CC list.

	'''If in doubt, file a bug'''. All errors must be taken care of.		'''If in doubt, file a bug'''. All errors must be taken care of.

	If the issue is in the infrastructure or autobuilder itself then file a bug against "Infrastructure: Autobuilder", infrastructure bugs should be assigned to [[User:Halstead\| Michael Halstead]] and autobuilder logic bugs to [[User:Rpurdie \| Richard Purdie]].		If the issue is in the infrastructure or autobuilder itself then file a bug against "Infrastructure: Autobuilder", infrastructure bugs should be assigned to [[User:Halstead\| Michael Halstead]] and autobuilder logic bugs to [[User:Rpurdie \| Richard Purdie]].

			==== Official Branches ====

			For builds of official branches, that is master or a release branch, '''all failures or warnings are critical''' and must be [[#Filing_bugs \| filed in Bugzilla]]. Remember to check that the issue isn't already filed. Where an issue is already filed, please do add a comment so we can assess how frequently different issues are occurring.

	=== Update ===		=== Update ===

Jagadheesan: /* Members */

2021-02-04T17:41:17Z

Members

← Older revision		Revision as of 17:41, 4 February 2021
Line 98:		Line 98:

	* [[User:Minjae Kim \| Minjae Kim]]		* [[User:Minjae Kim \| Minjae Kim]]

			* [[User:Jagadheesan \| Jaga]]

Alexandre Belloni: /* Process */

2021-02-01T21:41:44Z

Process

← Older revision		Revision as of 21:41, 1 February 2021
Line 17:		Line 17:
	The builds are shown in a tree like structure with the parent build and any child builds under it. The builds are edited as a group under the parent as quite often a failure might be common to the child builds. Each failure does need to be triaged individually although multiple builds can be changed at once to a given resolution.		The builds are shown in a tree like structure with the parent build and any child builds under it. The builds are edited as a group under the parent as quite often a failure might be common to the child builds. Each failure does need to be triaged individually although multiple builds can be changed at once to a given resolution.

	Once you have selected an issue to triage, you will have to take the correct reporting action and finally edit the entry to indicate what was done.		Swatbot can filter pending issues to be triaged using the [https://swatbot.yoctoproject.org/mainindex/swat/ SWAT Pending Builds] link. Once you have selected an issue to triage, you will have to take the correct reporting action and finally edit the entry to indicate what was done.

	You can also be notified when a build fails by subscribing to the [https://lists.yoctoproject.org/g/yocto-builds yocto-builds] mailing list. This is sending a mail when a build fails, including direct links to the [https://autobuilder.yoctoproject.org/ autobuilder job summary] and the [https://errors.yoctoproject.org/Errors/Latest/Autobuilder/ Error Reporting Service]. The mail will also state if it is expected that the build is triaged by Swat, so check this to see if the build can be ignored as the owner is taking full responsibility. Currently, swatbot will not give you this information so you have to get it from the autobuilder build entry (the <tt>Build properties</tt> tab should have: <tt>swat_monitor true</tt>), the autobuilder API, or the notification email.		You can also be notified when a build fails by subscribing to the [https://lists.yoctoproject.org/g/yocto-builds yocto-builds] mailing list. This is sending a mail when a build fails, including direct links to the [https://autobuilder.yoctoproject.org/ autobuilder job summary] and the [https://errors.yoctoproject.org/Errors/Latest/Autobuilder/ Error Reporting Service]. The mail will also state if it is expected that the build is triaged by Swat, so check this to see if the build can be ignored as the owner is taking full responsibility. Currently, swatbot will not give you this information so you have to get it from the autobuilder build entry (the <tt>Build properties</tt> tab should have: <tt>swat_monitor true</tt>), the autobuilder API, or the notification email.

Rpurdie: /* Process */

2021-01-30T17:54:07Z

Process

← Older revision		Revision as of 17:54, 30 January 2021
Line 13:		Line 13:
	== Process ==		== Process ==

	The SWAT process is now using a specific tool, [https://swatbot.yoctoproject.org/ swatbot]. Swatbot will list all the pending issues that ~~needs~~ to be triaged using [https://swatbot.yoctoproject.org/mainindex/swat/ this link ] or the "SWAT Pending Builds" link on the left hand menu. Each issue has links to the autobuilder stdio, warning ~~and~~ error logs.		The SWAT process is now using a specific tool, [https://swatbot.yoctoproject.org/ swatbot]. Swatbot has a filter which will list all the pending issues that need to be triaged using [https://swatbot.yoctoproject.org/mainindex/swat/ this link ] or the "SWAT Pending Builds" link on the left hand menu. Each issue has links to the autobuilder logs for the failing step (e.g. usually stdio and warning/error logs).

	Once you have selected an issue to triage, you will have to take the ~~proper~~ reporting action and finally edit the entry to indicate what was ~~the resolution~~.		The builds are shown in a tree like structure with the parent build and any child builds under it. The builds are edited as a group under the parent as quite often a failure might be common to the child builds. Each failure does need to be triaged individually although multiple builds can be changed at once to a given resolution.

			Once you have selected an issue to triage, you will have to take the correct reporting action and finally edit the entry to indicate what was done.

	You can also be notified when a build fails by subscribing to the [https://lists.yoctoproject.org/g/yocto-builds yocto-builds] mailing list. This is sending a mail when a build fails, including direct links to the [https://autobuilder.yoctoproject.org/ autobuilder job summary] and the [https://errors.yoctoproject.org/Errors/Latest/Autobuilder/ Error Reporting Service]. The mail will also state if it is expected that the build is triaged by Swat, so check this to see if the build can be ignored as the owner is taking full responsibility. Currently, swatbot will not give you this information so you have to get it from the autobuilder build entry (the <tt>Build properties</tt> tab should have: <tt>swat_monitor true</tt>), the autobuilder API, or the notification email.		You can also be notified when a build fails by subscribing to the [https://lists.yoctoproject.org/g/yocto-builds yocto-builds] mailing list. This is sending a mail when a build fails, including direct links to the [https://autobuilder.yoctoproject.org/ autobuilder job summary] and the [https://errors.yoctoproject.org/Errors/Latest/Autobuilder/ Error Reporting Service]. The mail will also state if it is expected that the build is triaged by Swat, so check this to see if the build can be ignored as the owner is taking full responsibility. Currently, swatbot will not give you this information so you have to get it from the autobuilder build entry (the <tt>Build properties</tt> tab should have: <tt>swat_monitor true</tt>), the autobuilder API, or the notification email.

← Older revision		Revision as of 14:22, 12 March 2021
Line 97:		Line 97:

	* [[User:SaulWold \| Saul Wold]]		* [[User:SaulWold \| Saul Wold]]

			* [[User:Oleksiy Obitotskyy \| Oleksiy Obitotskyy]]

	* [[User:Alejandro Enedino Hernandez Samaniego \| Alejandro Hernandez Samaniego]]		* [[User:Alejandro Enedino Hernandez Samaniego \| Alejandro Hernandez Samaniego]]

← Older revision		Revision as of 15:52, 8 March 2021
Line 92:		Line 92:
	* [[User:Anibal Limon \| Anibal Limon]]		* [[User:Anibal Limon \| Anibal Limon]]

	* Köry Maincent		* [[User:Köry maincent \| Köry Maincent]]

			* [[User:Thomas Perrot \| Thomas Perrot]]

	* [[User:SaulWold \| Saul Wold]]		* [[User:SaulWold \| Saul Wold]]