search for: prev_sampl

...nt samples) == 1, will flag a lot of samples, especially if len(prev) > 1. Reruns actually make this worse by making it likely that we flag the next run after the run we rerun. For instance, a flat line with 5% random noise flags all the time. Besides the Mann Whitney U test, we are not using prev_samples in any way sane way. Ideas: -Try and get more samples in as many places as possible. Maybe —multisample=4 should be the default? Make bots run more often (I have already done this on green dragon). - Use recent past run information to enhance single sample regression detection. I think we...

...noisiness in the number > of branch mispredicts). > BTW – graphs like the one in attachment make me think that the LNT webUI should be showing > sample points by default instead of line graphs showing the minimum execution time > per build number. > > > >> - Currently prev_samples is almost always just one other run, probably >> with only one sample itself. Lets give this more samples to work with. >> Start passing more previous run data to all uses of the algorithm, in >> most places we intentionally limit the computation to current=run and >> pre...