You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently we had a collision on "experiment run id" for three automated experiment runs. We should reconsider how we determine this value. Currently it's computed as the hex representation of the current timestamp seconds.
At first it seems seems unlikely that two or more experiments will compute the same run id, but given that we now have 39 (at the time of this writing) projects running automated experiments, each running 2-3 experiments, and them all starting at the exact same time Sunday @ 9:00 UTC, it's bound to happen often.
Recently we had a collision on "experiment run id" for three automated experiment runs. We should reconsider how we determine this value. Currently it's computed as the hex representation of the current timestamp seconds.
https://github.com/gradle/gradle-enterprise-build-validation-scripts/blob/fc1a6d6fc6e87c22ceb3d4f2c4fa50d8ea9a2fa9/components/scripts/lib/init.sh#L17-L19
At first it seems seems unlikely that two or more experiments will compute the same run id, but given that we now have 39 (at the time of this writing) projects running automated experiments, each running 2-3 experiments, and them all starting at the exact same time Sunday @ 9:00 UTC, it's bound to happen often.
Example: https://ge.solutions-team.gradle.com/scans?search.names=Experiment%20run%20id&search.timeZoneId=America/Chicago&search.values=64f44be9&selection.buildScanB=ygdfpgm4geobu
The text was updated successfully, but these errors were encountered: