When I run the test suite I get stuck on this test case, <snip> .. Executing RESULT_RC_SIGL.testGroup test case TEST_SIGL Executing The Chapter5Section1.testGroup class with 4 test cases .. Executing Section1.testGroup test case TEST_OBJECT_ISINSTANCEOF .. Executing Section1.testGroup test case TEST_OBJECT_OBJECTNAMEEQUALS .. Executing Section1.testGroup test case TEST_OBJECT_START Warning: orexxole.dll DLL process detach, instance count (3) not 0 ^CTerminate batch job (Y/N)? ^C
Same error message every time. If I run the section1.testGroup on its own it goes through every time. Hope it helps Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 19.11.2020 um 23:02 schrieb Rick McGuire <object.r...@gmail.com>: > > I've been tracing the execution of the ThrowExceptionX() calls, and > everything appears to be working as expected. You might want to try to see if > you can comment out SysFileTree tests to see if you can isolate the problem > to a single test. > > Rick > > On Thu, Nov 19, 2020 at 4:16 PM Rick McGuire <object.r...@gmail.com > <mailto:object.r...@gmail.com>> wrote: > I take back my earlier assertion. The two other threads are waiting for > kernel access so they can get dispatched. The main thread has just released > the kernel semaphore to wait for the object to complete, so those should be > able to run. I suspect your guess on ThrowExceptionX might be correct. > Perhaps we have an extra request on the Semaphore on the main thread after > the exception is thrown. > > Rick > > On Thu, Nov 19, 2020 at 4:04 PM Erich Steinböck <erich.steinbo...@gmail.com > <mailto:erich.steinbo...@gmail.com>> wrote: > The issue seems to be somehow related to SysFileTree, specifically our > Windows SysFileTree code. > From playing around with the test cases I got the impression it might be > related to Rexx errors. > Might the (relatively new) use of ThrowExceptionX break something? > > > On Thu, Nov 19, 2020 at 9:51 PM Rick McGuire <object.r...@gmail.com > <mailto:object.r...@gmail.com>> wrote: > Looking at this in the debugger, the main method is requesting the result > from a message object, and is waiting because there message is not complete. > However, the only other Rexx threads are a couple that are in the thread pool > waiting to be dispatched. I suspect there might have been an error in the > dispatched message object such that the thread died without a the message > completing. > > Rick > > On Thu, Nov 19, 2020 at 12:00 PM Erich Steinböck <erich.steinbo...@gmail.com > <mailto:erich.steinbo...@gmail.com>> wrote: > With the current trunk we have a hang issue on Windows when running the tests > that I cannot track down. > > I have no idea what may have introduced (or surfaced) the issue, and the > issue seems elusive as if it were related to GC. > > The fastest way to reproduce is by running > testoorexx -s -S -f SysFileTree -f Section1 > > Help very much appreciated! > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net <mailto:Oorexx-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net <mailto:Oorexx-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net <mailto:Oorexx-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel