CI failing due to puppeteer@3.0.0

[fcollonval]

Since 2 days, the check browser test is failing due to the usage of puppeteer@3.0.0.

An issue is opened there: puppeteer/puppeteer#5674

[jtpio]

Thanks @fcollonval for opening the issue.

Do you think it would be worth applying a fix by pinning puppeteer to ^2 in the browser check?

[blink1073]

I'm hesitant to make a new set of releases for this, at the very least I don't have the bandwidth until Wednesday.

[jtpio]

As mentioned in puppeteer/puppeteer#5674, one possible workaround for now is to add the following step to the GitHub Actions workflow:

    - name: TMP fix - install libgbm1
      run: sudo apt install -y libgbm1

[fcollonval]

As per actions/runner-images#732, the upstream Ubuntu image will be updated to add that new dependency. Should we update the repo with the temporary fix or just wait for an update of the image?

[blink1073]

I released JupyterLab 2.1.1 with a pinned version of puppeteer. I tried to run our failing CI build, but it is currently still picking up 2.1.0 in the install step.

[fcollonval]

Thanks @blink1073 !!
The CI is now passing.