Headless run dumps heaps of GL errors in the terminal #4288
Labels
Comments
|
Yes, I saw this yesterday too. I thought this may have been introduced in 3.3.1, but I see you're using 3.3.0.
Is easy to reproduce on my end, I'm just running Are your errors also printing after the test results print? Towards the end before video recording? |
|
Is the |
|
@jennifer-shehane In a run with video recording mostly between the results and before the video recording yes but I also found this line at the top of a spec: In a run without video recording a larger dump block appeared also on in this position. I also tried downgrading to 3.2.0 to see if it was there also but that doesn't seem to work. The runner reports it's still using 3.3.1. |
|
Looks like @brian-mann added this env var indeed: https://github.com/cypress-io/cypress/blame/4521cdcc87414def652fb622942d2ab0c2bc4db6/cli/lib/tasks/verify.js#L81 |
|
@verheyenkoen Yeah, but we released a 3.3.1 version to fix this. 🤔 #4281 |
|
I'm having the same issue with 3.3.0 and 3.3.1 on headless mode. Downgrading to 3.2.0 solved the issue. |
|
I have the same issue. with both version. Sometimes there is the error and sometimes not. Iam using nuxt with crossenv and a node express js server. |
|
I've been seeing this with 3.3.1, and this particular instance of the warning might hint at a cause: It looks like resources related to the headless browser's GPU-accelerated rendering are being destroyed, and then something rendering-related is happening. Maybe there's an ordering or concurrency issue between Cypress' before-unload hooks, etc, and its teardown of the embedded-viewport, shadowy-DOM-thingie in which the page is being tested? (I am not a web guy, obvs.) Corollary question: do we expect GPU acceleration to be used during headless builds using Electron? |
|
Same issue with both versions. Downgrading to |
|
I have this same bug on 3.3.1 which is frustrating because if I downgrade to 3.2.0 then I hit this bug |
|
I am having the same issues. I am using version 3.3.1. Please let me know if there is anything I need to add to this. Thanks! |
cypress-bot
bot
added
the
stage: ready for work
jennifer-shehane
added
type: unexpected behavior
|
This is likely not coming from electron debug logs - it's coming from the electron upgrade we did starting in |
|
We filter out a lot of garbage lines from electron, and likely need to add more ignored lines from the output. /cc @bkucera and @jennifer-shehane there is code in the CLI that ignores garbage output. |
|
I have this happen on every repo during The trick is to run a file with a failing test so that the logs show up during the screenshot processing. I also did see some instances where these logs showed up at the beginning of the spec file's run. Partial DEBUG logs where extra logging is happening Beginning of file logs Mac 10.13.6 |
|
Is there any way to get rid of them? Is there any way to get results from the tests that do not include these logs? |
|
We are trying to determine how and where they are printed so we filter them out. So far no progress on this issue.
…Sent from my iPhone
On Jul 2, 2019, at 19:11, sydneybarlow ***@***.***> wrote:
Is there any way to get rid of them? Is there any way to get results from the tests that do not include these logs?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I cannot locally reproduce this - but I can open a PR assuming this is coming from electron's @sydneybarlow if you want to get rid of them now you'd need to write your own script that spawns cypress as a child process and filter out the data that's being emitted from |
cypress-bot
bot
added
stage: work in progress
stage: needs review
cypress-bot
bot
added
stage: pending release
and removed
stage: needs review
|
The code for this is done in cypress-io/cypress#4644, but has yet to be released. |
|
Released in |
|
Hey team,
|
|
This issue will be closed to further comment as the exact issue here was resolved and tested. @sania-dsouza If you're experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current behavior:
Between my test results in the terminal I see heaps of these dumped lines. They look like errors from a GL library but can't really pin them to a specific component. It is quite annoying but it doesn't stop Cypress from working correctly.f
There's always multiple sections of dumps in the output (in between the runner output).
Desired behavior:
No errors 😀
Steps to reproduce: (app code and test code)
Seen this in all my projects recently. With any
cypress runcommand. Haven't seen this in the terminal when running the GUI.Versions
MacOS Mojave
iTerm2 3.2.9
OhMyZsh
Cypress 3.3.0
The text was updated successfully, but these errors were encountered: