-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Cypress times out with "Error running plugin" at stacktrace plugins/preprocessor.js:66:18 "Symbol not found" #1968
Comments
For what its worth, I ran the tests headlessly and they all passed. Not really sure what could be going on here. I think I'm more so looking for input on what could possibly be wrong rather than a solution as this seems like something system specific which I'm not sure you guys can help me with, unfortunately. Hoping it triggers a thought in someone's head that may have some things for me to try. |
Downgrading to node v8.10.0 and rolling back my project dependency updates seems to have fixed this. I can close the issue, but before I do so, have you guys seen anything like this? |
What does your I believe you are importing something in there which is a native module which is not precompiled correctly for the node version that comes built into |
My plugins file: const webpack = require('@cypress/webpack-preprocessor');
const webpackConfig = require('../../config/webpack/config-common');
module.exports = (on, config) => {
// `on` is used to hook into various events Cypress emits
// `config` is the resolved Cypress config
on('file:preprocessor', webpack({
webpackOptions: webpackConfig
}));
}; config-common is my base webpack config that just uses path, webpack, and webpack-merge. The config(s) that get merged in (which is based on the npm event being run) contain nothing more than webpack, browser-sync-webpack-plugin, path, or uglifyjs-webpack-plugin. Do you think the issue is within the webpack-preprocessor? |
@chrisbreiding can you take a look at this? |
@reintroducing can you do That will tell us what is requiring it. |
@brian-mann result:
What is |
@reintroducing
|
@jennifer-shehane right on, my apologies, googly eyes from looking over logs. |
I ran into this issue today- in my case was coming from a If you've found yourself reading this issue, I'd suggest a quick check for
|
Is there any obvious fix for this issue? I have the same problem on Cypress 6 on a fresh install. "dependencies": {
"@angular/animations": "^9.1.13",
"@angular/cdk": "^9.2.4",
"@angular/common": "^9.1.13",
"@angular/compiler": "^9.1.13",
"@angular/core": "^9.1.13",
"@angular/forms": "^9.1.13",
"@angular/platform-browser": "^9.1.13",
"@angular/platform-browser-dynamic": "^9.1.13",
"@angular/router": "^9.1.13",
"bootstrap": "^4.5.3",
"ngx-bootstrap": "^6.2.0",
"rxjs": "~6.5.4",
"tslib": "^1.10.0",
"zone.js": "~0.10.2"
},
"devDependencies": {
"@angular-devkit/build-angular": "^0.901.13",
"@angular/cli": "^9.1.13",
"@angular/compiler-cli": "^9.1.13",
"@angular/language-service": "^9.1.13",
"@types/node": "^12.19.11",
"codelyzer": "^5.1.2",
"concurrently": "^5.3.0",
"cypress": "^6.2.0",
"start-server-and-test": "^1.11.6",
"ts-node": "~8.3.0",
"tslint": "~6.1.0",
"typescript": "~3.8.3"
} This is my cypress index.js /**
* @type {Cypress.PluginConfig}
*/
module.exports = (on, config) => {
// `on` is used to hook into various events Cypress emits
// `config` is the resolved Cypress config
} and cypress.json {
"baseUrl": "http://localhost:4201"
} This is the error message: Title: Error running plugin Message: The following error was thrown by a plugin. We stopped running your tests because a plugin crashed. Please check your plugins file ( Details:
Stack trace:
|
@AndreiCatalinN Your issue does not look related to the original issue. The original issue was about a You are seeing an error being thrown from you plugins file however. I'm not able to reproduce it from the information provided alone. Perhaps it has something to do with your tsconfig file also? Could you open a new issue with your reproducible example? Since this issue with the 'Symbol not found' error hasn't had activity in a while, we'll close the issue until we can confirm this is still happening. Please comment if there is new information to provide concerning the original issue and we'd be happy to reopen. |
i am facing the same issue, any solution found? @AndreiCatalinN |
Current behavior:
My tests were working fine two weeks or so ago. I've changed nothing except updated some dependencies in my project unrelated to Cypress to their latest versions. When I try to run my tests now, Canary opens but nothing appears and then eventually it times out and I see this in Cypress:
Looking at Terminal reveals this:
At that point, the only thing I can do is close Cypress to kill the process.
Desired behavior:
Everything works as expected and tests run.
Steps to reproduce:
Just running my tests :\ It happens for every test that I've written no matter whats in it. My assumption is that it has something to do with the environment but I can't seem to pinpoint whats going on.
Versions
Cypress: 3.0.1
node: 10.3.0
npm: 6.1.0
Canary 69
OSX 10.13.3
The text was updated successfully, but these errors were encountered: