Since previously the Travis run was a no-op, and we're about to add support for a new stack (in the next PR), which would be good to be able to test properly.
The Cedar-14 runs have been marked as allow_failures, since Chrome currently fails to start due to:
error while loading shared libraries: libgbm.so.1
Fixing the buildpack on Cedar-14 is out of scope for this PR, plus the stack is EOL and no-one has opened a support ticket for broken of Cedar-14 support yet. I'm leaving the Cedar-14 entries in the matrix to (a) make the current state clearer, (b) make it easier for an external contributor to fix if desired.
edmorley
commented
4 years ago
Since previously the Travis run was a no-op, and we're about to add support for a new stack (in the next PR), which would be good to be able to test properly.
Uses an approach similar to that in: https://github.com/heroku/heroku-buildpack-ci-postgresql
The Cedar-14 runs have been marked as
allow_failures, since Chrome currently fails to start due to:error while loading shared libraries: libgbm.so.1Fixing the buildpack on Cedar-14 is out of scope for this PR, plus the stack is EOL and no-one has opened a support ticket for broken of Cedar-14 support yet. I'm leaving the Cedar-14 entries in the matrix to (a) make the current state clearer, (b) make it easier for an external contributor to fix if desired.
Refs W-7502526.