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

CI check_dev_2 hangs for 10 minutes #25770

Closed
Tracked by #25899
zhouqiang-cl opened this issue Jun 25, 2021 · 5 comments
Closed
Tracked by #25899

CI check_dev_2 hangs for 10 minutes #25770

zhouqiang-cl opened this issue Jun 25, 2021 · 5 comments
Assignees
Labels
severity/major sig/execution SIG execution type/bug The issue is confirmed as a bug.

Comments

@zhouqiang-cl
Copy link
Contributor

Bug Report

in ci https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_check_2/detail/tidb_ghpr_check_2/12426/pipeline

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

master

@zhouqiang-cl zhouqiang-cl added the type/bug The issue is confirmed as a bug. label Jun 25, 2021
@zhouqiang-cl zhouqiang-cl changed the title CI check_dev2 hangs for 10 minutes CI check_dev_2 hangs for 10 minutes Jun 25, 2021
@zhouqiang-cl
Copy link
Contributor Author

[2021-06-25T10:11:21.918Z] FAIL	github.com/pingcap/tidb/executor	540.618s

@ichn-hu
Copy link
Contributor

ichn-hu commented Jul 13, 2021

@zhouqiang-cl are there more evidence about the hangs? can it be reproduced? if not, shall we close it until more evidence is collected?

@ichn-hu
Copy link
Contributor

ichn-hu commented Jul 13, 2021

/assign @ichn-hu

@zhouqiang-cl
Copy link
Contributor Author

@zhouqiang-cl are there more evidence about the hangs? can it be reproduced? if not, shall we close it until more evidence is collected?

Seems it not happens this days. I will close it

@ti-srebot
Copy link
Contributor

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major sig/execution SIG execution type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

4 participants