Tunnel never closes and test never stops running

[arvedjo]

Hi DevExpress,

after updating from testcafe-browser-provider-saucelabs 2.0.0 to 3.0.0 the tunnel never closes and the test runs until timeout. This is reproducible for the following test:

import { Selector } from "testcafe";

fixture`Fixture`.page("http://example.com");

test("test", async (t) => {
  await t.click("body").expect(Selector("h1").innerText).eql("Example Domain");
});

I am tried it an Windows and a Debian docker. I am running on Saucelabs European Server.

This is the run command:

npx testcafe saucelabs:safari .\test\basic_test\ExampleTest.js

This is the console log which stops and runs until saucelabs timeout:
`
Running tests in:

• Safari 16.6 / macOS 10.15.7
  (https://app.eu-central-1.saucelabs.com/tests/***********************)

Fixture
√ test
`
Thank you for your support.

[JoergHeinicke5005]

We are facing the same issue as well in several of our test suites.

[github-actions]

We appreciate you taking the time to share the information about this issue. We replicated it, and it is currently in our internal queue. Please note that the research may take time. We'll update this thread once we have news.

[arvedjo]

Hi,
are there any updates on the issue?
Thanks Arved

[github-actions]

No updates yet. Once we make more progress, we will leave a comment.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

[JoergHeinicke5005]

This ticket shouldn't get closed due to some automatic process, but rather taken care of. Multiple users are confirming the issue in their tests.

[arvedjo]

Agree, please fix it. Still testing with old release with many deprecated dependencies to keep tests running.

[github-actions]

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

[FlorinePola2022]

Hi! any update on this ? is this issue being out of date ?