Disable problematic example

[hubertp]

Some jobs appear to be stuck because of it.

[radeusgd]

I don't think this PR does what it says it does.

[radeusgd]

Unless I am greatly mistaken, the main method is only ran when manually running the GC_Example.enso script file.

To actually disable the test, you need to do the change elsewhere:

diff --git a/test/Base_Tests/src/Runtime/Managed_Resource_Spec.enso b/test/Base_Tests/src/Runtime/Managed_Resource_Spec.enso
--- a/test/Base_Tests/src/Runtime/Managed_Resource_Spec.enso	(revision a4259d31e0ea025aae4e50bbc8533f07ee536708)
+++ b/test/Base_Tests/src/Runtime/Managed_Resource_Spec.enso	(date 1721744396649)
@@ -58,7 +58,7 @@
         r_3 = Panic.recover Any <| Managed_Resource.bracket 42 (_-> Nothing) (_-> Panic.throw "action")
         r_3.catch . should_equal "action"
 
-    group_builder.specify "allocate lots of resources at once" <|
+    group_builder.specify "allocate lots of resources at once" pending=(if Environment.get "CI" . is_nothing . not then "GC Example is marked as pending as it was causing problems on the CI.") <|
         remaining = GC_Example.perform_test 100000 (_->Nothing)
         remaining . should_equal 0

(additionally we can do it conditionally on the CI env var - we already have a few tests that are pending only on the CI - that has the advantage that any regressions are slightly more likely to be detected in some of the local runs we do from time to time)

[hubertp]

Unless I am greatly mistaken, the main method is only ran when manually running the GC_Example.enso script file.

To actually disable the test, you need to do the change elsewhere:

diff --git a/test/Base_Tests/src/Runtime/Managed_Resource_Spec.enso b/test/Base_Tests/src/Runtime/Managed_Resource_Spec.enso
--- a/test/Base_Tests/src/Runtime/Managed_Resource_Spec.enso	(revision a4259d31e0ea025aae4e50bbc8533f07ee536708)
+++ b/test/Base_Tests/src/Runtime/Managed_Resource_Spec.enso	(date 1721744396649)
@@ -58,7 +58,7 @@
         r_3 = Panic.recover Any <| Managed_Resource.bracket 42 (_-> Nothing) (_-> Panic.throw "action")
         r_3.catch . should_equal "action"
 
-    group_builder.specify "allocate lots of resources at once" <|
+    group_builder.specify "allocate lots of resources at once" pending=(if Environment.get "CI" . is_nothing . not then "GC Example is marked as pending as it was causing problems on the CI.") <|
         remaining = GC_Example.perform_test 100000 (_->Nothing)
         remaining . should_equal 0

(additionally we can do it conditionally on the CI env var - we already have a few tests that are pending only on the CI - that has the advantage that any regressions are slightly more likely to be detected in some of the local runs we do from time to time)

Ah, wasn't aware this was executed directly.