Andrew Brown

@fitzgen, should we now consider this closed? If the CI issues with `benchmark_effect_size` are no longer a problem, maybe my "access violation" hypothesis was incorrect and it was the variance...

I don't think this is resolved. @jlb6740 just triggered it again yesterday ([logs](https://github.com/bytecodealliance/sightglass/actions/runs/4411814530/jobs/7730681746#step:7:346)). I'm going to disable the test on Windows until we figure out what is going on.

Nice ideas! When I included #224 I had some (but definitely not all!) of the same thoughts but then I said to myself, "what are users likely to do?" I...

Maybe this issue should be moved to the wasi-libc or Wasmtime repository, whichever we think is more likely the problem? cc: @sunfishcode.

When we do this, I think we should remove or dramatically simplify `benchmarks-next/run.sh`.

Ah, ok, thanks for the report: a bunch of documentation just changed and some links were likely missed. Where did you find this broken link?

@geekbeast, commenting here to keep related topics in this issue: @brianjjones is actively working on this issue (#70, #72, #73) and I'm sure would be happy to discuss any parts...

To take this one step further, I've been going back and forth about whether we should bring in a progress meter here. We know how many iterations need to be...

Ok, no progress bars. One thing I just looked up is whether we could detect an ANSI terminal and just rewrite the same line; [seems like it might work with...

@danbev, thanks for this PR and apologies for not looking at it sooner. The reason is that I'm actually working on this at the moment (e.g., https://github.com/bytecodealliance/wasmtime/pull/8519) and have been...