- May 24, 2019
-
-
Pierre-Yves David authored
-
- May 21, 2019
-
-
Raphaël Gomès authored
-
- May 18, 2019
-
-
Pierre-Yves David authored
If the `local.repos` file is present, it will be read instead of the `default.repos` file. The file itself is not tracked by version control, it is... local
-
- 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
-
Pierre-Yves David authored
I started seeing benchmark failing because `hg debugupdatecache` covers more data in some core changesets (so taking extra time to warm some cold cache). Instead we perform an extensive cache warming in the preparation steps. Once the cache are warm the `hg debugupdatecache` run are "fast". See inline documentation for details. We also introduce a way to skip this step as it might be slow.
-
- May 19, 2019
-
-
Pierre-Yves David authored
Since 481259af4bdf the `debugupdatecache` command also warming the `hgtagsfnodes` cache too. We update the test to expect this file.
-
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
-
Pierre-Yves David authored
There is some delay with the mozilla-try one. We push the other one in the mean-time.
-
Pierre-Yves David authored
strictly speaking, I could have update the partials variants keeping the same identifier. However I got lazy and the whole things is long enough to generate.
-
- 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.
-
- May 16, 2019
-
-
Pierre-Yves David authored
-
- May 15, 2019
-
-
Pierre-Yves David authored
-
Pierre-Yves David authored
One more step toward replacing the makefile.
-
Pierre-Yves David authored
This will eventually replace the makefile to setup repository
-
- May 07, 2019
-
-
Pierre-Yves David authored
There have been various behavior and format change after a5e03453eae8. Tagging it will help us to move back to older version if necessary.
-
- Apr 28, 2019
-
-
Pierre-Yves David authored
I fear that the lack of the "same" params value invalidate previous result file that has this value. So I am adding it again. However I am not sure I got that right, that this is in an independent changeset easy to be dropped.
-
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
We are introduce new important configuration data, we should make sure the upgrade makes it available.
-
Pierre-Yves David authored
The roles are important we should include them in order to be able to use them.
-
Pierre-Yves David authored
The goal of this section is to provide a more flexible way to specify target of exchange benchmark. We start small and will add more information later. In the same way, the code to actually use it will land in later changesets.
-
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
The script can now be used to update the partial-sets information in the `.benchrepo` of the reference. This will prove useful as we introduce more partial variant (current target, the discovery test). note: the script is adding the data at the root level, so not the level the code currently expect. See next changeset for a fix.
-
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.
-
- Apr 28, 2019
-
-
Pierre-Yves David authored
Before this change, running upgrade-reference could change the repository-prefix when new version were adding new repository format key. This change is not necessary (see inline comment) and has various anoying side effect (eg: requires a upload/download unchanged file again).
-
Pierre-Yves David authored
We'll add more update to these data sooner. We move the initialization in an independent commit for clarity.
-
- Apr 27, 2019
-
-
Pierre-Yves David authored
Explicitly detecting this older format will help use do have improve behavior when upgrading a reference repository that already have a "repo-prefix" entry.
-
- Apr 28, 2019
-
-
Pierre-Yves David authored
This test will come handy as we modify the script more.
-
Pierre-Yves David authored
That entry is an implementation details, best to no longer rely on it.
-
- Apr 27, 2019
-
-
Pierre-Yves David authored
This carries the meaning better. For now we only renamed things in the code.
-
Pierre-Yves David authored
Small refactoring to clarify the code.
-
Pierre-Yves David authored
Having both `update-reference-config` and `update-benchrepo` is confusing. So we rename `update-benchrepo`. `update` is changed to `upgrade` to clarify that this is meant to move from an older version to a newer one. And `benchrepo` is changed to `reference`, the fact it touches `benchrepo` is mostly an implementation details, the main argument is a `*-reference.tar` file.
-
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.
-