Tobias Pfeiffer

Hi there, this is a known issue - you can find out more about the background etc. here: https://github.com/codeclimate/test-reporter/issues/413 Cheers, Tobi

Hmm probably :) I fell like I might need to clarify some things before that, also because they are not completely clear in my head (as in, some of them...

@elpikel lots of stuff :D I don't have the mind to fully refine this one atm but here's a couple that I think are good points: * #121 (just created)...

Huh, thanks for the report. Guess I have to get playing with live book. Weird that it isn't there but yeah... that this is the way to get the OTP...

Hey there, thanks for your feedback and issues you're raising! :green_heart: It's eerily similar in some aspects to #325 . I like the idea of setting a maximum_sample_size in general....

@michalmuskala yes that's exactly how I'd like it to be done :) I think right now through the memory vs. runtime split there's a bit of duplication/things that we need...

:wave: Hello, I believe I already gave you the "Hands, sorry" talk so I'm gonna skip it :grin: Specs absolutely should be updated. Iirc we even have tests to make...

Ah I see, the `pre_check` feature that runs every job once wouldn't help? :thinking:

Run time histograms, with input:  without input:  Full HTML reports: with input: http://www.pragtob.info/benchee/input-no-input/map_inputs_with_inputs_lol_map_flatten.html without input: http://www.pragtob.info/benchee/input-no-input/map_inputs_without_inputs_map_flatten.html

To summarize really quickly, without input performance seems a lot less stable and frequently jumping between top notch performance and bad performance:  whereas with input it still seems jumpy,...