Optimise file-lock retry options

[GiDW]

When processes with testcontainers are running in parallel they become very slow to start because of the file-lock retry strategy in testcontainers.

proper-filelock uses node-retry (repo) and exposes options to configure node-retry behavior. The current option is { retries: { forever: true } }. This leaves the rest on defaults (factor 2, minTimeout 1000, maxTimeout infinity).

Set file-lock retry options to retry faster and more frequently, avoiding timeouts that become too long.

{
  retries: {
    forever: true,
    factor: 1,
    minTimeout: 500,
    maxTimeout: 3000,
    randomize: true
  }
}

[netlify]

✅ Deploy Preview for testcontainers-node ready!

Name	Link
🔨 Latest commit	7f10747
🔍 Latest deploy log	https://app.netlify.com/sites/testcontainers-node/deploys/677e8ab52cdd340008010b0d
😎 Deploy Preview	https://deploy-preview-890--testcontainers-node.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[GiDW]

@cristianrgreco Could you retry this run? 🙏
Test failed on installing dependencies due to a network error. Seems unrelated to the actual change.

[GiDW]

@cristianrgreco For the failing test on modules/weaviate. This test fails for me locally on main as well. The only way I can make this test pass is by waiting after const container = await new WeaviateContainer().start();. Is this a known flaky test?

[cristianrgreco]

@GiDW I don't see any difference in test times from my side, so if for your case this is a big help them I'm happy to merge it. Adding some randomness makes sense IMO because otherwise the processes will check for locks at the same time. Happy to merge if you are.

[GiDW]

@cristianrgreco Yes, this helps my case. If you are willing to merge it, please do 🙂