-
Notifications
You must be signed in to change notification settings - Fork 210
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
Conversation
There was a problem hiding this 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 \ |
There was a problem hiding this comment.
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...
There was a problem hiding this comment.
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):
if you find any we can skip, that'd be great, but it's pretty painstaking to try over and over! Thanks!
* 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
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!
npm run test-all
@publiclab/is-reviewers
for help, in a comment belowIf 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!