- Sep 23, 2019
-
-
Pierre-Yves David authored
This is very useful when a benchmark are recenty introduced but is compatible with a larger range of revision.
-
- 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.
-
- May 19, 2019
-
-
Pierre-Yves David authored
Before, not passing a filter_fn means the function will always return False
-
- Apr 27, 2019
-
-
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.
-
- Apr 27, 2019
-
-
Pierre-Yves David authored
Given the level of the "benchmark-variables", it seems more appropriate to have the partial-sets at the same level. We start with mentioning that in a comment and then we will see if we can do something about it.
-
Pierre-Yves David authored
This can't hurt and make things a bit clearer.
-
Pierre-Yves David authored
The fact we use a hash of anything is an implementation details. In most case, directly using "repo-prefix" is what one should do. We implement that in the parsing code.
-
Pierre-Yves David authored
This is the information this attribute is meant to carry. Using it make things more robust and clarify things.
-
Pierre-Yves David authored
The new name have been around for 1 years, let us stop hacking the old name back. This will requires people to reclone, however will come in a larger wagon that will requires people to reclone anyway.
-
- Apr 05, 2019
-
-
Boris Feld authored
-
- Apr 02, 2019
-
-
Raphaël Gomès authored
Some repositories don't have all the variants that are tried. Instead of getting a `KeyError`, we now just skip the impossible combinations.
-
- Mar 28, 2019
-
-
Raphaël Gomès authored
This decorator will be used to mark versions that do not work most of the time. So instead passing `compatible_with("not(revset)")` and a negative filter function, we can just specify the revset wherein the bench should not run and optionally further filter on test kwargs.
-
- Mar 05, 2019
-
-
Raphaël Gomès authored
Both benchmarks/ and scmperf_lib/ make use of PyYAML to load yaml files. This library has used an unsafe (i.e. can load yaml bombs, etc.) loader by default since its inception and has been urging people to move to `safe_load` instead. We could have still used `load` by switching to SafeLoader, but the refactor shrunk the code so much that it would not really be an improvement.
-
Raphaël Gomès authored
Strip variants can differ between repos and should not be hardcoded. This change uses the data from the .benchrepo file for each repo to pass to each corresponding test. We are new storing the entire repo prefix instead of only storing the hash, since it is just as unique, removing the need to recompute the prefix from the hash later in the code.
-
- Mar 04, 2019
-
-
Raphaël Gomès authored
This list used to be hardcoded, this change gathers the unique strip variants into a list from every .benchrepo file for use in the ASV test matrix.
-
- Mar 05, 2019
-
-
Boris Feld authored
As we know use kwargs in setup too, we need to change how we compute the repo_name.
-
- Feb 26, 2019
-
-
Boris Feld authored
This was it will be easier to identify which variants is defined by the repo and which ones are defined by the test itself.
-
- Feb 13, 2019
-
-
Raphael Gomes authored
Some of the performance methods in Mercurial are not defined at all points in the history. There might be times when they were not yet defined or broken, etc.. This decorator adds a way of telling asv that this method should be skipped for the hash being tested.
-
- Mar 04, 2019
-
-
Raphaël Gomès authored
We currently are limited in the way that tests can be run against the test data, which has to reside in the same folder. For reasons of flexibility and/or performance, one might need to change the filesystem path to the repositories being tested. This change introduces a new config variable "repodir" which must contain a valid path. While this path is ran through `os.path.abspath`, it is recommended to use an absolute path, since the working directory in this context is not garanteed to be stable.
-
- Feb 12, 2019
-
-
Raphael Gomes authored
-
- Jan 25, 2019
-
-
Boris Feld authored
-
- Nov 23, 2018
-
-
Pierre-Yves David authored
This will give benchmark access repository specific variables.
-
Pierre-Yves David authored
Now that we have yaml, the sky is the limit.
-
- Nov 07, 2018
-
-
Pierre-Yves David authored
That repository might constains obsmarkers. Enabling evolve prevent an annoying warning.
-
Pierre-Yves David authored
Some commands of the `perf` extensions returns multiple value. Running the command multiple time would be quite slow. We add a way to reuse data from the same run from multiple `track_xxx` method.
-
Pierre-Yves David authored
This makes it possible to handle `perf` command returning multiple value.
-
Pierre-Yves David authored
We split the part responsible for running the actual command from the part responsible for processing it. This will be useful to introduce a new method relying on json output instead of parsing textual output.
-
- Aug 30, 2018
-
-
Pierre-Yves David authored
We use the new options offered by upstream ASV. We use a 3 repeat minimum and 10 repeat max. Max time (before we give up on max repeat) is 60 seconds per variants.
-
- Jul 06, 2018
-
-
Philippe Pepiot authored
-
- Aug 13, 2018
-
-
Martijn Pieters authored
-