- Sep 24, 2019
-
-
Pierre-Yves David authored
Let's try to move toward a new a better naming.
-
Pierre-Yves David authored
This will make it simple to pick a benchmark name.
-
Pierre-Yves David authored
If things are slow, we'll do with less loop. That is better than very long bench run and no numbers from time out.
-
Pierre-Yves David authored
We should probably do that upstream
-
Pierre-Yves David authored
And try our best otherwise.
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
- Sep 23, 2019
-
-
Pierre-Yves David authored
They have a dedicated "identical" benchmark now.
-
Pierre-Yves David authored
-
Pierre-Yves David authored
We expect these to make the rust code shine.
-
Pierre-Yves David authored
All other function name have "discovery" in them. Let us be consistent here.
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
Pierre-Yves David authored
We don't want error to silently pass, revision should either be silently skipped or work.
-
Pierre-Yves David authored
-
Pierre-Yves David authored
This is very useful when a benchmark are recenty introduced but is compatible with a larger range of revision.
-
Pierre-Yves David authored
This decorator that getting into play "after" the setup. That was too late.
-
Pierre-Yves David authored
We use a clear, simple but direct approach to skip test involving http for problematic revision.
-
- Sep 14, 2019
-
-
Pierre-Yves David authored
using explicite naming scheme help us to be more agile in the source code organisation. We extract an `utils.exchange` module in the process.
-
Pierre-Yves David authored
We move them to a new naming scheme
-
Pierre-Yves David authored
The current bench suite grew to an unmanageable point. Let us comment everything and reintroduce them slowly with scrutiny.
-
Pierre-Yves David authored
The current bench suite grew to an unmanageable point. Let us comment everything and reintroduce them slowly with scrutiny.
-
Pierre-Yves David authored
The current bench suite grew to an unmanageable point. Let us comment everything and reintroduce them slowly with scrutiny.
-
- Sep 24, 2019
-
-
Pierre-Yves David authored
Otherwise, the variant has no effect...
-
Pierre-Yves David authored
This is surprising and source of error. So we better improve the documentation a bit.
-
- Sep 14, 2019
-
-
Pierre-Yves David authored
We need more specialized util in various places. (yeah, the module to package switch will likely be a small pain)
-
- Sep 23, 2019
-
-
Pierre-Yves David authored
When running with an older Mercurial version we might need to look into the source repository. note: we should probably do these lookup using the system Mercurial anyway.
-
Pierre-Yves David authored
the short `-T` version got introduced later and is compatible with less revisions.
-
- Sep 16, 2019
-
-
Raphaël Gomès authored
-
- Sep 13, 2019
-
-
Pierre-Yves David authored
We get the actual command output instead of a traceback within the benchmark code.
-
Pierre-Yves David authored
I am not sure what the previous code was trying to achieve... but this should work fine.
-
Pierre-Yves David authored
This can be useful in other context.
-
Pierre-Yves David authored
I find the new form clearer.
-
Pierre-Yves David authored
This is a common short form.
-
Raphaël Gomès authored
This was forgotten in 608:f6394b762bec when adding the partial sets to the repository variants.
-
Raphaël Gomès authored
-
Pierre-Yves David authored
this will result in extra processing and output.
-
Raphaël Gomès authored
-
Pierre-Yves David authored
1) this is what it is meant for so let us use it. 2) if we don't use it, the user's `local.repos` will be used instead of the `default.repos` we carefully built for the test.
-