CI fails with strange errors (randomly) #17719
Labels
Comments
|
After adding |
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Jan 29, 2022
…e/MergePR One of the repeated intermittent failures we see in testing is a failure due to branches not being ready to merge. Prior to the immediate queue implementation we would attempt to flush all the queues and this would prevent the issue. However, the immediate queue is not flushable so the flushall is not successful at preventing this. This PR proposes an alternative solution - wait some time and try again up to 5 times. If this fails then there is a genuine issue and we should fail. Related go-gitea#17719 Signed-off-by: Andrew Thornton <[email protected]>
|
OK Cases 4 & 6 are fixed. Case 3 is likely fixed. Case 2 - This is a race between the pr patch queue and the test. We attempt to merge and then reattempt after flushing but I think the queues are not flushable since we moved to immediate queues. - I guess we could add a timer? #18451 should fix this. Case 1 - I have no idea what is happening there. Case 5... This looks like a deadlock or problem with the MySQL db - the SIGABORT suggests that something has called for everything to die. Now it could be that there was a problem with MySQL container. |
zeripath
added a commit
that referenced
this issue
Jan 29, 2022
…e/MergePR (#18451) One of the repeated intermittent failures we see in testing is a failure due to branches not being ready to merge. Prior to the immediate queue implementation we would attempt to flush all the queues and this would prevent the issue. However, the immediate queue is not flushable so the flushall is not successful at preventing this. This PR proposes an alternative solution - wait some time and try again up to 5 times. If this fails then there is a genuine issue and we should fail. Related #17719 Signed-off-by: Andrew Thornton <[email protected]>
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Feb 5, 2022
…e/MergePR (go-gitea#18451) Backport go-gitea#18451 One of the repeated intermittent failures we see in testing is a failure due to branches not being ready to merge. Prior to the immediate queue implementation we would attempt to flush all the queues and this would prevent the issue. However, the immediate queue is not flushable so the flushall is not successful at preventing this. This PR proposes an alternative solution - wait some time and try again up to 5 times. If this fails then there is a genuine issue and we should fail. Related go-gitea#17719 Signed-off-by: Andrew Thornton <[email protected]>
zeripath
added a commit
that referenced
this issue
Feb 5, 2022
…e/MergePR (#18451) (#18619) Backport #18451 One of the repeated intermittent failures we see in testing is a failure due to branches not being ready to merge. Prior to the immediate queue implementation we would attempt to flush all the queues and this would prevent the issue. However, the immediate queue is not flushable so the flushall is not successful at preventing this. This PR proposes an alternative solution - wait some time and try again up to 5 times. If this fails then there is a genuine issue and we should fail. Related #17719 Signed-off-by: Andrew Thornton <[email protected]>
|
outdated, close this one |
Chianina
pushed a commit
to Chianina/gitea
that referenced
this issue
Mar 28, 2022
…e/MergePR (go-gitea#18451) One of the repeated intermittent failures we see in testing is a failure due to branches not being ready to merge. Prior to the immediate queue implementation we would attempt to flush all the queues and this would prevent the issue. However, the immediate queue is not flushable so the flushall is not successful at preventing this. This PR proposes an alternative solution - wait some time and try again up to 5 times. If this fails then there is a genuine issue and we should fail. Related go-gitea#17719 Signed-off-by: Andrew Thornton <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are many strange errors occurring randomly during CI.
These errors are false positive, and make the CI fail, and then maintainers must spend more time to restart a CI build and wait .....
This issue records them, and hopefully we can resolve them to speed up the CI/merge workflow.
Case 1
Unexpected redirect in TestAPICreateComment with failed authentication
Case 2 - Should be fixed by #18451TestGit/SSH/BranchProtectMerge/MergePR failure to merge due to PR not being ready to merge
Case 3 - Likely fixed by #18444 - if not fixed it will be clearer.
NPE in TestEntries_GetCommitsInfo
Case 4 - Fixed by #17970Apparent SQLite deadlock in testInsertIssue
gitea CI failure (sqlite, 20m timeout)
https://gist.github.com/wxiaoguang/bd0e1c9377f00f6a4438836e07bba048
Very long logs, sample:
Case 5
Deadlock/Hang in TestRepoCommitsWithStatusError
Case 6 - FIXED by #18444make test-backend has changed files in the source tree
unit-test
The text was updated successfully, but these errors were encountered: