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

With VS Code 1.49 Tests can no longer run on Linux #73

Closed
rchiodo opened this issue Sep 11, 2020 · 5 comments
Closed

With VS Code 1.49 Tests can no longer run on Linux #73

rchiodo opened this issue Sep 11, 2020 · 5 comments
Labels
info-needed Issue requires more information from poster

Comments

@rchiodo
Copy link

rchiodo commented Sep 11, 2020

We're getting this on all of our test runs:

[5304:0911/170659.592044:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye
@rchiodo
Copy link
Author

rchiodo commented Sep 11, 2020

I thought maybe adding --disable-gpu might fix the problem but it doesn't seem to work.

@rchiodo
Copy link
Author

rchiodo commented Sep 11, 2020

Here's our args to run tests:

    runTests({
        extensionDevelopmentPath: extensionDevelopmentPath,
        extensionTestsPath: path.join(EXTENSION_ROOT_DIR_FOR_TESTS, 'out', 'test', 'index'),
        launchArgs: ['--disable-gpu', '--disable-extensions', workspacePath]
            .concat(channel === 'insiders' ? ['--enable-proposed-api'] : [])
            .concat(['--timeout', '5000']),
        version: channel,
        extensionTestsEnv: { ...process.env, UITEST_DISABLE_INSIDERS: '1' }
    }).catch((ex) => {
        console.error('End Standard tests (with errors)', ex);
        process.exit(1);
    });

@rchiodo
Copy link
Author

rchiodo commented Sep 11, 2020

Note: This worked fine with 1.48 and earlier.

@bpasero
Copy link
Member

bpasero commented Sep 30, 2020

@rchiodo that sounds like a CI configuration problem to me, not a VSCode issue. You can refer to https://github.com/bpasero/test-ts-pipeline for an example for running the tests on Windows, macOS and Linux in the GH CI.

@bpasero bpasero added the info-needed Issue requires more information from poster label Sep 30, 2020
@rchiodo
Copy link
Author

rchiodo commented Sep 30, 2020

It was ubuntu 16. We had to upgrade to Ubuntu 20 and the problem went away. Did VS code (electron) stop supporting Ubuntu 16?

@bpasero bpasero closed this as completed Oct 1, 2020
heaths added a commit to heaths/vscode-guid that referenced this issue Jan 5, 2021
vscode-test appears broken on Ubuntu 16.04.

See microsoft/vscode-test#73
heaths added a commit to heaths/vscode-guid that referenced this issue Jan 16, 2021
* Use @actions/core for setting env vars

* Resolve vulnerabilities

Resolves @dependabot PRs #34, #35

* Workflow to use Node 10.x

* Use ubuntu-latest

vscode-test appears broken on Ubuntu 16.04.

See microsoft/vscode-test#73

* Run ubuntu-latest tests under xvfb-run

* Add required check for branch policies

Allows matrix build job to change without requiring reconfiguring branch policies with strategy-specific names.

Branch policy will instead depend on the new "check" job that depends on all build jobs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

2 participants