cypress crash during long test run with error thrown by plugin / IPC channel closed #1953
Comments
|
I know that's not a lot to go on, is there some debug logging or something I could collect by configuring my cypress run so I could have them exported as artifacts from my build? I'm unable to reproduce this issue locally, and haven't tried to run locally with the container myself yet. |
|
It seems like I'm using some incorrect command line options with the cypress command, specifically:
If I drop that from my command line args, cypress runs with Chrome as I'd expect. I'll update the issue accordingly after a few CI runs if it seems that this fixes the problem with me (and it's electron specific -- I'm having a ton of issues across the board using Cypress with Electron and CI in general). |
|
It looks like I also see this in the logs right before the above stack trace: |
|
You need to quote the https://on.cypress.io/command-line#cypress-run-spec-lt-spec-gt As per the IPC channel dying, the stack trace is actually quite helpful here since its Cypress emitting this. @chrisbreiding can you take a look? You can add a https://on.cypress.io/command-line#Debugging-commands DEBUG=cypress:* cypress run <...> |
|
👍 facing same issue |
jennifer-shehane
added
the
stage: awaiting response
|
Hey @yknx4, did you try to place quotes around the If yes, and you're still facing this issue, can you provide the debug logs and also provide the content of your |
jennifer-shehane
changed the title
|
@jennifer-shehane I'm not even using '--spec' arguments. Plugins files const browserify = require('@cypress/browserify-preprocessor')
const path = require('path')
module.exports = on => {
const options = {
browserifyOptions: {
extensions: ['.js', '.ts'],
plugin: [['tsify', { project: path.join(__dirname, 'tsconfig.json') }]]
}
}
on('file:preprocessor', browserify(options))
}I can give you a copy of the debug log given a more private channel, like email or IM, I don't want to have the log public on Github ~ |
|
@yknx4 Were you able to resolve your issue? If you still need, you can email us at [email protected] to send logs outside of GitHub. |
|
Unfortunately we have to close this issue due to inactivity. Please comment if there is new information to provide concerning the original issue and we can reopen. |
jennifer-shehane
removed
the
stage: awaiting response
|
@jennifer-shehane I was 12 hours too late! I'm seeing this issue too after converting my Cypress project to Typescript. I'll email the logs I have |
jennifer-shehane
added
the
type: duplicate
jennifer-shehane
removed
the
type: duplicate
|
Hey @ZoroQualityAutomata - after looking at your issue, it looks different from this one. |
|
I believe we're seeing something extremely similar to this and it's really hurting us in CI. It's intermittent - sometimes our full suite of E2E tests succeeds. However, quite often we'll have one test in the suite fail with: After which, all subsequent specs fail with: We're using Cypress 3.1.5 and our plugins file is as follows - neither of these have changed since things were working fine: |
|
I just encountered this issue with Cypress 5.6.0 after upgrading the cypress webpack preprocessor from 4.1.0 to 5.5.0, running in gitlab ci with Chrome 87. and all subsequent suites also fail. The whole run usually takes around 60 minutes, and has 480 tests. |
|
I've just faced the same issue on Cypress 7.5.0. Suite is running via Jenkins CI and I've never experienced such error |
|
Same here. Cypress 8.5.0. Docker. Chrome browser in headless mode. |
|
Hi, I am seeing the same issue with Cypress 8 and 8.4. And: More details about the test suite: We believe that the ERR_IPC_CHANNEL_CLOSED error is a symptom of a plugin crash and that |
|
Having the same issue. Can this be reopened? |
|
@jennifer-shehane can we reopen this thread? See my comment above |
|
@SophieDePaula with this change #19553 we will be doing a better job of surfacing errors that occur in plugin code. |
|
I am facing the same issue with cypress 9.6.0 on docker. |
Current behavior:
After updating to 3.0.1 (from 3.0.0), after running a fairly large test run of 50 specs (compiled with the ts plugin), I've started to encounter these errors about 2/3 of the way through the suite. Every test afterwards fails immediately with the below stack trace:
Desired behavior:
Steps to reproduce:
I'm not sure if it's specific to my suite -- I've tried on a repo of simple tests (in the 50 or some odd range), but I think it has more to do with the size or complexity of the tests. I'll have to do some work to get an example of the crash.
Versions
Cypress 3.0.1
CircleCI 2.0 Config
cypress/browsers:chrome65-ff57
using the cypress run --browser chrome option
The text was updated successfully, but these errors were encountered: