Bug 16291 - Buildbot "branch selector" does not always work
Summary: Buildbot "branch selector" does not always work
Status: NEW
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 6.2
Assignee: Mathieu Dubois-Briand
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2026-05-20 21:08 UTC by Yoann Congal
Modified: 2026-11-11 00:00 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yoann Congal 2026-05-20 21:08:47 UTC
For example, see: https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3787. This is a build I started with the branch selector.

In the "build properties" we see:
branch	""
swat_monitor true
reason ""


But
branchselector "scarthgap-nut: {\"reason\": \"Stable maintenance - scarthgap-nut\", \"branch\": \"scarthgap\", \"swat_monitor\": false, ...

... as if the branchselector data was not applied to the buildbot properties...

For scarthgap builds it crashes quickly, it tries to use bitbake-setup that does not exist in that environment.
Comment 1 Randy MacLeod 2026-05-21 14:49:08 UTC
Try running with debug enabled in web browser.
Comment 3 Yoann Congal 2026-05-21 20:02:03 UTC
Note: the build I retried just after did not have the exception and did not have the bug.
Comment 4 Yoann Congal 2026-06-04 15:14:17 UTC
Some more info:
* I use Firefox (version 151.0.2)
* I see this bug when building a-full
* The fields missing in the transition from the branch selector to the actual builds include:
  * "branch" (the yocto-autobuilder-helper branch): set to my stable branch -> reset to default "master"
  * "swat_monitor": set to False -> reset to default "True"
* Since I've started monitoring, this bug happened if and only if the "Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data" error appeared
Comment 5 Yoann Congal 2026-06-04 16:15:30 UTC
Gemini (!) helped me found a reproducer:
* Go to a-full: https://autobuilder.yoctoproject.org/valkyrie/?#/builders/29
* Click "Start a-full Build"
* In "Release Shortcut Selector" field, type "sc"
* use keyboard arrows to target "scarthgap"
* hit enter with the keyboard (that the part Gemini pointed to)
* Click on "Start build"
* Wait for the build page to load

In the build property, the "branch" field is "" when "scarthgap" is expected.

Note: This sequence triggers the bug BUT NOT the exception (the exception is note the cause of this bug)

Side note: The exception is easily triggered by hitting enter in any field, eg "Reason"
Comment 6 Yoann Congal 2026-11-06 23:13:01 UTC
despite recent commits from Mathieu (thanks!):
releaseselector: Fix release selector not applied on keyboard use
https://git.yoctoproject.org/yocto-autobuilder2/commit/?id=92ac54e35a76e66ca6b596a1bc7763f06aa261e8
releaseselector: Fix checkbox filling
https://git.yoctoproject.org/yocto-autobuilder2/commit/?id=aadd487aa9a44beaf1140ef2062e494353df2b44
releaseselector: Read release shortcuts from the force scheduler spec
https://git.yoctoproject.org/yocto-autobuilder2/commit/?id=6430d31028f9da5630b40deebc480ad5b744b147

... I had the issue:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/29/builds/5075 (wrynose build using master helper)
Comment 7 Yoann Congal 2026-11-06 23:31:39 UTC
Might just be because Mathieu's commits do not seem to be deployed on the AB instance:
https://autobuilder.yoctoproject.org/valkyrie/plugins/yocto_console_view/scripts.js: (after reindentation)
          const w = n.get('force-field-branchselector'),
          O = w.parentNode.previousSibling,
          j = O.textContent.indexOf(':');

That look like the removed code of
https://git.yoctoproject.org/yocto-autobuilder2/commit/?id=6430d31028f9da5630b40deebc480ad5b744b147
Comment 8 Mathieu Dubois-Briand 2026-11-07 07:51:01 UTC
(In reply to Yoann Congal from comment #7)
> Might just be because Mathieu's commits do not seem to be deployed on the AB
> instance:

Yes, I believe it's still the old code. As an easy proof, on a broken browser (like Firefox on my phone), we can see each line of the drop down menu still contains the whole serialized configuration.
Comment 9 Yoann Congal 2026-11-11 00:00:09 UTC
I think it's fixed now (beware: old code can linger in the browser cache!)

IIUC, the plugin needed a manual rebuild before being deployed.

I'd say to use it for a few days/builds and then close this bug as fixed.

Thanks Mathieu!