Skip to content

Improve resilience to cacheManager: EOF #10

Description

@robdimsdale

When we run ctrl+c the paketo buildpacks integration tests we sometimes see the following error on re-runs:

=== RUN   TestIntegration
    init_test.go:68: 
        Unexpected error:
            <*errors.errorString | 0xc000441a90>: 
            failed to open cacheManager: EOF
            {
                s: "failed to open cacheManager: EOF",
            }
        occurred
--- FAIL: TestIntegration (0.00s)
FAIL
FAIL	github.com/paketo-buildpacks/node-engine/integration	0.009s
FAIL
** GO Test Failed with index.docker.io/paketobuildpacks/builder:buildpackless-base**

We typically resolve this with:

rm -rf $HOME/.freezer-cache

This works, but it's not a great UX. Can we make this library more resilient to an empty cache manager?

Example of community member running into it: see paketo-buildpacks/node-engine#630

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions