Iterations rerun displayed at the bottom is read from config, rather the analysis' algorithm setting which are a copy of config.
With the changes to determining true pass rate using multiple swarming tasks and stopping only when they converge, the config's default value is unlikely to be the true number of iterations ran.
Need an easy way to determine the true number of iterations that were run, possibly for each data point (e.g. in the mouse-over) since they may vary depending on how long it took for the pass rate to converge
Comment 1 by sheriffbot@chromium.org
, Sep 24Status: Untriaged (was: Available)