[JAVA-4919] MONGODB-AWS ECS Auth tests fail since Kotlin driver added to the repository Created: 31/Mar/23  Updated: 01/Nov/23

Status: Backlog
Project: Java Driver
Component/s: Test Coverage
Affects Version/s: None
Fix Version/s: None

Type: Build Failure Priority: Major - P3
Reporter: Ross Lawley Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to JAVA-5207 Update AWS Auth test host and ECS Task Blocked
Quarter: FY24Q4
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   

The failure

The error is related to gradle failing / timing out / the daemon crashing when running the test.

Investigation so far

These test are currently failing since the introduction of the Kotlin driver:

Running the previous commit as a patch succeeds.

Probable cause:

Adding the kotlin driver into the gradle build seems to be the suspect.

Failed fixes

  • Updating Gradle to 7.6.1
  • Updating to Ubuntu 2004
  • Running driver-core:compileJava before running the test
  • Removing kotlin when running the ECS test (driver-core has a compile time dependency due for the codec registry to bson-kotlin / bson-kotlinx)


 Comments   
Comment by Githook User [ 05/Apr/23 ]

Author:

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

Message: Disable AWS ECS tests

Until we can figure out why they are failing and fix it.

It seems to be related to the recent addition of the Kotlin
driver

JAVA-4919
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/9ac2664495639b7b2c5369c37a0562b5f202c492

Comment by Jeffrey Yemin [ 03/Apr/23 ]

Options include:

  • Temporarily removing driver-core dependency on bson-kotlin (added for the default codec registry)
  • Roll back all of Kotlin changes
  • Disable the ECS tests
  • Find the root cause
Comment by Ross Lawley [ 31/Mar/23 ]

* Exception is:
[2023/03/31 18:48:42.756] sh14992| sh123| org.gradle.launcher.daemon.client.DaemonDisappearedException: Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)

Every incantation I've tried:

  • increasing memory for the jvm and the kotlin.daemon.jvm.options,
  • using a custom settings.gradle to only include the required projects
  • clearing the gradle cache directory
  • no-daemon mode

All have timed out or crashed with the above error.

I haven't been able to get onto the box to see if there are any error logs.

Recommendations are to look at the resources - why does this scenario have issues compiling both Java and Kotlin code when its fine on the other builds?

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