[JAVA-4977] failed:WriteConcernOperationTest.*omit Created: 24/May/23  Updated: 28/Oct/23  Resolved: 25/May/23

Status: Closed
Project: Java Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 4.10.0

Type: Build Failure Priority: Unknown
Reporter: xgen-buildbaron-user Assignee: Jeffrey Yemin
Resolution: Fixed Votes: 0
Labels: BB-Tools
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Documentation Changes: Not Needed
Documentation Changes Summary:

1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?


 Description   

test on tests-jdk8-unsecure__version~4.0_os~linux_topology~sharded-cluster_auth~noauth_ssl~nossl_jdk~jdk8

Host: i-0b4d9d40c4ad88604
Project: mongo-java-driver
Commit: 14dd3563

Failing Test Logs:

  • com.mongodb.client.WriteConcernOperationTest.shouldPassAllOutcomes_default-write-concern-2.6.json_DeleteMany_omits_default_write_concern - Logs | History

Task Logs:



 Comments   
Comment by Jeffrey Yemin [ 25/May/23 ]

Decided to skip the tests on sharded clusters < 4.2

Comment by Githook User [ 25/May/23 ]

Author:

{'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}

Message: Disable WriteConcernOperationTest where server is sharded and < 4.2

The tests are flaky on older servers and the issue appears to be with the server not the driver

JAVA-4977
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/15911e0b9734cce559d8dcd682db73b393249244

Comment by xgen-buildbaron-user [ 24/May/23 ]

A new auto-resolution rule has been created for this BF. Active rules can be seen
here.

Key: JAVA-4977
Expiration: expire_on_bf_close
Rules:
  projects: .*
  tests: WriteConcernOperationTest.*omit

Generated at Thu Feb 08 09:03:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.