DevExpress / testcafe

A Node.js tool to automate end-to-end web testing.
https://testcafe.io
MIT License
9.82k stars 672 forks source link

Getting sometime "Uncaught exception: Error: write EOF" OR "Uncaught exception: Error: write EPIPE" when I run testcafe testcase over teamcity build. #7426

Closed rupesh1395 closed 1 year ago

rupesh1395 commented 1 year ago

What is your Scenario?

Simple write the tetscafe tetscase in typescript. Put in Suite and run the suite 7 to 8 time in TeamCity. I used -u also. It will give below error Test Failed Uncaught exception: Error: write EPIPE

What is the Current behavior?

Getting this error Test Failed Uncaught exception: Error: write EPIPE at afterWriteDispatched (internal/stream_base_commons.js:156:25) at writeGeneric (internal/stream_base_commons.js:147:3) at Socket._writeGeneric (net.js:787:11) at Socket._write (net.js:799:8) at doWrite (internal/streams/writable.js:377:12) at clearBuffer (internal/streams/writable.js:529:7) at onwrite (internal/streams/writable.js:430:7) at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:103:10) at WriteWrap.callbackTrampoline (internal/async_hooks.js:131:17) Browser: Chrome 108.0.0.0 / Windows 10

What is the Expected behavior?

Testcase should be pass or fail .Uncaught exception error should not return

What is your public website URL? (or attach your complete example)

You can run on any test website.

What is your TestCafe test code?

function testViewTest(): any { test('View Test', async(t) => { await testcom.login(t); await t .resizeWindow(1600, 1100); await MainPage.pagenavigate(); await t .expect(testpage.getFileNameTableCell(test).exists).notOk() .expect(testpage.getFileNameTableCell(test).exists).notOk() .expect(testpage.getFileNameTableCell(test).exists).notOk();

  hhshs.forEach(async header => {
        await t
            .expect(hshs.exists).ok();
    });
    t.ctx.passed = true;
});

}

Your complete configuration file

"skipJsErrors": true, "pageRequestTimeout": 60000, "browserInitTimeout": 600000

Your complete test report

No response

Screenshots

image image

Steps to Reproduce

1.Simple write any testcafe test case in typescript language. Put the testcase in suite

  1. Run suite through TeamCity build
  2. See the error in build log

TestCafe version

2.0.0

Node.js version

v14.18.1

Command-line arguments

runner .src(tests) .browsers('chrome').reporter('teamcity')

Browser name(s) and version(s)

Chrome 108

Platform(s) and version(s)

Windows

Other

No response

github-actions[bot] commented 1 year ago

Thank you for submitting this issue. We would love to assist you and diagnose it. However, we need a simple sample that we can easily run on our side in order to replicate the issue and research its cause. Without a sample, we are not able to figure out what's going on and why this issue occurs. Refer to this article to create the best example: How To: Create a Minimal Working Example When You Submit an Issue. We look forward to your response.

rupesh1395 commented 1 year ago

Hey it is simple to replicate this issue . Write simple testcafe test case and put in a one suite file and run through teamcity 5 to6 times you will get uncaught exception error

AlexKamaev commented 1 year ago

It's a very complex usage scenario, and it's not clear if it's related to TestCafe. Please simplify your usage scenario to reproduce the issue on a local machine. Please also update your nodejs version. In addition, the testcafe-reporter-teamcity module is marked as deprecated.

github-actions[bot] commented 1 year ago

This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.

rupesh1395 commented 1 year ago

I am not getting this issue in current version(Testcafe 2.1.0). Thank you