Skip to content
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

citgm.through2-v4.0.1 failing on multiple platforms #809

Closed
BethGriggs opened this issue Jun 29, 2020 · 1 comment · Fixed by #810
Closed

citgm.through2-v4.0.1 failing on multiple platforms #809

BethGriggs opened this issue Jun 29, 2020 · 1 comment · Fixed by #810

Comments

@BethGriggs
Copy link
Member

  • Node Version: multiple
  • CitGM Version: 7.0.0
  • Platform: multiple

through2 appears to be failing on many platforms across all release lines with the following error:

 /home/iojs/tmp/citgm_tmp/32c9f2d6-33d9-47a5-a794-ef0983c8a8de/through2/node_modules/puppeteer/.local-chromium/linux-722234/chrome-linux/chrome: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory
 TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md
     at onClose (/home/iojs/tmp/citgm_tmp/32c9f2d6-33d9-47a5-a794-ef0983c8a8de/through2/node_modules/puppeteer/lib/Launcher.js:750:14)
     at Interface.<anonymous> (/home/iojs/tmp/citgm_tmp/32c9f2d6-33d9-47a5-a794-ef0983c8a8de/through2/node_modules/puppeteer/lib/Launcher.js:739:50)
     at Interface.emit (events.js:326:22)
     at Interface.close (readline.js:424:8)
     at Socket.onend (readline.js:202:10)
     at Socket.emit (events.js:326:22)
     at endReadableNT (_stream_readable.js:1243:12)
     at processTicksAndRejections (internal/process/task_queues.js:80:21)

https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/2398/nodes=fedora-latest-x64/testReport/junit/(root)/citgm/through2_v4_0_1/

I've not dug in any further yet.

/cc @rvagg

@richardlau
Copy link
Member

I suspect it's linked to rvagg/through2@164d3f8 and we probably want to avoid the test:browser script for Node.js.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants