On 11/28/14, 1:12 PM, "Christofer Dutz" wrote:
>Hi Alex,
>
>well I was simply assuming that something is generally not setup
>correctly and that one of them could simply check the reason for this and
>I was assuming that if we sort out the problem the tests could work fine.
Yeah, well it is in
...@adobe.com]
Gesendet: Freitag, 28. November 2014 17:55
An: dev@flex.apache.org
Betreff: Re: Jenkins builds and general structure of FlexJS/Falcon related
project
On 11/28/14, 8:29 AM, "Christofer Dutz" wrote:
>I changed the test runner in falcon to start the flashplayer wit
On 11/28/14, 8:54 AM, "Alex Harui" wrote:
>
>
>On 11/28/14, 8:29 AM, "Christofer Dutz" wrote:
>>The problem is the build structure of the project in general.
>>
>>It contains Falcon as well as FlexJS, unfortunately FlexJS' tests need
>>ASJS, which in turn needs Falcon.
>>
>>So we have sort of
On 11/28/14, 8:29 AM, "Christofer Dutz" wrote:
>I changed the test runner in falcon to start the flashplayer with a
>timeout (currently set to 20 seconds as I asked someone of Infra to check
>what the flashplayer is complaining about
This is exactly why using builds.a.o for GUI tests is ineff
Hi,
today I worked on getting the Flex builds working on builds.apache.org.
I changed the test runner in falcon to start the flashplayer with a timeout
(currently set to 20 seconds as I asked someone of Infra to check what the
flashplayer is complaining about ... but will set that back to 1 o
