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

chore: do not use a subshell hack when using XVFB #6884

Merged

Conversation

aslushnikov
Copy link
Contributor

This was originally introduced in 9caa61a.
However, we no longer save process STDERR.

# XVFB-RUN merges both STDOUT and STDERR, whereas we need only STDERR
# Wrap `npm run` in a subshell to redirect STDERR to file.
- run: xvfb-run --auto-servernum --server-args="-screen 0 1280x960x24" -- bash -c "npm run test -- --project=${{ matrix.browser }}"
- run: xvfb-run --auto-servernum --server-args="-screen 0 1280x960x24" -- npm run test -- --project=${{ matrix.browser }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I locally run the tests without --auto-servernum --server-args="-screen 0 1280x960x24 also in the Python repo we don't have it. Can we remove it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The --auto-servernum is a general good practice; this sets up isolated x displays for different commands. In our case we never have a second consumer for xvfb, but I'd still keep it.

The screen configuration was added at f0fcdc8 and I don't think anything has changed with that regard. I'd keep it as-is too.

This was originally introduced in 9caa61a.
However, we no longer save process STDERR.
@aslushnikov aslushnikov force-pushed the cleanup-xvfb-launching-on-gha branch from 5cf5b13 to 869b57d Compare June 3, 2021 22:07
@aslushnikov aslushnikov merged commit 401dcfd into microsoft:master Jun 3, 2021
@aslushnikov aslushnikov deleted the cleanup-xvfb-launching-on-gha branch June 3, 2021 22:28
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

Successfully merging this pull request may close these issues.

2 participants