Puppeteer 3.0.0 refuses to launch on CI #5661
Comments
5 tasks
|
@aduh95 it really looks like some new requirement - after installing libgbm in runtime everything works fine for me |
4 tasks
|
Same issue on these three auto-PRs from dependabot to update puppeteer - they all fail on Linux:
17 04 2020 04:22:16.927:ERROR [launcher]: Cannot start ChromeHeadless
/home/runner/work/api/api/src/API/node_modules/puppeteer/.local-chromium/linux-737027/chrome-linux/chrome: error while loading shared libraries: libgbm.so.1: cannot open shared object file: No such file or directory |
mathiasbynens
added a commit
that referenced
this issue
Apr 17, 2020
mathiasbynens
added a commit
that referenced
this issue
Apr 17, 2020
papandreou
added a commit
to papandreou/puppeteer-heroku-buildpack
that referenced
this issue
Apr 17, 2020
It's a new requirement of puppeteer 3: puppeteer/puppeteer#5661 Context: https://peakon.slack.com/archives/C72DKLYDD/p1587160894230300
papandreou
added a commit
to papandreou/puppeteer-heroku-buildpack
that referenced
this issue
Apr 17, 2020
It's a new requirement of puppeteer 3: puppeteer/puppeteer#5661
brentvatne
added a commit
to expo/expo
that referenced
this issue
Apr 22, 2020
brentvatne
added a commit
to expo/expo
that referenced
this issue
Apr 22, 2020
* Move guides out of versioned directory and set up redirects * Split up sidebar groups on the API reference side * Better version selector * Add Get Started section and some more cleanup * Improve version selector and top level header * Remove Overview from SDK reference * Remove unnecessary logs * Fix some internal links * Remove danger checks for now * Convert test-links script to js with puppeteer to follow redirects * Attempt to fix puppeteer running on docs * Add libgm-dev to puppeteer installation step puppeteer/puppeteer#5661
adunkman
added a commit
to ustaxcourt/ef-cms
that referenced
this issue
Jul 24, 2020
thanks, it really works. I spend days to find the solution but nothing works. but I tried your solution It really works. 🥳 |
mark-meyer
pushed a commit
to ustaxcourt/ef-cms
that referenced
this issue
Jul 30, 2020
* expecting correct mock call * serve non court-issued document from document viewer [skip ci] * renamed interactor * fixed test name * add tests [skip ci] * fix attachment button margin/indent * send out service emails * Show serve petition button on document viewer * checking that the service emails are sent * fixing where the email service is executed * tests for bad sequence paths * address feedback * route fixes * 5811: service bug fix * style fixes for attachment viewer * another css update * 5811: DOD - npm update, swagger, pa11y * 5811: refactoring - create COURT_ISSUED_DOCUMENT_TYPES constant * added test around serving court issued order for e filed case from message detail view * removing unused imports * Remove alternateBackLocation code * 4295 - the processed link was not previewing the correct document * Added test for serving paper filed document. Cleanup. * Button a11y * WIP testing service of court issued docs through document detail view * added test around service of court issued doc from document detail view * 5811: integration test for serving paper-filed petition from message detail * fixing unit test * no links should display for external users * added test around service of court issued document from doc detail ciew * added test around service of paper filed document from document detail view * moved log in step * 5811: integration test for serving e-filed petition from document view * making validation feedback easier to work with [skip ci] * increase test timeout * refactored filing docket entry sequence * added test coverage, and fixed sequence error found via adding unit tests * updated jsdoc * updated jsdoc * Update Reports.md * address my own PR comments * Updated test, packages * Fix deploy - downgrade aws-xray-sdk * fixed logging options that were changed for local debugging * Merge branch 'develop' into migration-mobbing * 5811: integration test fix * Implicit signedAt for notice document entity * Hide show edit signature button for notice * fixed in progress document, and qc complete logic in fileDocketEntrySequence * npm update * Remove edit signature button from message doc for notice * fixed failing integration test * added entity member for documentIdBeforeSigning setting value for documentIdBeforeSigning on saveSignedDocument * fixed integration tests and unit tests * fixed unit tests * Bug fix * Update notice integration tests to reflect signature updates * Rebuild entity docs * NPM update * all contacts need a contactId * Update package-lock.json * Update create cases script to reference new api urls * WIP - change remove/add signature flow, add documentIdBeforeSignature property to document * adding applicationContext to interactor calls updated package-lock * Signing/unsigned draft document new flow working, need to refresh pdf * Reload pdf after removing signature. Await async functions. * Support deploys at the `prod` branch. * add a representing array for contact IDs * [skip ci] Scaffold new Document signed property validation * update validation using isDraft on Document * some cleanup and tests wip [skip ci] * tests for remove signature action [skip ci] * Replace Edit Signature with Remove Signature * Adding tests * update jsdocs [skip ci] * Added tests * updating integration test to reflect new remove/add signature flow * updating test data * display names of parties being represented * 5811: bug fixes - address feedback * Husky pre-commit for entity docs * don't show in progress for unservable documents * show filing date on docket record for unservable documents * test fix * Rebuild entity docs * Edit uploaded PDF from Message flow * Do not clear draftState when signing a document * Rename var * updated messageDetailHelper * removed unnecessary method * fix linting errors * fixed comments that were reorganized during lint on save * add servedParties validation and documentation * 5812: integration tests * fixed seed data for draft order * allow email address to be saved * fixed conditional * Fixing tests * add tests * wiki updates * Don't include archived draft documents in draft documents list * Handle message document route with documentId * Fix create cases script setting ready for trial * docket number is no longer a link in the different case message boxes * using docketnumberiwthsuffix instead of just docketnumber * 5810: redesign judges dashboard * Handle route with documentId for draft docs * 650: remove case id from `serveCaseToIrs` code paths * Add some tests * add missing validation keys * replace mocks and interactor arguments * Remove console.log * removed attachments column * 5810: use case messages on judge/chambers dashboard * fix invalid UUIDs in tests! * Get case by docketNumber instead of caseId * add postinstall as suggested by kk * fix integration tests * Get case by docketNumber instead of caseId * let -> const; update test description * Use docketNumber instead of caseId Fixing tests * Use docketNumber instead of caseId * Update document list for doc viewer and drafts viewer * Revert use of table layout for doc viewer list * fixed bug with inProgress documents not routing to /review screen. Served documents route to new documents view screen. added updated tests * Bug fix when editing draft notice * removed .only * try pa11y with a large * smaller containers * make deploy step use a small * fixed sonarcloud error, added tests around navigation from different qc sections * reduce concurrency * assign less memory to JVM * boost minmum memory * Bug fix: trial session planning report term * Bug fix: increase editState size * test fix * bump back up to xlarge for now * patch lodash on puppeteer runtime * bump concurrency back up * addressing PR comments * clean up different test file * Use CircleCI contexts for prod deploys. This enables switching AWS credentials for the docker image used as a machine executor. * Add libgbm-dev to CI image. puppeteer/puppeteer#5661 * Update CODE_REVIEW.md * fix test comment * fix test * Add iam:CreateServiceLinkedRole to CircleCI user. This is used the first time a custom domain is provisioned for API Gateway to grant permission for CircleCI to create a Cloudfront distribution in an AWS-owned account as described in AWS documentation: https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html#edge-optimized-custom-domain-names Co-authored-by: Rachael Parris <43251054+rachaelparris@users.noreply.github.com> Co-authored-by: klohman <klohman@flexion.us> Co-authored-by: Mrinalini <mrinalinisinha05@gmail.com> Co-authored-by: Kris Koskelin <kkoskelin@flexion.us> Co-authored-by: Cody Seibert <cseibert@flexion.us> Co-authored-by: Matt Hopson <matthopson@gmail.com> Co-authored-by: Eric Sorenson <eric@sorenson.software> Co-authored-by: Cody Seibert <cseibert113@gmail.com> Co-authored-by: Eric Sorenson <esorenson@flexion.us> Co-authored-by: Matt <mhopson@flexion.us> Co-authored-by: Rachel Schneiderman <rschneiderman@flexion.us> Co-authored-by: Joseph Sutton <jsutton@flexion.us> Co-authored-by: Joseph Sutton <sutt0n@users.noreply.github.com> Co-authored-by: Andrew Dunkman <andrew.dunkman@gsa.gov> Co-authored-by: rachelschneiderman <rschneiderman379@gmail.com> Co-authored-by: Victoria McFadden <victoria.mcfadden@gsa.gov> Co-authored-by: Mike Marcotte <mike.marcotte@gmail.com>
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Tell us about your environment:
What steps will reproduce the problem?
puppeteer.launch()What is the expected result?
The browser should launch headlessly.
What happens instead?
I didn't find
libgbmlisted on the Troubleshooting page, it's probably a requirement quite recent because I didn't have the issue on Puppeteer 2.x.The text was updated successfully, but these errors were encountered: