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

Error: Command failed: xvfb-run --server-args="-screen 0 1280x720x24" #7984

Closed
ridginald opened this issue Aug 30, 2023 · 1 comment
Closed
Labels
TYPE: bug The described behavior is considered as wrong (bug).

Comments

@ridginald
Copy link

What is your Scenario?

Test runs in GitHub Actions should complete as normal - but quite often freeze, and fail. This happens with and without the testcafe-action. This behaviour seems to have started since the releases of 3.x.x and beyond

We've reduced concurrency, but still results in the same error/s

What is the Current behavior?

The error below occurs intermittently when running our Testcafe tests with GitHub Actions. There doesn't appear to be any set pattern, they can just fall over at any point during a test run with the error below.

Running headless doesn't resolve the issues - we've also experimented with and without the testcafe-action

This happens with our own self-hosted, as well as, GitHub hosted runners

node:child_process:935
throw err;
^

Error: Command failed: xvfb-run --server-args="-screen 0 1280x720x24" npx testcafe < our run commands >
at checkExecSyncError (node:child_process:861:11)
at execSync (node:child_process:932:15)
at Object. (/home/ubuntu/actions-runner/_work/_actions/ridginald/testcafe-action-customdr/v1.0.6/index.js:66:1)
at Module._compile (node:internal/modules/cjs/loader:1198:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1252:10)
at Module.load (node:internal/modules/cjs/loader:1076:32)
at Function.Module._load (node:internal/modules/cjs/loader:911:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:22:47 {
status: 4,
signal: null,
output: [ null, null, null ],
pid: 32680,
stdout: null,
stderr: null
}

What is the Expected behavior?

Test runs complete as normal - whether that be pass or fail

What is your public website URL? (or attach your complete example)

Our applicaiton runs on multiple websites, and we're unable to provide these publicly

What is your TestCafe test code?

We can't provide this publicly

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

  1. Run tests with GitHub Actions

TestCafe version

3.0.0, 3.1.0, 3.2.0, 3.3.0

Node.js version

18.7.0

Command-line arguments

chrome:headless tests/path/to/tests.js -q attemptLimit=2,successThreshold=1 --env=live --reporter spec:report.txt

Browser name(s) and version(s)

Chrome 116.0.5845.96, Firefox 116.0

Platform(s) and version(s)

Linux Ubuntu 20.04 + Ubuntu 22.04

Other

No response

@ridginald ridginald added the TYPE: bug The described behavior is considered as wrong (bug). label Aug 30, 2023
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Aug 30, 2023
@AlexKamaev
Copy link
Contributor

The issue can appear if xvfb is not installed in your self-hosted runner, so it's hardly a TestCafe issue. As for testcafe-action, that package is deprecated, so we cannot give any recommendations on this.

@AlexKamaev AlexKamaev closed this as not planned Won't fix, can't repro, duplicate, stale Aug 31, 2023
@need-response-app need-response-app bot removed the STATE: Need response An issue that requires a response or attention from the team. label Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

2 participants