A bit further up it says exactly which tests are failing. That’s just the suites.
On Jan 2, 2015, at 12:31 PM, Erik de Bruin <e...@ixsoftware.nl> wrote: > ... > [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest > [flexunit] Tests run: 36, Failures: 2, Errors: 0, Skipped: 0, Time > elapsed: 3.603 sec > ... > [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest > [flexunit] Tests run: 31, Failures: 1, Errors: 0, Skipped: 2, Time > elapsed: 170.805 sec > ... > [flexunit] Tests run: 428, Failures: 3, Errors: 0, Skipped: 20, Time > elapsed: 252.987 sec > > I'll reboot soon, then I'll try again. > > EdB > > > > On Fri, Jan 2, 2015 at 11:29 AM, Harbs <harbs.li...@gmail.com> wrote: >> I’m not seeing any failures, and Jenkins is not reporting any failures >> either. >> >> Which tests are failing for you? >> >> On Jan 2, 2015, at 11:55 AM, Erik de Bruin <e...@ixsoftware.nl> wrote: >> >>> Harbs, >>> >>> When I ran the tests with Java 1.8 on my Mac (Yosemite), I still see >>> failures: >>> >>> ... >>> [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest >>> [flexunit] Tests run: 36, Failures: 2, Errors: 0, Skipped: 0, Time >>> elapsed: 3.603 sec >>> ... >>> [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest >>> [flexunit] Tests run: 31, Failures: 1, Errors: 0, Skipped: 2, Time >>> elapsed: 170.805 sec >>> ... >>> [flexunit] Tests run: 428, Failures: 3, Errors: 0, Skipped: 20, Time >>> elapsed: 252.987 sec >>> >>> On 1.6 all is well! >>> >>> EdB >>> >>> >>> >>> On Wed, Dec 31, 2014 at 10:45 PM, Harbs <harbs.li...@gmail.com> wrote: >>>> I hacked together a solution for this. I’m not sure if there’s a nicer way >>>> to do it. Feel free to fix it up... >>>> >>>> After my last commit, we are down to 20 ignored tests total. >>>> >>>> It would be great if someone could check the one test that’s failing on >>>> the CI server. It’s passing on my machine, so I’m not sure what’s wrong >>>> there. If there’s no easy way to fix that test, we can set it to ignore >>>> again, but it looks like a good test to have. >>>> >>>> On Dec 31, 2014, at 11:22 PM, Harbs <harbs.li...@gmail.com> wrote: >>>> >>>>> Piotr, I have a question: >>>>> >>>>> I’m looking at the EventOverrideTest. >>>>> >>>>> The old tests look like they were run via xml like this: >>>>> <TestCase functionName="keyDownDerivedTest"> >>>>> <TestData name="overrideEditManager">true</TestData> >>>>> <TestData name="flash">false</TestData> >>>>> <TestData name="fileName">empty.xml</TestData> >>>>> <TestData name="tb_rtl">false</TestData> >>>>> <TestData name="rl_ltr">false</TestData> >>>>> </TestCase> >>>>> >>>>> These values were different for the different test cases. >>>>> >>>>> How is TestData.overrideEditManager supposed to be set on a case-by-case >>>>> basis in the current setup? >>>>> >>>>> There’s also a variable called TestData.eventOverride. I’m not sure how >>>>> that;’s supposed to be set. >>>>> >>>>> On Dec 31, 2014, at 12:36 AM, piotrz <piotrzarzyck...@gmail.com> wrote: >>>>> >>>>>> Harbs, >>>>>> >>>>>> Congratulations! You are absolutly the best! :) >>>>>> >>>>>> Do you still want me to look into tests ordering? >>>>>> >>>>>> Piotr >>>>>> >>>>>> >>>>>> >>>>>> ----- >>>>>> Apache Flex PMC >>>>>> piotrzarzyck...@gmail.com >>>>>> -- >>>>>> View this message in context: >>>>>> http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p44017.html >>>>>> Sent from the Apache Flex Development mailing list archive at Nabble.com. >>>>> >>>> >>> >>> >>> >>> -- >>> Ix Multimedia Software >>> >>> Jan Luykenstraat 27 >>> 3521 VB Utrecht >>> >>> T. 06-51952295 >>> I. www.ixsoftware.nl >> > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl
