I require every benchmark be run at least four times and average the most consistent/best runs of the three to tease out any flukey runs. Or in extreme cases signify there's a problem with the test setup that the results are so wild. Thus there should be a way to group results together as a singular test for a card to create a comparison with.
This might require a separate model that sits between the "hardware"/"benchmark" models and the "result" model to group the raw results.
I require every benchmark be run at least four times and average the most consistent/best runs of the three to tease out any flukey runs. Or in extreme cases signify there's a problem with the test setup that the results are so wild. Thus there should be a way to group results together as a singular test for a card to create a comparison with.
This might require a separate model that sits between the "hardware"/"benchmark" models and the "result" model to group the raw results.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I require every benchmark be run at least four times and average the most consistent/best runs of the three to tease out any flukey runs. Or in extreme cases signify there's a problem with the test setup that the results are so wild. Thus there should be a way to group results together as a singular test for a card to create a comparison with.
This might require a separate model that sits between the "hardware"/"benchmark" models and the "result" model to group the raw results.
Closing as this was handled in
c940a248d7