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

Golang 1.20 breaks fly integration tests #8680

Closed
xtremerui opened this issue Feb 2, 2023 · 1 comment · Fixed by #8681
Closed

Golang 1.20 breaks fly integration tests #8680

xtremerui opened this issue Feb 2, 2023 · 1 comment · Fixed by #8681
Labels

Comments

@xtremerui
Copy link
Contributor

xtremerui commented Feb 2, 2023

Summary

golang 1.20 seems breaks (or makes them flaky) tests wherever there is stdin.close(). It is probably due to changes in os/exec package.

Steps to reproduce

Run concourse fly integration tests with go 1.20 and observe error as below example:

logging in to team 'main'


target saved
logging in to team 'main'


target saved


• Failure [0.311 seconds]
login -k Command login to new target with invalid SSL with -k [It] succeeds 
github.com/concourse/concourse/fly/integration/login_insecure_test.go:53

  Unexpected error:
      <*fs.PathError | 0xc000988bd0>: {
          Op: "close",
          Path: "|1",
          Err: <*errors.errorString | 0x1b4cab0>{
              s: "file already closed",
          },
      }
      close |1: file already closed
  occurred

  github.com/concourse/concourse/fly/integration/login_insecure_test.go:62

Expected results

Test passed

Actual results

Test failed

Additional context

The race condition seems happen more often in a slower env. In the case of Concourse CI, the errors are happening in external darwin worker.

Triaging info

  • Concourse version: 7.9.0
  • Browser (if applicable):
  • Did this used to work? yes
@xtremerui xtremerui added the bug label Feb 2, 2023
@xtremerui
Copy link
Contributor Author

We will hold on to Golang 1.19.5 until this issue is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant