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

xvfb-run and electron suddenly stopped working properly #5176

Open
romaingweb opened this issue Nov 20, 2020 · 1 comment
Open

xvfb-run and electron suddenly stopped working properly #5176

romaingweb opened this issue Nov 20, 2020 · 1 comment

Comments

@romaingweb
Copy link

Description of your issue:

Part of our test suite is using an electron app to run Cucumber-JS acceptance tests. (cucumber-electron)
To make it work, we use xvfb to simulate the display required by electron to open a window. That was working fine until recently where we tried to upgrade electron to a more recent version. The actual build for the update went well, but all subsequent builds failed. We tried to rebuild using SSH to figure out what is going on, but no luck so far. We also rebuilt without the cache, just in case there were dependency issues between electron and cucumber-js.

The strangest part is if we're rebuilding an older build that was passing, it also fails with the same result: test results failed to be outputted from the cucumber-electron suite.

The previously passing build: https://app.shippable.com/github/hiptest/cucumberstudio/runs/13024/summary/console
The new failing build for the same code revision: https://app.shippable.com/github/hiptest/cucumberstudio/runs/13032/summary/console

It would be really helpful if you had any insights for us to try and fix this strange behavior.

We are the makers of Cucumber-js and Cucumber-electron, so we can also work at the level to try different things if that helps.

@romaingweb romaingweb changed the title xfvb-run and electron suddenly stopped working properly xvfb-run and electron suddenly stopped working properly Nov 20, 2020
@a-murphy
Copy link

a-murphy commented Dec 1, 2020

Errors that suddenly appear are typically the result of installing a different version of a dependency. In some cases, it can even be that although the immediate dependency has a version specified, a dependency of that dependency does not and a different version starts to be installed. Perhaps given that your first build succeeded it could be something installed by your scripts after the point at which it later failed? Unfortunately, I was not able to find any clues in the logs as to what that might be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants