I was about to send a mail on that. Glad you asked though, I was afraid
no one had heard my cry for help :).
I had hoped to find some time to look at your problem later this week, but it looks as if
you have solved it already. Is that so?
Solved? Not really. Temporarily patched would be more suitable of a
description for what I did.
As I explained earlier the problem occurred when testing changes in
presence states. A series of tests in the TestOperationSetPresence class
would make the stack enter new presence states and verify that the
transition had generated all the corresponding events. The test that
failed was the one that brought the stack back to the on-line state as
that particular transition did not generate any events.
I had previously alredy added a Thread.sleep() at the end of each state
transition test as I had the feeling that the AIM server was not liking
rapid consecutive transitions. All I did now was increase that delay
from 2000 to 5000 ms, and that seemed to somehow work.
Oh dear! I've been there before many times, but (I think) always with ant running
jUnit tests which cause several Threads to run... this shouldn't matter, but often it
does. There's some old documentation on how (in theory) to extend jUnit for
multi-threading classes, and I even got desperate enough to plan the work once.
IBM wrote a new test harness for multi-threading last year (alphaworks software),
but I didn't like it for many reasons.
Am I right in thinking these failing tests involve multiple Threads - I know I could
look with a debugger, but I've got too many computers doing stuff at the moment.
As you can see this is far from being a solution but at least it stops
the "Build Failed" mails. In other words you are welcome to still have a
look at this and find a real solution.
Can you tell me the name of the test class and an individual test that is failing? I
presume I only need to comment-out a sleep and it will break?
I think this problem will take a while to resolve properly, but I will take a quick look
to see if it matches my own experiences. If it does match, then you can "look forward"
to randomly failing tests and hours of frustration tinkering with sleep times when ever
something apparently-unrelated has changed.
OTOH, in case you'd like to tackle sth else, we also have a problem with
ICQ nicknames. The joustsim stack that we use was primarily created for
AIM and it doesn't implement the ICQ requests that deal with nicknames.
I've been talking to Keith Lea (the author) about that and he had sent
me some classes that someone else had written and that supposedly
implement this stuff. I haven't yet had the time to look into those
since I am working on the MetaContactList now so if you (or anyone else
for that matter) are interested in this, I'd be glad to send them over.
Let me know if that's the case.
Nice try! I'm afraid I've got a backlog of (paid) work at the moment, with some
aggressive-but-justified deadlines. I'll be working 7 days a week for some time,
so can only spare SipComm the occasional hour or so.
On Tue, 21 Feb 2006 11:29:38 +0100, Emil Ivov wrote:
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com