Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
1
-
SDK22: Lambda + KV Range Scan, SDK24: Lambda + Known Issues
Description
The amount of failures for dotnet is growing as seen here http://sdk.jenkins.couchbase.com/blue/organizations/jenkins/dotnet%2Fsdk%2FTransactionsFITPerformer_SinglePerformer/detail/TransactionsFITPerformer_SinglePerformer/810/tests/
The failures are still happening locally but releases have stopped it from being analysed properly until now. The client problems I mentioned previously are likely contributing: TXNN-124
Now even simple StandardTest such as oneInsertCommitted are failing. On Jenkins it seemed to be ATR problems since so many tests are failing on the assertion assertCompletedInASingleAttempt but the problem is worse.
When run locally it is easier to see that I can't even find the ATR or doc in the UI, the create fails the first time as a transient failure then claims to succeed. As I mentioned though there is no document, it is missing in the UI and when the ATR check is commented out the assertDocExists check fails as well with doc not found.
For the performer to get the latest driver changes and for any new updates to the performer to be run on CI then the work to update the performer for the breaking change will need to be made. (Not the big change to make the integrated performer, just the smaller changes to make the old performer compatible which Graham made a guide to doing.)
Attachments
Issue Links
- relates to
-
TXNN-124 Problems with Client Record
- Resolved