FluintAirTestRunner won't close

[Ruprict]

I have seen this issue in a few threads here, but I can't seem to
figure out what people did to get rid of it. I am running Java 1.6,
ant 1.71. When I run the fluint ant task, the AIR runner comes up,
tests run, then it doesn't close. If I manually close it, the build
finishes.

I am sure I am simply missing whatever the fix is, so sorry for the
post, but I have burned a day on this already and need a push (read:
massive shove) in the right direction.

Thanks!

[Ruprict]

More info...

So, after changing a bunch of double quotes to single quotes, the
manual running of the ant build works. However, the CI tool (Cruise)
now hangs. I can see the TestRunner.exe process hanging there, which
I can kill, but the CI tool doesn't recover.

I realize this could be a Cruise issue as well, but thought I'd add
the info in case someone has been here before.

Thanks.

[Ruprict]

Even MORE info...


So, the CI task seems to be hanging in creating the output reports.
If I kill the process now, the ci job keeps going, but I don't get any
reports. This only happens when the CI is running. The manual ant
task creates the reports just fine.

I have opened up the security of the output folder to the planet, so I
don't think this is a security issue. Oh, and I just realized I never
mentioned my OS, which is Windows Server 2008.

[Brian]

@Ruprict - Sorry for taking so long to get back with you. I believe
you're running into the issue that I encountered when trying to run
Fluint AIRTestRunner headlessly via a CI server. From what I was able
to research and find, the Flash Player and AIR runtime need a windowed
environment to execute correctly. When you manually execute the Ant
script, it's because you're executing the Ant script in the context of
the user you're logged in as that has the windowing environment
available, that is succeeds. When you run CruiseControl it's most
likely using a JEE server under the hood that is setup to run
headlessly. I believe the stall in your build occurs because AIR
can't find a windowing environment to actually execute.

I was only able to get our build working headlessly on Linux using
xvfb-run with X-Windows as have most people from what I've heard. I
did have some luck running the CI server as LOCAL_ACCOUNT on WindowsXP
but I found it was too hard getting my build to work without a
specific user running the CI server (I used Hudson). I'm not sure if
Windows Server 2008 has more options available when setting the rights
for services, but even when I tried to grant desktop access to my CI
server's service in Windows it failed for me. You may want to
consider leaving a user logged in, running the CI server as
LOCAL_ACOUNT, and then when you need to use the box accessing it via
VNC or RDP; I played with this ideas initially but gave up on it, so
it may work but I can't promise anything.

I have yet to hear a success story of using any Flex testing tool on a
CI server running on Windows. Until Adobe can release a headless
Flash Player or AIR runtime, I can't give you much help, sorry.
Supposedly Icabod is being used by Google and does this but it's not
available publicly yet.

-Brian

[Glenn Goodrich]

Thanks for the great reply, Brian.  It inspired me to change the Logon account for the Cruise services to my account, which seems to have done the trick.

Fantastic, and thanks again.

Glenn

gl...@goodrichs.net