-
Notifications
You must be signed in to change notification settings - Fork 13
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
Fix config #561
Fix config #561
Changes from 6 commits
71bb103
afc8031
194a0c4
3fad45c
58067bf
4c2e076
79118e2
121adab
76f1e89
d51fb41
c8a36fa
3069e64
1603e57
37f5f1f
85f85dc
9a160d8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -87,8 +87,8 @@ results: | |
ferretdb: | ||
stats: | ||
expected_fail: 10 | ||
expected_skip: 19 | ||
expected_pass: 633 | ||
expected_skip: 16 | ||
expected_pass: 621 | ||
|
||
ignore: | ||
# returns unknown result. | ||
|
@@ -124,8 +124,6 @@ results: | |
- go.mongodb.org/mongo-driver/mongo/integration/TestClient/retry_writes_error_20_wrapped/write_error_code_19_right_msg | ||
- go.mongodb.org/mongo-driver/mongo/integration/TestClient/retry_writes_error_20_wrapped/write_error_code_20 | ||
- go.mongodb.org/mongo-driver/mongo/integration/TestClient/retry_writes_error_20_wrapped/write_error_code_20_wrong_msg | ||
- go.mongodb.org/mongo-driver/mongo/integration/TestCausalConsistency_NotSupported | ||
- go.mongodb.org/mongo-driver/mongo/integration/TestCausalConsistency_NotSupported/afterClusterTime_not_included | ||
- go.mongodb.org/mongo-driver/mongo/integration/TestCausalConsistency_NotSupported/clusterTime_not_included | ||
- go.mongodb.org/mongo-driver/mongo/integration/TestChangeStream_Standalone | ||
- go.mongodb.org/mongo-driver/mongo/integration/TestChangeStream_Standalone/no_custom_standalone_error | ||
|
@@ -157,6 +155,8 @@ results: | |
- go.mongodb.org/mongo-driver/x/mongo/driver/integration/TestAggregate/Multiple_Batches | ||
- go.mongodb.org/mongo-driver/x/mongo/driver/integration/TestAggregate/TestMaxTimeMSInGetMore | ||
fail: | ||
- go.mongodb.org/mongo-driver/mongo/integration/TestCausalConsistency_NotSupported | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There must be a comment explaining why those tests fail There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I need to look into it more. They were previously passing now they panic.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I am not super confident on this but it seems that the changes made now cause their event monitor to return nil here when it tries to inspect the command name. Could be related to mongodb/mongo-go-driver#1347? @AlekSi should I add this failing test to common ignore for now? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. But it only fails on FerretDB which invalidates the above. 👁️ There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Added to FerretDB failures. |
||
- go.mongodb.org/mongo-driver/mongo/integration/TestCausalConsistency_NotSupported/afterClusterTime_not_included | ||
- go.mongodb.org/mongo-driver/examples/documentation_examples/TestDocumentationExamples | ||
|
||
# (NotImplemented) `aggregate` stage "$project" is not implemented yet | ||
|
@@ -182,10 +182,13 @@ results: | |
- go.mongodb.org/mongo-driver/mongo/integration/unified/TestUnifiedSpec | ||
mongodb: | ||
stats: | ||
expected_skip: 432 | ||
expected_pass: 1940 | ||
expected_skip: 435 | ||
expected_pass: 1948 | ||
|
||
skip: | ||
# skipping due to known failure: Test times out. See GODRIVER-2943 | ||
- go.mongodb.org/mongo-driver/mongo/integration/unified/TestUnifiedSpec/server-discovery-and-monitoring/unified/logging-standalone.json/Topology_lifecycle | ||
|
||
# execution failed: test must be skipped: "the \"modifyCollection\" operation is not supported" | ||
- go.mongodb.org/mongo-driver/mongo/integration/unified/TestUnifiedSpec/collection-management/modifyCollection-pre_and_post_images.json/modifyCollection_to_changeStreamPreAndPostImages_enabled | ||
- go.mongodb.org/mongo-driver/mongo/integration/unified/TestUnifiedSpec/crud/unified/findOneAndUpdate-errorResponse.json/findOneAndUpdate_document_validation_errInfo_is_accessible | ||
|
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.
Why the number of passing tests went down?
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.
That's needs some investigation.
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.
We seem to be running less subtests in total with the update. This is not the case for MongoDB. I am unsure why this is happening. I took a lot at the changelog but could not find a commit that might be the culprit. I logged some more output to verify that:
Any ideas?
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.
This bumped our passes back up a little.