Problems loading benchmarks_generated.js of v4.7.1

[birkskyum]

When running the bench, it only shows 4.7.1 and main and not the current branch. My hypothesis is that it fails to load/register the latest tag 4.7.1, then loads main (displayed as 4.7.1) and the local branch (displayed as main).

Workaround

Changing this line:

maplibre-gl-js/test/bench/versions/index.html

Line 24 in 3160299

window.versionsDisplayName = [responseJson['tag_name'], 'main'];

To use 4.7.0 instead:
window.versionsDisplayName = ['v4.7.0', 'main'];

Resolves the problem:

[HarelM]

4.7.1 was recently uploaded to gh-pages, one should be able to try and load the script and see what's wrong.
I guess we should have better automation to avoid these kind of issues...

[HarelM]

It is possible that this is because main and 4.7.1 have the same commit and so the code the runs the benchmarks gets confused and only shows main and the current branch with the wrong titles?
The following seems to work for me:

$1> npm run start-bench
$2> npm run benchmark -- --compare v4.7.0 --compare v4.6.0 --compare v4.7.1

[HarelM]

I think the following code solves this issue and issues in general where you add version with the same commit, I'm just not sure it's worth adding to the benchmark code, it is already too complicated... :-(
This basically checks (badly) that when loading a new script more benchmarks versions are added, and if this is not the case the current version display name is removed from the list.