OK, I updated the code to output a less verbose message at that point of the test and then check the state of the affected plugins. Let's see how it works tonight.
-Mark > -----Original Message----- > From: Ceki Gülcü [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 18, 2002 11:07 AM > To: Log4J Developers List > Subject: RE: FW: [GUMP] Test Failure > > > > You can check the status of each plugin separately to see if they are all > shutdown. > > At 10:58 18.12.2002 -0800, you wrote: > >Ceki, > > > >This is an excellent suggestion. And, I had not thought that > the order of > >the plugin shutdown would be different, but now it is obvious. It is > >indeterminate, at best. How can I account for this in the test file > >comparisons? I can break the multiple plugin shutdown case into its own > >test case to make this easier to deal with. > > > >-Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
