- Sep 26, 2019
-
-
Pierre-Yves David authored
Not sure why this started to happened, but seems relatively harmless.
-
- Sep 16, 2019
-
-
Raphaël Gomès authored
-
- Sep 24, 2019
-
-
Pierre-Yves David authored
Let's try to move toward a new a better naming.
-
- 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.
-
- Sep 16, 2019
-
-
Raphaël Gomès authored
-
- Sep 13, 2019
-
-
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.
-
- Aug 09, 2019
-
-
Pierre-Yves David authored
We are warming more of the branchcache. So let's use them
-
- Aug 06, 2019
-
-
Raphaël Gomès authored
-
Raphaël Gomès authored
Forgetting to use $PYTHON and just calling the script as an executable will make it use the system version of python instead of the one running the tests, which has very little chance of a) being the right version and b) having the right packages installed.
-
- May 17, 2019
-
-
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.
-
- May 15, 2019
-
-
Pierre-Yves David authored
-
Pierre-Yves David authored
This will eventually replace the makefile to setup repository
-
- 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
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.
-
- 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
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
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
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.
-
- Mar 30, 2019
-
-
Pierre-Yves David authored
-
- Apr 24, 2019
-
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
- Apr 06, 2019
-
-
Raphaël Gomès authored
This change was forgotten in 33ba3b5df38e during the draft phase.
-
- Apr 05, 2019
-
-
Raphaël Gomès authored
Most failure cases have to be covered basically end-to-end, so we might as well test the entire script. Moreover, failures would be easy to pinpoint since we are testing a single condition every time.
-
Raphaël Gomès authored
This unit test is here to make sure the base cases are covered and most of the actual logic (that it, not opening files and fetching data) is correct.
-
Raphaël Gomès authored
Pytest is the best python test runner in 2019, so it makes sense for us to use it for testing our own scripts. Since its test discovery relies on python modules (even in Python 3), this change adds the required __init__.py files in the folder structure. A minimal pytest.ini config file was added with usual parameters.
-
Boris Feld authored
-
Boris Feld authored
We have the times in the scheduler logs
-
Boris Feld authored
-
Boris Feld authored
Mercurial core commit d7e751ec679e introduced a new format variant named `compression-level` which updates all repo hashes.
-
- Mar 28, 2019
-
-
Boris Feld authored
-
- Mar 27, 2019
-
-
Boris Feld authored
This way we can detect bad file names
-