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

Test failure: Race detected in TestGit/SSH #26411

Closed
silverwind opened this issue Aug 9, 2023 · 5 comments
Closed

Test failure: Race detected in TestGit/SSH #26411

silverwind opened this issue Aug 9, 2023 · 5 comments
Labels
type/bug type/upstream This is an issue in one of Gitea's dependencies and should be reported there

Comments

@silverwind
Copy link
Member

silverwind commented Aug 9, 2023

Description

Seen this for the first time:

https://github.com/go-gitea/gitea/actions/runs/5808995595/job/15746928976?pr=26409

=== TestGit/SSH (tests/integration/git_test.go:95)
==================
WARNING: DATA RACE
Read at 0x00c00501a5b8 by goroutine 221160:
  github.com/gliderlabs/ssh.(*sshContext).Err()
      <autogenerated>:1 +0x31
  database/sql.(*Rows).awaitDone()
      /opt/hostedtoolcache/go/1.21.0/x64/src/database/sql/sql.go:2973 +0x2a8
  database/sql.(*Rows).initContextClose.func1()
      /opt/hostedtoolcache/go/1.21.0/x64/src/database/sql/sql.go:2949 +0x8f

Gitea Version

main

@silverwind silverwind changed the title Race detected in TestGit/SSH Test failure: Race detected in TestGit/SSH Aug 9, 2023
@silverwind
Copy link
Member Author

Related: gliderlabs/ssh#211

@silverwind
Copy link
Member Author

silverwind commented Aug 9, 2023

This is coming up a lot recently on CI. I wonder whether a recent change in our code exposed this race. Assuming upstream does not merge this quickly, we may need to put a bandaid fix in our code, or if possibly selectively disable the race detector for those code paths.

@wxiaoguang
Copy link
Contributor

wxiaoguang commented Aug 9, 2023

OK, I will "bypass" the upstream in the PR #26409


Update: The patch works, CI passes

@silverwind
Copy link
Member Author

silverwind commented Aug 10, 2023

Fixed in main branch and 1.20, leaving it open until we have a proper fix via gliderlabs/ssh#211.

@silverwind silverwind added the type/upstream This is an issue in one of Gitea's dependencies and should be reported there label Aug 10, 2023
@wxiaoguang
Copy link
Contributor

The upstream is dead. I think this issue could also be closed since our "workaround" works well.

wxiaoguang pushed a commit that referenced this issue Nov 3, 2023
Revert the workaround of #26409 and fix #26411, update github.com/gliderlabs/ssh to include gliderlabs/ssh@02f9d57
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 7, 2023
fuxiaohei pushed a commit to fuxiaohei/gitea that referenced this issue Jan 17, 2024
Revert the workaround of go-gitea#26409 and fix go-gitea#26411, update github.com/gliderlabs/ssh to include gliderlabs/ssh@02f9d57
silverwind pushed a commit to silverwind/gitea that referenced this issue Feb 20, 2024
Revert the workaround of go-gitea#26409 and fix go-gitea#26411, update github.com/gliderlabs/ssh to include gliderlabs/ssh@02f9d57
6543 pushed a commit to 6543-forks/gitea that referenced this issue Feb 22, 2024
Revert the workaround of go-gitea#26409 and fix go-gitea#26411, update github.com/gliderlabs/ssh to include gliderlabs/ssh@02f9d57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/bug type/upstream This is an issue in one of Gitea's dependencies and should be reported there
Projects
None yet
Development

No branches or pull requests

2 participants