After we switched to bitbake-setup, several data are missing on new entries in errors.yoctoproject.org.

I will try to summarize what I understood below.

So first, an error-report.txt json file is generated by the report-error bbclass during builds. Typical example:

{
    "auto_conf": "SDKMACHINE = \"x86_64\"\nPACKAGE_CLASSES = \"package_rpm\"\nDL_DIR = '/srv/autobuilder/valkyrie.yocto.io/current_sources'\nSSTATE_DIR ?= '/srv/autobuilder/valkyrie.yocto.io/pub/sstate'\nSANITY_TESTED_DISTROS = ''\nBB_HASHSERVE = 'wss://hashserv-eu.yoctoproject.org/ws'\nOE_FRAGMENTS += 'core/yocto-autobuilder/autobuilder core/yocto-autobuilder/autobuilder-resource-constraints'\nEXTRA_IMAGE_FEATURES ?= 'allow-empty-password empty-root-password allow-root-login'\n",
    "bitbake_version": "2.15.2",
    "branch_commit": "mathieu/master-next: 7a571c23b137c4bf60fa6d402e3f86195f263bde",
    "build_sys": "x86_64-linux",
    "component": "core-image-full-cmdline:do_build core-image-sato-sdk:do_build core-image-minimal:do_build",
    "distro": "poky",
    "failures": [],
    "layer_version": [
        "meta                 = \"mathieu/master-next:7a571c23b137c4bf60fa6d402e3f86195f263bde\"",
        "meta-yocto-bsp       ",
        "meta-poky            = \"master:fe65e142d0d9ba0e51ff9175ffa82e902f982a20\""
    ],
    "local_conf": "",
    "machine": "qemuarm64",
    "nativelsb": "universal/fedora-41",
    "target_sys": "aarch64-poky-linux"
}

This report is then sent to errors.yoctoproject.org using scripts/send-error-report. Report will be parsed to extract some properties and make them available online. E.g. https://errors.yoctoproject.org/Errors/Details/885372/

I believe parsing is done here: https://git.yoctoproject.org/error-report-web/tree/Post/parser.py#n24

So, first issue: the commit is no longer extracted correctly. Values in the "branch_commit" field of above json looks correct, but for some reason the web page report "Commit: unknown".

Additionally, a lot of other entries of the above report are unpopulated: host distro, build system, target system... We need to investigate why.

In addition, we probably want to add bitbake branch/commit as we are no longer using the poky repo. Maybe meta-yocto also.

What about branches/commits shown on https://errors.yoctoproject.org/Errors/Latest/Autobuilder/ ?

Also, we need to ensure search URLs used on the autobuilder console view are still working after all of that: https://git.yoctoproject.org/yocto-autobuilder2/tree/yocto_console_view/src/views/ConsoleView/ConsoleView.tsx#n200