ci(jest-changed-files): enable mercurial related test on CI

[mrazauskas]

Summary

Split from #12322

One mercurial related test is skipped on CI long time ago, but it works on GitHub Actions. It makes sense to enable it.

Also there is another hg test which is sometimes failing on CI possibly due to flakiness (some timeout, race condition or so). Seemed that adding jest.retryTimes is making that test pass.

Test plan

So here is the plan. First I am simply enabling the skipped test. Will try to force-push few times, if there is flakiness I will add jest.retryTimes and will force-push few times to restart CI again. This way we can check if jest.retryTimes is really necessary.

[SimenB]

Awesome, thanks for taking the time to dig into this @mrazauskas! Flaky CI has been annoying for a long time

[codecov-commenter]

Codecov Report

Merging #12327 (b76d4e4) into main (201901f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main   #12327   +/-   ##
=======================================
  Coverage   67.25%   67.25%           
=======================================
  Files         330      330           
  Lines       17354    17354           
  Branches     5073     5073           
=======================================
  Hits        11671    11671           
  Misses       5651     5651           
  Partials       32       32           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 201901f...b76d4e4. Read the comment docs.

[SimenB]

Is it passing every time now? 😅

[mrazauskas]

Indeed. Runs with no issues. Perhaps let’s leave it for few of days and then I will force-push again.

[SimenB]

This specific one is not running, so it's not a flaky one. I'll land this, but understanding why other tests are failing sporadically would be nice...

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.