I confirmed that the CI server also timed out. IMO, I wouldn’t worry about the arrow tests until you see them fail in a run where nothing failed before it.
I ran the tests in the debugger and tons of trace statements were dumped to the console. They look like: [trace] 340 71.95 STR2ColBB autoColBA autoConBB alwaysConBA auto It isn’t clear to me whether that is indicative of some bad code or config that is rendering and re-rendering the content or whether it really needs to run that code path that many times, but the trace statement is probably contributing to the likelihood that the test will time out. Anyway, hope that helps. I’m going back to my FlexJS code. -Alex On 1/28/15, 1:09 PM, "Alex Harui" <aha...@adobe.com> wrote: >I think I have a clue. I am getting an error due to a script timeout. >Have you examined the test output on the build server to see if had >something like this? > >I think the results are in >bin/apps/automation_apps/TEST-UnitTest.Tests.ContainerAttributeTest.xml > >-Alex > >On 1/28/15, 1:02 PM, "Harbs" <harbs.li...@gmail.com> wrote: > >>run “ant all” on TLF. >> >>On Jan 28, 2015, at 11:00 PM, Chris Martin <chrsm...@outlook.com> wrote: >> >>> How can I run these tests locally on my machine? :) >>> >>> Chris >>> >>>> From: harbs.li...@gmail.com >>>> Subject: Re: Failing TLF Builds >>>> Date: Wed, 28 Jan 2015 22:31:30 +0200 >>>> To: dev@flex.apache.org >>>> >>>> So maybe this is something that needs to be fixed to make the tests >>>>more stable. >>>> >>>> On Jan 28, 2015, at 10:02 PM, Alex Harui <aha...@adobe.com> wrote: >>>> >>>>> Actually, in the little I’ve looked at the test so far, I >>>>> have concerns that a failing test could leave the suite in a bad >>>>>state so >>>>> the only important thing is the first test to fail. >>>> >>> >> >
