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.
Try running with debug enabled in web browser.
(In reply to Randy MacLeod from comment #1) > Try running with debug enabled in web browser. https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3857 got hit also: I had the javascript console open and saw: Uncaught (in promise) SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data a https://autobuilder.yoctoproject.org/valkyrie/plugins/yocto_console_view/scripts.js:13 a https://autobuilder.yoctoproject.org/valkyrie/plugins/yocto_console_view/scripts.js:13 u https://autobuilder.yoctoproject.org/valkyrie/plugins/yocto_console_view/scripts.js:13 EventListener.handleEvent* https://autobuilder.yoctoproject.org/valkyrie/plugins/yocto_console_view/scripts.js:13 mz https://autobuilder.yoctoproject.org/valkyrie/assets/index-DAU-Rq3u.js:105 ur https://autobuilder.yoctoproject.org/valkyrie/assets/index-DAU-Rq3u.js:99 <anonymous> https://autobuilder.yoctoproject.org/valkyrie/plugins/yocto_console_view/scripts.js:13 <anonymous> https://autobuilder.yoctoproject.org/valkyrie/plugins/yocto_console_view/scripts.js:1 <anonymous> https://autobuilder.yoctoproject.org/valkyrie/plugins/yocto_console_view/scripts.js:1 The exception appears at scripts.js:13:54260
Note: the build I retried just after did not have the exception and did not have the bug.
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
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"
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)
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
(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.
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!