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

Integration tests can not run after running go test -count=1 -timeout 0 ./integration/... -v -run Integration #630

Closed
pacostas opened this issue Mar 15, 2023 · 3 comments

Comments

@pacostas
Copy link
Contributor

System info:

Linux fedora 6.1.15-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Mar 3 17:29:44 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Description:

The integration tests error after using the command go test -count=1 -timeout 0 ./integration/... -v -run Integration

Expected Behavior

Integration tests should run successfully

Current Behavior

Integration tests error with below error message

=== 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**

Possible Solution

I have tried:

  • removing all docker images and containers
  • uninstall and install all go dependencies
  • uninstall and install go

Steps to Reproduce

  1. Run the integration tests as usual with the command ./scripts/integration.sh
  2. Run the tests with go test -count=1 -timeout 0 ./integration/... -v -run Integration, this command should produce an error
  3. Run again the integration tests ./scripts/integration.sh this time they should produce an error

Motivations

I can not run the integration tests on my pc and as a result do further development.

@ryanmoran
Copy link
Member

Try deleting the freezer cache: rm -rf $HOME/.freezer-cache. If you ^C the tests early in the test run, sometimes it corrupts the local cache.

@robdimsdale
Copy link
Member

I also opened this issue to fix the underlying issue: ForestEckhardt/freezer#10

@pacostas
Copy link
Contributor Author

@ryanmoran Thank you, it worked!

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

No branches or pull requests

3 participants