Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TestCafe v1.7.0 specific issue - 'Error: ESPIPE: invalid seek, read' error thrown #4528

Closed
sijosyn opened this issue Nov 27, 2019 · 5 comments
Labels
FREQUENCY: level 1 OS: Mac STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).

Comments

@sijosyn
Copy link

sijosyn commented Nov 27, 2019

What is your Test Scenario?

With Node v8.11.1, I get 'Error: ESPIPE: invalid seek, read' error when running TestCafe example test.

With Node v10.16.3 test runs fine. Seems like a regression in TestCafe v1.7.0. See screenshot.

What is the Current behavior?

With Node v8.11.1, I get 'Error: ESPIPE: invalid seek, read' error when running TestCafe example test.

What is the Expected behavior?

With Node v10.16.3 test runs fine.

What is your web application and your TestCafe test code?

Your website URL (or attach your complete example):

Your complete test code (or attach your test files):
 import { Selector } from 'testcafe';

fixture `Getting Started`
	.page `http://devexpress.github.io/testcafe/example`;

test('My first test', async t => {
	// Test code
});
Your complete configuration file (if any):

Your complete test report:

see screenshot

Screenshots: Screen Shot 2019-11-27 at 11 22 44 AM

Steps to Reproduce:

  1. Go to my website ...
  2. Execute this command...
  3. See the error...

Your Environment details:

  • testcafe version: v1.7.0
  • node.js version: v8.11.1 . Note: Issue doesn't occur with v10.16.3
  • command-line arguments: testcafe chrome test.js
  • browser name and version: Chrome 78
  • platform and version: macOS 10.14.6
  • other:
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Nov 27, 2019
@alexey-lin
Copy link
Contributor

Hi @sijosyn,

I reproduced the problem. Thank you for bringing this issue to our attention. We will look into it.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Nov 28, 2019
@alexey-lin alexey-lin added FREQUENCY: level 1 OS: Mac STATE: Need research TYPE: bug The described behavior is considered as wrong (bug). labels Nov 28, 2019
@jiteshsojitra
Copy link

Thanks @alexey-lin for accepting the issue, #4530 looks same?

@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Nov 28, 2019
@alexey-lin
Copy link
Contributor

@jiteshsojitra These issues seem to be different because they are reproducible under different OS's and in different node.js versions. Still, they might have a common cause, of course.

@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Nov 28, 2019
@AndreyBelym
Copy link
Contributor

AndreyBelym commented Nov 29, 2019

This issue is caused by a bug in Node.js: nodejs/node#19240. You can update your Node.js to the latest 8.x version (8.16.1) or downgrade to a version that doesn't contain this bug (8.9.4).

Please note that we will discontinue supporting Node.js 8.x in January 2020 due to the Node.js end-of-life schedule: https://nodejs.org/en/about/releases/

@lock
Copy link

lock bot commented Dec 9, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Dec 9, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Dec 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FREQUENCY: level 1 OS: Mac STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

4 participants