Community
Participate
Working Groups
See summary. When tests are run thus, they load the test scenario from disk. This means the repositories collection is null; this means new repos will get instantiated. But during teardown the repos from the previous test method are not deactivated (if optimizing==true). These repos are still hanging around in the VM somewhere, and are holding on to resources such as TCP ports, file locks and what not, so that the new repos fail to activate properly. (When run as a suite there is no problem because the scenario isn't loaded from disk for each test, but is the same instance for all tests.)
[09:22:13] Eike Stepper: what about this: [09:22:28] Eike Stepper: by default the "repo optimization" is disabled [09:22:37] Eike Stepper: the suites explicitely enable it [09:22:56] Caspar/Jasper: that could work, yes
Moving all open bug reports to 4.1 because the release is very near and it's hghly unlikely that there will be spare time to address 4.0 problems. Please make sure that your patches can be applied against the master branch and that your problem is not already fixed there!!!
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
I don't obeserve any trouble. Can I test this with a specific test class? No activity or ping here for years. Please reopen this bug if you feel a need.
