Bug 258920

Since 249031 we are running performance tests with multiple RPis in parallel.

And there is a potential issue that can happen because there are several workers for each performance bot working in parallel.

Bot1 starts testing commit 1234@main
Bot2 starts testing commit 1245@main

Bot2 ends before than Bot1 -> The data on the dashboard will appear as if commit 1245@main happened before than 1234@main because the dashboard doesn't use the browser_version (or commit revision) to sort the data.
The dashboard sorts the data by the timestamp. And the runner (the bot) defaults to sends automatically a timestamp with the date of when it finish testing.


To overcome this problem we can implement a way of sending the data with the timestamp of the checked_out git commit (HEAD).

That way we can also re-run performance tests on old checkouts and the data will be sent to the server with the right timestamp.

We don't really care about when the performance test was executed, in reality we should care about the commit date of the commit that we have built (that is the one checked out).