- Sep 24, 2019
-
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
- Sep 23, 2019
-
-
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
the short `-T` version got introduced later and is compatible with less revisions.
-
- 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.
-
Raphaël Gomès authored
This was forgotten in 608:f6394b762bec when adding the partial sets to the repository variants.
-
- Aug 01, 2019
-
-
Raphaël Gomès authored
We can't make sure that no Rust code will be run before the rust module policy was introduced in 94167e701e125dce1788e19b1e1489958235e40c, in fact, we can be pretty sure of it.
-
- Jul 22, 2019
-
-
Raphaël Gomès authored
If the `setup` method fails, the tests session waits for timeout (1800s per benchmark!), because BaseExchangeMixin's setup launches `hg serve`. The ASV test runner does not understand that setup failed and it should move on to the next benchmark. This shuts down the `hg serve` in case the `setup` breaks.
-
- Jul 18, 2019
-
-
Pierre-Yves David authored
`self.check_output` call signature is sightly different from `subprocess.check_output`, so the call was wrong.
-
- May 17, 2019
-
-
Pierre-Yves David authored
Exchange test takes a lot of time, rsync is one of the factor. Factoring the code will make it easier to improve and measure.
-
Pierre-Yves David authored
-
- May 19, 2019
-
-
Pierre-Yves David authored
This new experimental mode need to be tracked. The initial implementation is quite slow but things could get better over time.
-
Pierre-Yves David authored
Before, not passing a filter_fn means the function will always return False
-
- May 18, 2019
-
-
Pierre-Yves David authored
This benchmark measure cases where both side has missing changed. pypy and mozilla-try has partial variant for it.
-
- May 19, 2019
-
-
Pierre-Yves David authored
Otherwise, we can modify an inherited list, affecting all other benchmark.
-
- Apr 28, 2019
-
-
Pierre-Yves David authored
This one is dedicated to tracking the time taken for two identical repository to realise they are identical. We take the addition of a new test as an opportunity to give it a proper name to this test.
-
Pierre-Yves David authored
The existing discovery test are now using the new roles information. To keep the compatibility witht he older class structure. We are using the `benchmark_name` feature to keep the same name. We'll probably want to use the very same feature to rename all test later into something more sensible. However, as a side effect, this means we are dropping the "same" variant of the subset/super set test. So ASV will be confused by the params value change... <sigh>. Important note: for this discovery to work, benchmark now needs to be have an upgraded reference.
-
- Apr 27, 2019
-
-
Pierre-Yves David authored
benchmark test can now "easily" use the new role information. A `BaseExchangeTimeSuite` subclass can use the `role_action` and `role_subtype` to declare the role the class is using. Then decorate the class with `@setup_role` to make sure the parameters variants are properly set. Finally the appropriate data can we accessed through the `role_data` property.
-
Pierre-Yves David authored
We need this information to be available to the benchrepo code before we can use it.
-
- Apr 28, 2019
-
-
Pierre-Yves David authored
Now that the upgrade script write them one level lower, we read it at that level. For now, it is simple to keep compatibility with the older form. So we keep it.
-