csharp: Iterate more in GC-dependent test

Summary:
The inheritance test depends on the objects being actively destroyed.
Currently this happens in a two step process, where first the C#
object is collected from the GC. As this happens in a separate thread,
we schedule a callback to run in the main loop to actually unref the
EO object.

This commit adds more iterations to make sure the EO of the parent is
unref'd and releases the child.

This should be the last C#-related CI test failure

Ref T8313

Reviewers: stefan_schmidt, brunobelo, felipealmeida

Reviewed By: felipealmeida

Subscribers: cedric, #reviewers, #committers

Tags: #efl

Maniphest Tasks: T8313

Differential Revision: https://phab.enlightenment.org/D10612
This commit is contained in:
Lauro Moura 2019-11-26 11:56:51 -03:00
parent bb3f741990
commit aacd2fa82d
1 changed files with 3 additions and 3 deletions

View File

@ -142,9 +142,9 @@ class TestInheritance
CreateAndCheckInheritedObjects(out parentWRef, out childWRef);
// Two invocations to iterate a the child wasn't being released with a single one
Test.CollectAndIterate();
Test.CollectAndIterate();
// We need some extra iterations of the main loop to allow the async callbacks
// registered from the Dispose method to the main loop to run.
Test.CollectAndIterate(10, 10);
var parent = (Dummy.TestObject) parentWRef.Target;
var child = (Dummy.TestObject) childWRef.Target;