I’m also seeing that columnContainerBreakTest2000 failed in the last two
runs.  It and several others are failing for me too.  Are they passing for
you?  Maybe if I look to see why they fail it will shed light on the
Arrows test.  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.

-Alex

On 1/28/15, 11:13 AM, "Harbs" <harbs.li...@gmail.com> wrote:

>There are about 20 tests that are ignored because they had issues when
>they were ported.
>
>My concern is actually two specific tests:
>
>GeneralFunctionsTest.arrowDown
>GeneralFunctionsTest.arrowUp
>
>These are passing for me locally, but are failing on the CI server.
>
>The reason I suspect there’s a real problem is that I’ve had a report of
>the down arrow moving to the wrong location on the line, but I have not
>seen this myself. So if someone gets these tests to fail on their
>machines, I’d really like to find out what behavior they observe.
>
>On Jan 28, 2015, at 8:43 PM, Alex Harui <aha...@adobe.com> wrote:
>
>> I just ran the tests myself. I get:
>> 
>> [flexunit] FlexUnit test spanElementReplaceTextInvalidPos in suite
>> UnitTest.Tests.ElementOperationTest was ignored.
>> [flexunit] FlexUnit test testAllEnumProps in suite
>> UnitTest.Tests.AllParaAttributeTest was ignored.
>> [flexunit] FlexUnit test endTabLongStringTest in suite
>> UnitTest.Tests.TabTest was ignored.
>> [flexunit] FlexUnit test noTabStop in suite UnitTest.Tests.TabTest was
>> ignored.
>> [flexunit] FlexUnit test arabicDirection in suite
>> UnitTest.Tests.WritingModeTest was ignored.
>> [flexunit] FlexUnit test twoColumnsTest in suite
>> UnitTest.Tests.ScrollingTest was ignored.
>> [flexunit] FlexUnit test draggingSelectioinMultiFlows in suite
>> UnitTest.Tests.ContainerTypeTest was ignored.
>> [flexunit] FlexUnit test deleteAtContainerStart (simple in suite
>> UnitTest.Tests.CompositionTest was ignored.
>> [flexunit] FlexUnit test partialCompositionTest (simple in suite
>> UnitTest.Tests.CompositionTest was ignored.
>> [flexunit] FlexUnit test deleteAtContainerStart (asknot in suite
>> UnitTest.Tests.CompositionTest was ignored.
>> [flexunit] FlexUnit test partialCompositionTest (asknot in suite
>> UnitTest.Tests.CompositionTest was ignored.
>> [flexunit] FlexUnit test columnContainerBreakTest3000 ([object Object])
>> in suite UnitTest.Tests.ContainerAttributeTest had errors.
>> [flexunit] FlexUnit test columnContainerBreakTest0 ([object Object]) in
>> suite UnitTest.Tests.ContainerAttributeTest had errors.
>> [flexunit] FlexUnit test columnContainerBreakTest1000 ([object Object])
>> in suite UnitTest.Tests.ContainerAttributeTest had errors.
>> [flexunit] FlexUnit test columnContainerBreakTest2000 ([object Object])
>> in suite UnitTest.Tests.ContainerAttributeTest had errors.
>> [flexunit] FlexUnit test paddingBottomTest ([object Object]) in suite
>> UnitTest.Tests.ContainerAttributeTest was ignored.
>> [flexunit] FlexUnit test checkColumnGapOnWidthChangeTest ([object
>> Object]) in suite UnitTest.Tests.ContainerAttributeTest was ignored.
>> [flexunit] FlexUnit test paddingBottomTest ([object Object]) in suite
>> UnitTest.Tests.ContainerAttributeTest was ignored.
>> [flexunit] FlexUnit test checkColumnGapOnWidthChangeTest ([object
>> Object]) in suite UnitTest.Tests.ContainerAttributeTest was ignored.
>> [flexunit] FlexUnit test columnContainerBreakTest0 ([object Object]) in
>> suite UnitTest.Tests.ContainerAttributeTest had errors.
>> [flexunit] FlexUnit test columnContainerBreakTest1000 ([object Object])
>> in suite UnitTest.Tests.ContainerAttributeTest had errors.
>> [flexunit] FlexUnit test columnContainerBreakTest2000 ([object Object])
>> in suite UnitTest.Tests.ContainerAttributeTest had errors.
>> [flexunit] FlexUnit test columnContainerBreakTest3000 ([object Object])
>> in suite UnitTest.Tests.ContainerAttributeTest had errors.
>> [flexunit] FlexUnit test ShortTextMouseEventTBRTLTest in suite
>> UnitTest.Tests.AllEventTest was ignored.
>> [flexunit] FlexUnit test ShortTextMouseEventRLLTRTest in suite
>> UnitTest.Tests.AllEventTest was ignored.
>> [flexunit] FlexUnit test ShortTextMouseEventTBLTRTest in suite
>> UnitTest.Tests.AllEventTest was ignored.
>> [flexunit] FlexUnit test ShortTextMouseEventRLRTLTest in suite
>> UnitTest.Tests.AllEventTest was ignored.
>> [flexunit] FlexUnit test contentWidthCheckLongFloat in suite
>> UnitTest.Tests.FloatTest was ignored.
>> [flexunit] FlexUnit test deletePreviousWordTest in suite
>> UnitTest.Tests.OperationTest was ignored.
>> [flexunit] FlexUnit test applyFormatToElementTest in suite
>> UnitTest.Tests.OperationTest was ignored.
>> 
>> I actually don’t think I ever saw them run for me which is why I did
>>test
>> checkins when I was trying to fix the build.
>> 
>> 
>> -Alex
>> 
>> On 1/28/15, 1:02 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>> 
>>> Arg!
>>> 
>>> Now the arrow tests are failing again.
>>> 
>>> I have a feeling that this is a legitimate failure, but it’s a
>>> sometimes/some machine failure.
>>> 
>>> If someone is constantly getting these failures, I have something I’d
>>> like them to try.
>>> 
>>> Thanks,
>>> Harbs
>>> 
>>> On Jan 28, 2015, at 9:23 AM, Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>>> At least the arrow tests are passing now.
>>>> 
>>>> I just disabled the paddingBottomTest.
>>>> 
>>>> On Jan 28, 2015, at 6:39 AM, Alex Harui <aha...@adobe.com> wrote:
>>>> 
>>>>> That last failure was after rebooting.
>>>>> 
>>>>> On 1/27/15, 11:20 AM, "Alex Harui" <aha...@adobe.com> wrote:
>>>>> 
>>>>>> If Erik doesn’t get to it first, I’ll try to remember to reboot the
>>>>>> mustella server tonight (about 10 hours from now).
>>>>>> 
>>>>>> On 1/27/15, 11:02 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>>>>>> 
>>>>>>> The last three builds of TLF failed on Jenkins. There’s three tests
>>>>>>> failing on the server, but are passing locally for me.
>>>>>>> 
>>>>>>> Is there any way to restart the server to try to get them to pass?
>>>>>>>Or
>>>>>>> should we just disable the tests on the server?
>>>>>>> 
>>>>>>> Maybe there’s some way that we can include the problematic tests in
>>>>>>> local
>>>>>>> builds, but exclude them from Jenkins?
>>>>>>> 
>>>>>>> Other thoughts anyone?
>>>>>>> 
>>>>>>> Harbs
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
>

Reply via email to