You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Execute MolComponentManager's tests in the Molecule-Examples package
testDeepCleanupGarbageCollect, testFlushComponents and testGarbageCollect can fail.
Executing them individually doesn't raise errors, and since the tests pass in Pharo 11 it seems more of a Pharo 12 problem than an setUp and tearDown problem.
Expected behavior
Tests that pass in Pharo 11 should also pass in Pharo 12.
Screenshots
Examples of different outputs
Version information:
OS: Windows
Version: 22H2
Pharo Version: 12
The text was updated successfully, but these errors were encountered:
Thanks Eliot
Thank for your report. If your tests works in isolation and not in a group it means that you get a dependency between your tests.
The tester runner has been changed to make sure that the tests are not always run in the same order just to spot such hidden and bad dependencies.
So can you check your code because to us this is not a Pharo problem.
S
Bug description
Some tests that pass in Pharo 11 don't pass in Pharo 12.
To Reproduce
Steps to reproduce the behavior:
dev-incubator
branch)MolComponentManager
's tests in theMolecule-Examples
packagetestDeepCleanupGarbageCollect
,testFlushComponents
andtestGarbageCollect
can fail.Executing them individually doesn't raise errors, and since the tests pass in Pharo 11 it seems more of a Pharo 12 problem than an
setUp
andtearDown
problem.Expected behavior
Tests that pass in Pharo 11 should also pass in Pharo 12.
Screenshots
Examples of different outputs
Version information:
The text was updated successfully, but these errors were encountered: