My ember.js app’s tests do not run at all with the image node:10-browsers.
Fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown element “blank”
Here’s the error log
message: >
Error: Browser exited unexpectedly
Non-zero exit code: null
Stderr:
Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
DevTools listening on ws://127.0.0.1:34662/devtools/browser/60da2d32-5fb9-40f5-a9af-ebaa3db48eca
[0315/160159.843107:FATAL:gpu_data_manager_impl_private.cc(892)] The display compositor is frequently crashing. Goodbye.
Failed to generate minidump.
Log: |
{ type: 'error', text: 'Error: Browser exited unexpectedly' }
{ type: 'error', text: 'Non-zero exit code: null' }
{ type: 'error',
text:
'Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"\n\nDevTools listening on ws://127.0.0.1:34662/devtools/browser/60da2d32-5fb9-40f5-a9af-ebaa3db48eca\n[0315/160159.843107:FATAL:gpu_data_manager_impl_private.cc(892)] The display compositor is frequently crashing. Goodbye.\nFailed to generate minidump.' }
I’m getting this too. It looks like the image changed some time in the last few days. Builds worked fine on Wednesday but are broken today with this error.
The circleci/node:10-browsers image isn’t the same thing as circleci/node:10.14-browsers. Currently it points to circleci/node:10.15.3-browsers.
Does your app work with that image? If it does, then something might be wrong with the 10-browsers tag. If it doesn’t, a change in Node or the upstream Docker image is what’s causing this.
Most of the 10.x.y images have not changed in months. It’s possible the error is the result of a change in an upstream dependency included in the image, but it’s hard to say.
@FelicianoTech’s question is a good one. You can also find old jobs that were successful and pin the sha256 of the image that was used in those jobs in your config.yml file.
If you can definitively point this issue to something in our images code, please open an issue here:
Hmm, I played around with this a bit (since another project using the same image did build just fine), and apparently the reason was a different testem config.