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

adjust gitpod settings to be able to run jest tests in gitpod #1798

Merged
merged 3 commits into from
Jan 25, 2021

Conversation

jywarren
Copy link
Member

Fixes #0000 (<=== Replace 0000 with the Issue Number)

Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!

  • tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR -- or run tests locally with npm run test-all
  • code is in uniquely-named feature branch and has no merge conflicts
  • PR is descriptively titled
  • ask @publiclab/is-reviewers for help, in a comment below
  • Insert-step functionality is working correct as expected.

We're happy to help you get this ready -- don't be afraid to ask for help, and don't be discouraged if your tests fail at first!

If tests do fail, click on the red X to learn why by reading the logs.

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software
Please make sure to get at least two reviews before asking for merging the PR as that would make the PR more reliable on our part
Thanks!

@jywarren jywarren requested a review from a team as a code owner January 25, 2021 16:06
@gitpod-io
Copy link

gitpod-io bot commented Jan 25, 2021

@jywarren jywarren changed the title add xvfb to gitpod dockerfile to run jest tests in gitpod adjust gitpod settings to be able to run jest tests in gitpod Jan 25, 2021
Copy link
Member

@daemon1024 daemon1024 left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -3,5 +3,61 @@ FROM gitpod/workspace-full
USER root
RUN sudo apt-get update && apt-get install -y apt-transport-https \
&& sudo apt-get install -y \
xserver-xorg-dev libxext-dev libxi-dev build-essential libxi-dev libglu1-mesa-dev libglew-dev pkg-config libglu1-mesa-dev freeglut3-dev mesa-common-dev \
xserver-xorg-dev \
Copy link
Member

Choose a reason for hiding this comment

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

We need so many? 🙀
Gitpod already takes a very long time to start...

Copy link
Member Author

Choose a reason for hiding this comment

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

the first time -- after that it should be able to re-use the prebuilt container. I got this list from docs here (sorry should have linked):

https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#chrome-headless-doesnt-launch-on-unix

if you find any we can skip, that'd be great, but it's pretty painstaking to try over and over! Thanks!

@jywarren jywarren merged commit e5ea6e5 into main Jan 25, 2021
jywarren added a commit to publiclab/PublicLab.Editor that referenced this pull request Jan 27, 2021
jywarren added a commit to publiclab/PublicLab.Editor that referenced this pull request Jan 27, 2021
* Try running tests in GitHub Actions

* Update tests.yml

* tweaks and switch to grunt-contrib-jasmine v2.0.0

* add prereqs for Chrome Headless

see publiclab/image-sequencer#1798

* jest tweaks

* running! only 3 failing tests

* getting closer

* fix jest tests

* Update Gruntfile.js
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.

3 participants