Skip to main content
R
richard_szalay
Participant
January 6, 2011
Question

AirCIListener freezing in FlexUnit 4.1 RC2

  • January 6, 2011
  • 1 reply
  • 1364 views

Hi guys,

I'm having troubles running the FlexUnit 4.1 RC2 CIListener on an AIR application. The window is launched and the first few tests run in the UI (I have the AIRCIListener, TraceListener and the UIListener all added), but once it gets to the 3rd or 4th test it locks up the window ("not responding"). This is presumably when it is trying to send the buffered data across to the ant task.

The listener is definitely connecting to the ant task host, but it is never receiving any data. If I break (CTRL+C) out of the ant task, the tests continue to run to completion in the opened window.

The output of the ant task is as follows (I've clipped the paths):

Setting up server process ...
Starting server ...
Opening server socket on port [1024].
Waiting for client connection ...
Found AIR version: 2.0
Created application descriptor at
Executing 'c:\...\adl.exe' with arguments:
'C:\...\flexUnitDescriptor.xml'

The ' characters around the executable and arguments are
not part of the command.

Client connected.
Setting inbound buffer size to [262144] bytes.
Receiving data ...
Sending acknowledgement to player to start sending test data ...

Any thoughts?

Rich

This topic has been closed for replies.

1 reply

M
mlabriola
Participating Frequently
January 6, 2011

Sounds like the player isn't getting the acknowledgment to continue... although you said it gets through a few tests. Are you sure about that/is it always the same number or same test that fails?

Just asking as I haven't seen this but obviously need to get it fixed

R
richard_szalayAuthor
Participant
January 6, 2011

It's always between 4 and 6 tests when it freezes - always the same number within a build, though causing a full rebuild could cause it to change (between 4 and 6). It definitely sounds like it's freezing when attempting to fire off the buffer to the server.

Also, I can confirm that moving back to FlexUnit 4.0 (swc and jar) fixes the problem.

M
mlabriola
Participating Frequently
January 6, 2011

Okay, thanks for the effort on this.

What's your environment like, os, jre version, etc.? Will try to get setup here to replicate

Mike

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices