update yaml #159
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Main workflow | |
| on: [push] | |
| jobs: | |
| run: | |
| name: Run | |
| runs-on: ${{ matrix.operating-system }} | |
| strategy: | |
| matrix: | |
| operating-system: [ubuntu-latest] | |
| steps: | |
| - uses: actions/checkout@master | |
| - name: Set Node.js 18.x | |
| uses: actions/setup-node@master | |
| with: | |
| node-version: 18.x | |
| - name: Disable AppArmor | |
| # Ubuntu >= 23 has AppArmor enabled by default, which breaks Puppeteer. | |
| # See https://github.com/puppeteer/puppeteer/issues/12818 "No usable sandbox!" | |
| # this is taken from the solution used in Puppeteer's own CI: https://github.com/puppeteer/puppeteer/pull/13196 | |
| # The alternative is to pin Ubuntu 22 or to use aa-exec to disable AppArmor for commands that need Puppeteer. | |
| # This is also suggested by Chromium https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md | |
| run: echo 0 | sudo tee /proc/sys/kernel/apparmor_restrict_unprivileged_userns | |
| shell: bash | |
| - name: npm install | |
| run: npm install | |
| - name: npm test | |
| run: npm test |