-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
System.Data.OleDb.Test - timeout and hangs #74488
Comments
Tagging subscribers to this area: @roji, @ajcvickers Issue DetailsThe test suite fails Failures in last 120 days
Roughly 1 failure per day, with 4 rolling runs affected in last 3 weeks. It is blocking CI, we should investigate it ASAP.
|
This comment was marked as duplicate.
This comment was marked as duplicate.
I do not see any hits in last week, so there is a good chance that this is fixed. |
I still see hits on some PRs, some of them created 1-2 days ago. Reopening. |
Stack trace of the crash (the hangs seems to be caused by crash reporting taking too long, so same root cause):
|
Note #76054 which could be related: after performing a query via the OleDB ACE driver, the process no longer exits properly. I've verified that switching to the SQL Server OleDB driver makes the problem go away, so presumably this would be an issue in the ACE driver itself. This could also be the root cause for the problem happening above, so switching to a different OleDB driver in the tests could be the "fix" here (though ideally, the ACE driver would be fixed...). /cc @ajcvickers |
@karelz we have a report that installing a recent update to the ACE driver may make this go away (KB5002243, see #76054 (comment)). Is it possible to make sure this KB is installed on our CI images? |
@roji this is also happening in the release/6.0 branch quite frequently, but it seems the automated arcade error message detection doesn't work in that branch. So if there is a fix available, please backport it to 6.0. Here is an example:
|
Here's another hit in a release/6.0 PR: #77283 |
@carlossanlop OK, thanks for flagging that. Is there anyone who can help with the suggestion in #74488 (comment)? It's possible that some Windows updates on the CI machines would make this go away. |
Since this is a known build error, I'm going to remove the blocking-clean-ci label. |
Roughly 1 failure per day, with 4 rolling runs affected in last 3 weeks. It is blocking CI, we should investigate it ASAP.
Report
Summary
Known Issue Error Message
Fill the error message using known issues guidance.
The text was updated successfully, but these errors were encountered: