🔧 Gitpod to use the Docker image

[trallard]

Last step following from #4 - this should make it so that we use the prebuilt image and enables pre-builds for Gitpod

[trallard]

Ran the tests again and now it all works as expected 🎉 - @gabalafou or @tonyfast can you do a sanity check and merge? 🙏🏽

[gabalafou]

So I'm still seeing an issue when I do the following:

1. Open PR #5 in Gitpod
2. cd testing/jupyterlab
3. yarn test

The issue is that error message we saw before: that we need to run npx playwright install.

Here's a screenshot:

[gabalafou]

Follow up. If I run npx playwright install then yarn test, it works as I expect: Playwright runs the tests and generates a WCAG violation report for the tests run.

[trallard]

Are you opening Gitpod from master or from this branch? @gabalafou

Not sure if you will be able to access my logs https://gitpod.io/projects/accessibility/83f468d6-33ef-4dfc-9a5c-c092cfe67913 but you can see the pre-build is completing all these installs

[gabalafou]

I was opening from this branch/PR by going to this URL: https://gitpod.io/#https://github.com/Quansight-Labs/accessibility/pull/5

[gabalafou]

When I go to the logs url you pasted, all I see is one line:

operation not permitted: missing get permission on workspace

[trallard]

I figured...

[gabalafou]

¯\_(ツ)_/¯

It makes no sense. All I can tell you is that when I was playing around with Gitpod, the only way I could get this to work is if I put npx playwright install under command in the .gitpod.yml file. I don't know enough about what's going on under the hood to understand why running that command in init doesn't "stick."

[gabalafou]

Okay, here's a clue from my command log (pasted below). See how there's nothing in ~/.cache? But after I run npx playwright install the browser folders are put in .cache. My first thought was that maybe Gitpod nukes the .cache folder between the init commands and the point at which it puts you in the shell. But the fact that yarn exists in .cache suggests to me that's not it. Maybe it has something to do with who Gitpod thinks the user is (and hence the home directory path to .cache) when it runs init?

(a11y-tests) gitpod > /workspace/accessibility $ cd testing/jupyterlab/
(a11y-tests) gitpod > /workspace/accessibility/testing/jupyterlab $ ls ~/.cache
yarn
(a11y-tests) gitpod > /workspace/accessibility/testing/jupyterlab $ npx playwright install
Downloading Playwright build of chromium v1000 - 132.8 Mb [====================] 100% 0.0s 
Playwright build of chromium v1000 downloaded to /home/gitpod/.cache/ms-playwright/chromium-1000
Downloading Playwright build of ffmpeg v1007 - 2.6 Mb [====================] 100% 0.0s 
Playwright build of ffmpeg v1007 downloaded to /home/gitpod/.cache/ms-playwright/ffmpeg-1007
Downloading Playwright build of firefox v1322 - 76.3 Mb [====================] 100% 0.0s 
Playwright build of firefox v1322 downloaded to /home/gitpod/.cache/ms-playwright/firefox-1322
Downloading Playwright build of webkit v1630 - 86.6 Mb [====================] 100% 0.0s 
Playwright build of webkit v1630 downloaded to /home/gitpod/.cache/ms-playwright/webkit-1630
(a11y-tests) gitpod > /workspace/accessibility/testing/jupyterlab $ ls ~/.cache
ms-playwright  yarn

[trallard]

Maybe it has something to do with who Gitpod thinks the user is (and hence the home directory path to .cache) when it runs init?

It should not matter unless you are jumping on an already made workspace anywho will merge for now and can improve later - esp if we are merging the other doit branch