-
Notifications
You must be signed in to change notification settings - Fork 933
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
Added support for the CancelQuery() method in IStatelessSession #3074
Added support for the CancelQuery() method in IStatelessSession #3074
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution,
We do not accept PR without corresponding tests. See contributing. May you add a test?
…xtensions class as it has been deferred to the next major version. (#809)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not checked all databases on my local setup, so waiting for the automated tests to do this for me.
src/NHibernate.Test/Stateless/StatelessSessionCancelQueryFixture.cs
Outdated
Show resolved
Hide resolved
On GitHub action, AFAIK we are running SQL Server under Linux, and we seem to hit dotnet/SqlClient#109. It has been fixed in Microsoft.Data.SqlClient 2.0, but we are using System.Data.SqlClient, which is unlikely to be fixed, since Microsoft has announced it will go on developing only Microsoft.Data.SqlClient. Should we switch Sql Server tests to Microsoft.Data.SqlClient? Well, ideally I think we should go on testing System.Data.SqlClient under .Net Framework, but test Microsoft.Data.SqlClient under net6.0. |
@hazzik, it seems this cancel test freezes Oracle test suit. (Maybe Oracle does not support Cancel...) The NHibernate agent on TeamCity seems gone. Can you check what is going on please? |
This comment was marked as off-topic.
This comment was marked as off-topic.
We should at least add it to the test suit. Maybe we test it in both platforms? |
Changed on 'cancel': In oracle message contain word 'cancel'(ORA-01013: user requested cancel of current operation) and not 'cancelled' or 'canceled'. Word 'cancel' contains in message for all database types.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Ok, agent is back. I've also increased tier for the VM, so builds are slightly faster now. |
For some reason I cannot get any logs for Oracle |
Oracle on TC works fine :-/ |
@hazzik I'll try installing 18.3 on my machine and run the test: if it passes then I have no idea why TC failed. |
On 18.3 (on my local server) it works fine, all tests passed. The only difference from TC is that I have Oracle on Windows. |
"Canceled in 360m - Oracle" misled me, I checked locally for nothing. At the TC: all test(NHibernate Oracle Managed 32) pass. |
Why misled? There is clearly some issue with Git Hub Action build (Oracle on Linux) - https://github.com/nhibernate/nhibernate-core/runs/7643016174?check_suite_focus=true |
On "Git Hub Action" yes but not on teamcity(I initially thought that the assembly hung on the TC due to deadlock). So "misled me" means that the problem is not where I thought it was. |
But I wrote that:
|
Yes, yes I am blind, sometimes. |
I think we should simply skip tests for Oracle and Sql Server on linux. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SupportsCancelQuery
introduction looks not necessary to me (I expected skip right inside test case). But why not.
It makes for a central point for checking database limitations, which may help when we wish to check if some of these limitations do no more apply. Tests skipped directly inside them for some databases are harder to spot. |
This comment was marked as resolved.
This comment was marked as resolved.
Created issue to track SqlServer and Oracle #3167 |
Resolve #809