WIP: workaround objexport failure
diff --git a/kotlin-native/backend.native/tests/build.gradle b/kotlin-native/backend.native/tests/build.gradle
index 0a8bed8..ab96b9a 100644
--- a/kotlin-native/backend.native/tests/build.gradle
+++ b/kotlin-native/backend.native/tests/build.gradle
@@ -95,6 +95,7 @@
ext.isExperimentalMM = project.globalTestArgs.contains("-memory-model") && project.globalTestArgs.contains("experimental")
ext.isNoopGC = project.globalTestArgs.contains("-Xgc=noop")
+ext.isAggressiveGC = project.globalTestArgs.contains("-Xbinary=gcSchedulerType=aggressive")
// TODO: It also makes sense to test -g without asserts, and also to test -opt with asserts.
if (project.globalTestArgs.contains("-g")) {
@@ -5363,6 +5364,9 @@
if (isNoopGC) {
swiftExtraOpts += ["-D", "NOOP_GC"]
}
+ if (isAggressiveGC) {
+ swiftExtraOpts += ["-D", "AGGRESSIVE_GC"]
+ }
}
frameworkTest('testObjCExportNoGenerics') {
diff --git a/kotlin-native/backend.native/tests/objcexport/values.swift b/kotlin-native/backend.native/tests/objcexport/values.swift
index 78dde61..977618e 100644
--- a/kotlin-native/backend.native/tests/objcexport/values.swift
+++ b/kotlin-native/backend.native/tests/objcexport/values.swift
@@ -896,9 +896,15 @@
Holder.ref2 = obj2
}
+// With aggressive GC, the objects referenced from the Holder become freed once
+// we left the autoreleasepool scope, before ValuesKt.gc().autoreleasepool
+// TODO: This behaviour is possible for the regular GC too (but much less probable),
+// so we need to handle it somehow. E.g. by disabling GC at all during setting up the test.
+#if !AGGRESSIVE_GC
try assertFalse(Holder.ref1 === nil)
try assertFalse(Holder.ref2 === nil)
try assertEquals(actual: Holder.deinitialized, expected: 0)
+#endif
ValuesKt.gc()
