Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
1.1.0
-
1
Description
.net Neo Failures
|
|
|
|
|
ATRDeletedTest - insert_onStagedReplace_whenCollectionHasBeenDeleted_shouldNotSucceed - timed out
|
|
|
|
|
ConcurrencySameATRTest - concurrentTxns10-500 - timeout on blocking read |
|
|
|
|
ConcurrencyTest - concurrentTxns50-100 - timed out |
|
|
|
|
ConcurrencyTest - concurrentTxns500_query - timeout on blocking read
|
|
|
|
|
ErrorHandlingTest - replacingDocAndHittingCasErrorContinuously - assertion error
|
|
|
|
|
ExpiredClientSideTest - checkExpiryFieldIsNotEqualToExpiration - null pointer exception |
|
|
|
|
FailureDuringCommitTest - crashDuringCommitOneRemoveDoneOneLeft - timed out
|
FailureDuringCommitTest - continuousFailOnSecondRemoveMidCommit - timed out
|
|
|
|
|
FailureDuringRollbackTest - failOnSecondDocMidRollback - timed out
|
|
|
|
|
LargeTransactionsTest - create25kDocumentTransaction() - timed out
|
|
|
|
|
MultipleBucketsTest - basicRemoveMultipleBuckets_secondBucketNonDefaultCollection() - timed out
|
|
|
|
|
MultipleTransactionsTest - twoConcurrentTransactionsInsertingSameDoc - null pointer exception |
|
|
|
|
SameDocTwiceTest - readWritePermissionsOnCollectionsOfTxnOperationButNotOnATRCollection - aborted
|
|
|
|
|
More timeouts in the cleanup and query tests.
|
I believe that using the certificates is causing a delay which can cause these timeout errors, we have seen them on other sdks as well and even the driver takes longer to start the tests when it has to load the certificates.
|
These are the notes from the failures found when running the Neo multicerts tests.
The method that was used to apply the multicerts was to use a CertificateStoreFactory, search using the thumbprint in my local cert store and then use that factory in the cluster options. I then ran the usual test suite minus the situational tests.