Closed schneems closed 4 months ago
Running docker pull heroku/builder:22
locally to pick up the latest builder image (which includes Procfile CNB v3.0.0) should resolve the failures.
The reason running the libcnb-test
tests locally don't pick up this new version is because we intentionally use --pull-policy if-not-present
when libcnb-test
invokes pack build
, which means if the image exists locally a newer one isn't pulled to (a) reduce the chance of hitting Docker rate limits when running lots of tests, (b) to improve test performance.
This is obviously a trade-off, however, it's only in fairly rare circumstances that this will cause an issue (in this instance we intentionally made a breaking change in Procfile CNB which affects some lesser used scenarios + the start_container
tests in this repo happen to test those lesser used scenarios for completeness, though in reality it's not something many users will really hit.)
Also worth noting that using pack build
locally in its default config will cause an image pull too (since it defaults to --pull-policy always
), so over the long term the builder image on buildpack maintainers machines will stay up to date even though libcnb-test
itself doesn't pull newer versions.
Thanks, that did it.
Tests are failing on one of my prs and locally using main. Any ideas on what cache state might need to be invalidated as it seems the last PR merged into main was successful.
Here's my output: