While trying to stabilize output of the `test-remotefilelog-bgprefetch.t` test (https://phab.mercurial-scm.org/D5960), we detected that `debugwaitonrepack` is buggy. Here is how I reproduced it: python run-tests.py --runs-per-test=100 test-remotefilelog-bgprefetch.t I cannot reproduce the issue 100% of the time and it seems more flaky with a busy workstation.
My patch to try to stabilize the test file has landed and the test is more stable but is still failing from time to time (https://ci.octobus.net/job/MercurialPy2/327/console for example). From a discussion with Augie, it might be because of using exotic file-system (inside Docker) and maybe linked to flock usage.
Bug was set to UNCONFIRMED for 30 days, bumping
Bug was set to UNCONFIRMED for 31 days, bumping
The CI job now run on a normal VM running Debian 9.9 on an ext4 partition so it might not be related to the file-system in the end,
We no longer use flock. Boris, should we sloce this bug ?
Fixed by https://mercurial-scm.org/repo/hg/rev/ee0959e7d435 Pierre-Yves David <pierre-yves.david@octobus.net> remotefilelog-test: glob some flaky output line (issue6083) The two following lines are flaky underload, yet the final result is correct. The command involves background pre-check of output, these are not stable probably because they run in parallel in multiple process. I spent a couple of hours trying to understand the pattern and gave up. The documented intend of these tests is safely guaranteed by checking the cache content after the command. If it become useful to start testing precise internal details of the, they will have to be tested in a more appropriate framework than `.t` tests. Differential Revision: https://phab.mercurial-scm.org/D8102 (please test the fix)
Bug was set to TESTING for 7 days, resolving