-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Renderer CoreText warnings displaying when running cypress in Electron #7245
Comments
I can consistently reproduce this with this portion of a test. The first test triggers it, and running additional tests allows enough time for it to manifest. If I run the first test in isolation with an .only it ends before I see the error in the logs context('Past Years Top 10s', function() {
beforeEach(function() {
cy.visit('https://top100.winespectator.com/archives/')
})
it('Elements Appear', function() {
cy.get('.s-archive-item')
.should('be.visible')
.and('have.length', 6)
})
})
context('100 Values', function(){
beforeEach(function() {
cy.visit('https://top100.winespectator.com/values/')
})
it('Map appears, and can be clicked to expand', function() {
cy.get('.values-map-link')
.should('be.visible')
.click()
cy.get('.featherlight-content')
.should('be.visible')
.find('.featherlight-close')
.click()
cy.get('.featherlight-content')
.should('not.be.visible')
})
it('Header Buttons serve valid pages', function() {
cy.get('.values-menu')
.find('a')
.each(function(button) {
cy.validateHref(button)
})
})
}) |
Working back, it appears that this was introduced in 4.2.0 |
I am able to see the Renderer warnings, but am not able to reproduce the crashing with a SIGSEGV exit. Is the SIGSEGV crash consistent on each run? Because I'm not sure the crash is related to the Renderer warnings. I can see the warnings started appearing in 4.2.0 when running in Electron. Probably due to the Electron upgrade. You can run the tests passing |
I think this may have something to do with the app under test using |
The crash for me occurs later in the test run. As I continue to run more tests this error spams my log. It may be triggering some sort of leak. After a minute or so the process crashes. |
I encountered the same problem! |
The CoreText warnings started appearing on a fresh install (4.7.0) on the base todo mvc app. It does not have As mentioned it is only happening on electron ( |
For full verification I ran It does exist on page: https://top100.winespectator.com/archives/ But it doesn't exist in the app I am testing (which still gives the error when run on electron): |
This is not fixed in the upcoming Electron 9 upgrade. |
Reproducible example: it('Map appears, and can be clicked to expand', () => {
cy.visit('https://top100.winespectator.com/values/')
cy.get('.values-map-link')
.should('be.visible')
.click()
}) |
This is not fixed in Electron 10 upgrade, Cypress 5.5.0 |
FYI, the issue on our side was caused by using |
FWIW, this issue has affected nearly every application I test with Cypress, often triggered by a deeply-nested dependency that I don't have direct control over. Would be really great to be able to suppress these, as our test output is not very useful (getting thousands of these warnings printed per test run) |
FWIW - Same issue using
It renders just above the XML terminal output. As suggested by @starpit, I checked our |
You don't need |
Any status update regarding this topic? it's making the CLI output just useless with all the noise coming from this message |
This is not fixed in latest Electron (13.0.0-beta.7) either. |
I confirm the issue exists in Cypress 7.4.0 when running in headless mode with |
Still experiencing this in Cypress 8.3.0 The way I worked around it was by setting a custom |
I'm still experiencing this in 9.5.4 It doesn't affect tests, but it makes the console output so much harder to parse. |
Until this is fixed, I'm piping my CI output through
|
This is still present in 12.11.0. |
the issue still exists. |
I'm not able to recreate this behavior with this example in 12.13.0. Is this still hapenning? |
Current behavior:
During my test run my log started being filled with:
Eventually, Cypress crashed between tests, between the Screenshot and Video packaging steps:
Desired behavior:
Cypress executes test runs without crashing
Test code to reproduce
fwiw most of my tests were hitting
winespectator.com -- I had tests running on the home page here.
Versions
Platform: darwin (19.4.0)
Cypress Version: 4.5.0
The text was updated successfully, but these errors were encountered: