You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flex.apache.org by Harbs <ha...@gmail.com> on 2014/12/29 11:01:20 UTC

TLF status was: [DISCUSS] Release Apache Flex 4.14.0

I’ve made some more progress. We’re down to 5 failures and 1 error:
 [flexunit] Suite: UnitTest.Tests.OperationTest
 [flexunit] Tests run: 47, Failures: 2, Errors: 0, Skipped: 2, Time elapsed: 5.002 sec
 [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
 [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.409 sec
 [flexunit] Suite: UnitTest.Tests.CrossContainerTest
 [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
 [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
 [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.947 sec
 [flexunit] Suite: UnitTest.Tests.TabTest
 [flexunit] Tests run: 19, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 0.713 sec
 [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
 [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.794 sec
 [flexunit] Suite: UnitTest.Tests.EventOverrideTest
 [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.374 sec
 [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
 [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.158 sec
 [flexunit] Suite: UnitTest.Tests.FactoryImportTest
 [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
 [flexunit] Suite: UnitTest.Tests.AllEventTest
 [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.729 sec
 [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
 [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 0.274 sec
 [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
 [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.178 sec
 [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
 [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.436 sec
 [flexunit] Suite: UnitTest.Tests.FloatTest
 [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.313 sec
 [flexunit] Suite: UnitTest.Tests.AttributeTest
 [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.778 sec
 [flexunit] Suite: UnitTest.Tests.FlowModelTest
 [flexunit] Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.267 sec
 [flexunit] Suite: UnitTest.Tests.ElementOperationTest
 [flexunit] Tests run: 25, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.772 sec
 [flexunit] Suite: UnitTest.Tests.WritingModeTest
 [flexunit] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.549 sec
 [flexunit] Suite: UnitTest.Tests.UndoRedoTest
 [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.040 sec
 [flexunit] Suite: UnitTest.Tests.ScrollingTest
 [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.430 sec
 [flexunit] Suite: UnitTest.Tests.BoxTest
 [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.116 sec
 [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
 [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.738 sec
 [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
 [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 78.049 sec
 [flexunit] Suite: UnitTest.Tests.CompositionTest
 [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 17.595 sec
 [flexunit] Results :
 [flexunit] Tests run: 428, Failures: 5, Errors: 1, Skipped: 41, Time elapsed: 184.707 sec
On Dec 24, 2014, at 9:13 PM, Harbs <ha...@gmail.com> wrote:

> Here’s the current results. I’ll start with the OperationTest results. There’s a good chance that the other issues are related to the one I just fixed...
> 
> [flexunit] Suite: UnitTest.Tests.OperationTest
>  [flexunit] Tests run: 47, Failures: 4, Errors: 3, Skipped: 2, Time elapsed: 5.089 sec
>  [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>  [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.339 sec
>  [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec
>  [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 2.887 sec
>  [flexunit] Suite: UnitTest.Tests.TabTest
>  [flexunit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.543 sec
>  [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.767 sec
>  [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>  [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.376 sec
>  [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>  [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.152 sec
>  [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
>  [flexunit] Suite: UnitTest.Tests.AllEventTest
>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.695 sec
>  [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 1.998 sec
>  [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>  [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.173 sec
>  [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>  [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.313 sec
>  [flexunit] Suite: UnitTest.Tests.FloatTest
>  [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.469 sec
>  [flexunit] Suite: UnitTest.Tests.AttributeTest
>  [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.421 sec
>  [flexunit] Suite: UnitTest.Tests.FlowModelTest
>  [flexunit] Tests run: 23, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 1.273 sec
>  [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>  [flexunit] Tests run: 25, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 1.363 sec
>  [flexunit] Suite: UnitTest.Tests.WritingModeTest
>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec
>  [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
>  [flexunit] Suite: UnitTest.Tests.ScrollingTest
>  [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.769 sec
>  [flexunit] Suite: UnitTest.Tests.BoxTest
>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.201 sec
>  [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.951 sec
>  [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>  [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 113.957 sec
>  [flexunit] Suite: UnitTest.Tests.CompositionTest
>  [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 3.929 sec
>  [flexunit] 
>  [flexunit] Results :
>  [flexunit] 
>  [flexunit] Tests run: 428, Failures: 6, Errors: 5, Skipped: 41, Time elapsed: 177.319 sec
>  [flexunit] 
> On Dec 24, 2014, at 9:09 PM, Harbs <ha...@gmail.com> wrote:
> 
>> I’m running the Unit Tests right now. I’ll see what comes up…
>

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by piotrz <pi...@gmail.com>.

Hi Harbs,

It's even better - In jenkins build we do not have these 1 error :)

Great job!

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43943.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

Thanks. :-)

I’m not getting that error any more, so I guess there’s no need.

On Dec 31, 2014, at 12:36 AM, piotrz <pi...@gmail.com> wrote:

> Harbs,
> 
> Congratulations! You are absolutly the best! :) 
> 
> Do you still want me to look into tests ordering? 
> 
> Piotr
> 
> 
> 
> -----
> Apache Flex PMC
> piotrzarzycki21@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.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by piotrz <pi...@gmail.com>.

Harbs,

This is another huge thing which I have to implement in our TLF tests -
configuration for every test case.

Logic for reading configuration for tests was bind with some UI
functionality (It was tree where you could choose which tests should be
launched) - I have removed everything and left only basic configuration - As
you could see in EventOverrideTest we don't have properties
TestData.eventOverride or TestData.overrideEditManager.

It could be my next step after SDK release. - Add tests configuration from
flex-tlf\test\testCases\.

I think we have enough from our TLF side to for this release. :)

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p44071.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by piotrz <pi...@gmail.com>.

Erik,

I have just tried on Windows with Java 1.8 and I don't have any errors...

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p44073.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

I have a feeling there might be a some-times bug here.

There seems to be a difference between different machines on arrow behavior which might be why the arrow test is failing for you.

Please try the following:
Place your cursor in the beginning of a text flow line (it should not matter which one) and hit the up arrow key. Does the cursor move to the beginning or end of the previous line?

For me it moves to the beginning of the line, but for one of my QA folks, it moves to the end of the line. Since it’s not failing for me, I’m having trouble debugging…

On Jan 2, 2015, at 12:55 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> I see the 'flex-tlf' build is also reporting no issues. So, it must be
> me, and I didn't see any issues when I use Java 1.6.
> 
> Let's leave it at that, and go back to stabilizing the release branch
> and get 4.14 out the door.
> 
> Thanks,
> 
> EdB
> 
> 
> 
> On Fri, Jan 2, 2015 at 11:42 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>> Ah, lemme look...
>> 
>> Here they are:
>> 
>> [flexunit] FlexUnit test paddingBottomTest ([object Object]) in suite
>> UnitTest.Tests.ContainerAttributeTest failed.
>> [flexunit] FlexUnit test arrowUp in suite
>> UnitTest.Tests.GeneralFunctionsTest failed.
>> [flexunit] FlexUnit test arrowDown in suite
>> UnitTest.Tests.GeneralFunctionsTest failed.
>> 
>> Thanks,
>> 
>> EdB
>> 
>> 
>> On Fri, Jan 2, 2015 at 11:38 AM, Harbs <ha...@gmail.com> wrote:
>>> 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 <er...@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 <ha...@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 <er...@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 <ha...@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 <ha...@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 <pi...@gmail.com> wrote:
>>>>>>>> 
>>>>>>>>> Harbs,
>>>>>>>>> 
>>>>>>>>> Congratulations! You are absolutly the best! :)
>>>>>>>>> 
>>>>>>>>> Do you still want me to look into tests ordering?
>>>>>>>>> 
>>>>>>>>> Piotr
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> -----
>>>>>>>>> Apache Flex PMC
>>>>>>>>> piotrzarzycki21@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
>>> 
>> 
>> 
>> 
>> --
>> 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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

I see the 'flex-tlf' build is also reporting no issues. So, it must be
me, and I didn't see any issues when I use Java 1.6.

Let's leave it at that, and go back to stabilizing the release branch
and get 4.14 out the door.

Thanks,

EdB



On Fri, Jan 2, 2015 at 11:42 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
> Ah, lemme look...
>
> Here they are:
>
> [flexunit] FlexUnit test paddingBottomTest ([object Object]) in suite
> UnitTest.Tests.ContainerAttributeTest failed.
> [flexunit] FlexUnit test arrowUp in suite
> UnitTest.Tests.GeneralFunctionsTest failed.
> [flexunit] FlexUnit test arrowDown in suite
> UnitTest.Tests.GeneralFunctionsTest failed.
>
> Thanks,
>
> EdB
>
>
> On Fri, Jan 2, 2015 at 11:38 AM, Harbs <ha...@gmail.com> wrote:
>> 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 <er...@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 <ha...@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 <er...@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 <ha...@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 <ha...@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 <pi...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Harbs,
>>>>>>>>
>>>>>>>> Congratulations! You are absolutly the best! :)
>>>>>>>>
>>>>>>>> Do you still want me to look into tests ordering?
>>>>>>>>
>>>>>>>> Piotr
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -----
>>>>>>>> Apache Flex PMC
>>>>>>>> piotrzarzycki21@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
>>
>
>
>
> --
> 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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Ah, lemme look...

Here they are:

[flexunit] FlexUnit test paddingBottomTest ([object Object]) in suite
UnitTest.Tests.ContainerAttributeTest failed.
[flexunit] FlexUnit test arrowUp in suite
UnitTest.Tests.GeneralFunctionsTest failed.
[flexunit] FlexUnit test arrowDown in suite
UnitTest.Tests.GeneralFunctionsTest failed.

Thanks,

EdB


On Fri, Jan 2, 2015 at 11:38 AM, Harbs <ha...@gmail.com> wrote:
> 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 <er...@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 <ha...@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 <er...@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 <ha...@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 <ha...@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 <pi...@gmail.com> wrote:
>>>>>>
>>>>>>> Harbs,
>>>>>>>
>>>>>>> Congratulations! You are absolutly the best! :)
>>>>>>>
>>>>>>> Do you still want me to look into tests ordering?
>>>>>>>
>>>>>>> Piotr
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----
>>>>>>> Apache Flex PMC
>>>>>>> piotrzarzycki21@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
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

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 <er...@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 <ha...@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 <er...@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 <ha...@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 <ha...@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 <pi...@gmail.com> wrote:
>>>>> 
>>>>>> Harbs,
>>>>>> 
>>>>>> Congratulations! You are absolutly the best! :)
>>>>>> 
>>>>>> Do you still want me to look into tests ordering?
>>>>>> 
>>>>>> Piotr
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> -----
>>>>>> Apache Flex PMC
>>>>>> piotrzarzycki21@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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

...
[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 <ha...@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 <er...@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 <ha...@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 <ha...@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 <pi...@gmail.com> wrote:
>>>>
>>>>> Harbs,
>>>>>
>>>>> Congratulations! You are absolutly the best! :)
>>>>>
>>>>> Do you still want me to look into tests ordering?
>>>>>
>>>>> Piotr
>>>>>
>>>>>
>>>>>
>>>>> -----
>>>>> Apache Flex PMC
>>>>> piotrzarzycki21@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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

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 <er...@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 <ha...@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 <ha...@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 <pi...@gmail.com> wrote:
>>> 
>>>> Harbs,
>>>> 
>>>> Congratulations! You are absolutly the best! :)
>>>> 
>>>> Do you still want me to look into tests ordering?
>>>> 
>>>> Piotr
>>>> 
>>>> 
>>>> 
>>>> -----
>>>> Apache Flex PMC
>>>> piotrzarzycki21@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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

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 <ha...@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 <ha...@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 <pi...@gmail.com> wrote:
>>
>>> Harbs,
>>>
>>> Congratulations! You are absolutly the best! :)
>>>
>>> Do you still want me to look into tests ordering?
>>>
>>> Piotr
>>>
>>>
>>>
>>> -----
>>> Apache Flex PMC
>>> piotrzarzycki21@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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

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 <ha...@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 <pi...@gmail.com> wrote:
> 
>> Harbs,
>> 
>> Congratulations! You are absolutly the best! :) 
>> 
>> Do you still want me to look into tests ordering? 
>> 
>> Piotr
>> 
>> 
>> 
>> -----
>> Apache Flex PMC
>> piotrzarzycki21@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.
>

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

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 <pi...@gmail.com> wrote:

> Harbs,
> 
> Congratulations! You are absolutly the best! :) 
> 
> Do you still want me to look into tests ordering? 
> 
> Piotr
> 
> 
> 
> -----
> Apache Flex PMC
> piotrzarzycki21@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.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

Could someone take a look at AllParaAttributeTest? It’s passing on my local machine, but failing on the ci server. I’m not sure what’s going wrong there.

If we can get that test to consistently pass that would be nice…

On Dec 31, 2014, at 12:36 AM, piotrz <pi...@gmail.com> wrote:

> Harbs,
> 
> Congratulations! You are absolutly the best! :) 
> 
> Do you still want me to look into tests ordering? 
> 
> Piotr
> 
> 
> 
> -----
> Apache Flex PMC
> piotrzarzycki21@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.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by piotrz <pi...@gmail.com>.

Harbs,

Congratulations! You are absolutly the best! :) 

Do you still want me to look into tests ordering? 

Piotr



-----
Apache Flex PMC
piotrzarzycki21@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.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

Could someone take a look at the error on the CI server? The TLF build is passing, but there’s some kind of Java error:

ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
java.io.IOException: remote file operation failed: <http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/> at hudson.remoting.Channel@174ea1b:flex_sdk_slave2: java.io.IOException: Failed to read <http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/ws/bin/apps/asTestApps/bin/AliceScroll.swf>
Is this really a JUnit report file? Your configuration must be matching too many files

I’m clueless as to what this means…

Harbs

On Dec 30, 2014, at 9:42 PM, Harbs <ha...@gmail.com> wrote:

> Whoopee!
> 
> I just fixed the last failing test just in time for the new year! TLF should now be good to go. :-)
> 
> I’ll try to write a wiki on the table support sometime over the next few days.
> 
> When I have some time, I’ll also try to take a look at the ignored tests and see which ones I can get operational.
> 
> On Dec 30, 2014, at 4:57 PM, piotrz <pi...@gmail.com> wrote:
> 
>> Yep Only one error left.
>

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

Whoopee!

I just fixed the last failing test just in time for the new year! TLF should now be good to go. :-)

I’ll try to write a wiki on the table support sometime over the next few days.

When I have some time, I’ll also try to take a look at the ignored tests and see which ones I can get operational.

On Dec 30, 2014, at 4:57 PM, piotrz <pi...@gmail.com> wrote:

> Yep Only one error left.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by piotrz <pi...@gmail.com>.

Yep Only one error left.
I see some new errors, after last build we should see in
${output.dir}/apps/automation_apps/bin
reports with unit tests results. 

Is it problem with file write ? Anyone know ? 

[flexunit] Tests run: 428, Failures: 1, Errors: 0, Skipped: 42, Time
elapsed: 592.169 sec
 [flexunit] 

BUILD FAILED
c:\Jenkins\workspace\flex-tlf\build.xml:312: FlexUnit tests failed during
the test run.

Total time: 13 minutes 44 seconds
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to
exception
java.io.IOException: remote file operation failed:
c:\Jenkins\workspace\flex-tlf at
hudson.remoting.Channel@174ea1b:flex_sdk_slave2: java.io.IOException: Failed
to read
c:\Jenkins\workspace\flex-tlf\automation_tests\src\UnitTest\Tests\ContainerAttributeTest.as
Is this really a JUnit report file? Your configuration must be matching too
many files
	at hudson.FilePath.act(FilePath.java:977)
	at hudson.FilePath.act(FilePath.java:959)
	at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:90)
	at
hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:120)
	at
hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:137)
	at
hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
	at hudson.model.Run.execute(Run.java:1784)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p44001.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by piotrz <pi...@gmail.com>.

Ok. I will have some time on Saturday or Sunday and will try to look into
that. 



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43995.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

It did not help.

On Dec 30, 2014, at 12:45 PM, piotrz <pi...@gmail.com> wrote:

> Put it in the WritingModeTest
> 
> [TestCase(order=1)]
> public class WritingModeTest

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by piotrz <pi...@gmail.com>.

Put it in the WritingModeTest

[TestCase(order=1)]
public class WritingModeTest

I haven't ordered unit test classes yet, so this is only my guess, whether
this help.




-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43993.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

That goes in WritingModeTest.as or in AllTestsSuite.as?

(I still have no clue how these tests are working internally. It makes me very uncomfortable to be working with them as “black boxes”…)

On Dec 30, 2014, at 12:27 PM, piotrz <pi...@gmail.com> wrote:

> Ok so try to add [TestCase(order=1)] tag to WritingModeTest class from my
> link.
> 
> 
> 
> -----
> Apache Flex PMC
> piotrzarzycki21@gmail.com
> --
> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43990.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by piotrz <pi...@gmail.com>.

Ok so try to add [TestCase(order=1)] tag to WritingModeTest class from my
link.



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43990.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

The order the tests are run seems to have nothing to do with the order of variables or alphabetical order.

On Dec 30, 2014, at 12:20 PM, Harbs <ha...@gmail.com> wrote:

> I tried that. It did not make a difference.
> 
> On Dec 30, 2014, at 12:17 PM, piotrz <pi...@gmail.com> wrote:
> 
>> Try to put public var writingModeTest:WritingModeTest; in the first place in
>> AllTestsSuite - It could help and run WritingModeTest as first.
>> 
>> Piotr
>> 
>> 
>> 
>> -----
>> Apache Flex PMC
>> piotrzarzycki21@gmail.com
>> --
>> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43986.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

I tried that. It did not make a difference.

On Dec 30, 2014, at 12:17 PM, piotrz <pi...@gmail.com> wrote:

> Try to put public var writingModeTest:WritingModeTest; in the first place in
> AllTestsSuite - It could help and run WritingModeTest as first.
> 
> Piotr
> 
> 
> 
> -----
> Apache Flex PMC
> piotrzarzycki21@gmail.com
> --
> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43986.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by piotrz <pi...@gmail.com>.

Try to put public var writingModeTest:WritingModeTest; in the first place in
AllTestsSuite - It could help and run WritingModeTest as first.

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43986.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Jup, that last commit took care of that "problem" ;-)

EdB



On Tue, Dec 30, 2014 at 12:35 PM, Harbs <ha...@gmail.com> wrote:
> I’ve been getting the ContainerAttributeTest failure on and off. I have a feeling it’s a rounding error problem. If so, I’ll fix the test to take that into account…
>
> On Dec 30, 2014, at 1:32 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>
>> I got:
>>
>> "insertTextTest in suite UnitTest.Tests.OperationTest"
>>
>> on both Javas;
>>
>> "paddingBottomTest ([object Object]) in suite
>> UnitTest.Tests.ContainerAttributeTest failed."
>>
>> only on Java 1.6.
>>
>> HTH,
>>
>> EdB
>>
>>
>> On Tue, Dec 30, 2014 at 11:29 AM, Harbs <ha...@gmail.com> wrote:
>>> The consistent failure was OperationTest.insertTextTest Right?
>>>
>>> The second one should be WritingModeTest.arabicDirection.
>>>
>>> It consistently fails for me when I run all the test, but passed when I only run WritingModeTest.
>>>
>>> On Dec 30, 2014, at 12:24 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>>
>>>> Java 1.8:
>>>>
>>>> Tests run: 428, Failures: 1, Errors: 0, Skipped: 42, Time elapsed: 257.348 sec
>>>>
>>>> Java 1.6:
>>>>
>>>> Tests run: 428, Failures: 2, Errors: 0, Skipped: 42, Time elapsed: 500.364 sec
>>>>
>>>> EdB
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Dec 30, 2014 at 11:09 AM, Harbs <ha...@gmail.com> wrote:
>>>>> BTW, I just made another commit. The only real error left seems to be an Operation test error where a new span is being inserted into a Link element rather than being inserted after it.
>>>>>
>>>>> On Dec 30, 2014, at 12:07 PM, Harbs <ha...@gmail.com> wrote:
>>>>>
>>>>>> Okay, but how do we change the order in AllTestsSuite? I want to move WritingModeTest to the top.
>>>>>>
>>>>>> Changing the order of the variables does not seem to do anything.
>>>>>>
>>>>>> On Dec 30, 2014, at 11:51 AM, piotrz <pi...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi Harbs,
>>>>>>>
>>>>>>> Yes you can order items in your unit test class. Take a look [1]
>>>>>>>
>>>>>>> [1] https://cwiki.apache.org/confluence/display/FLEX/FlexUnit+Order
>>>>>>>
>>>>>>> Piotr
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----
>>>>>>> Apache Flex PMC
>>>>>>> piotrzarzycki21@gmail.com
>>>>>>> --
>>>>>>> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43982.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
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

I’ve been getting the ContainerAttributeTest failure on and off. I have a feeling it’s a rounding error problem. If so, I’ll fix the test to take that into account…

On Dec 30, 2014, at 1:32 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> I got:
> 
> "insertTextTest in suite UnitTest.Tests.OperationTest"
> 
> on both Javas;
> 
> "paddingBottomTest ([object Object]) in suite
> UnitTest.Tests.ContainerAttributeTest failed."
> 
> only on Java 1.6.
> 
> HTH,
> 
> EdB
> 
> 
> On Tue, Dec 30, 2014 at 11:29 AM, Harbs <ha...@gmail.com> wrote:
>> The consistent failure was OperationTest.insertTextTest Right?
>> 
>> The second one should be WritingModeTest.arabicDirection.
>> 
>> It consistently fails for me when I run all the test, but passed when I only run WritingModeTest.
>> 
>> On Dec 30, 2014, at 12:24 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>> 
>>> Java 1.8:
>>> 
>>> Tests run: 428, Failures: 1, Errors: 0, Skipped: 42, Time elapsed: 257.348 sec
>>> 
>>> Java 1.6:
>>> 
>>> Tests run: 428, Failures: 2, Errors: 0, Skipped: 42, Time elapsed: 500.364 sec
>>> 
>>> EdB
>>> 
>>> 
>>> 
>>> 
>>> On Tue, Dec 30, 2014 at 11:09 AM, Harbs <ha...@gmail.com> wrote:
>>>> BTW, I just made another commit. The only real error left seems to be an Operation test error where a new span is being inserted into a Link element rather than being inserted after it.
>>>> 
>>>> On Dec 30, 2014, at 12:07 PM, Harbs <ha...@gmail.com> wrote:
>>>> 
>>>>> Okay, but how do we change the order in AllTestsSuite? I want to move WritingModeTest to the top.
>>>>> 
>>>>> Changing the order of the variables does not seem to do anything.
>>>>> 
>>>>> On Dec 30, 2014, at 11:51 AM, piotrz <pi...@gmail.com> wrote:
>>>>> 
>>>>>> Hi Harbs,
>>>>>> 
>>>>>> Yes you can order items in your unit test class. Take a look [1]
>>>>>> 
>>>>>> [1] https://cwiki.apache.org/confluence/display/FLEX/FlexUnit+Order
>>>>>> 
>>>>>> Piotr
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> -----
>>>>>> Apache Flex PMC
>>>>>> piotrzarzycki21@gmail.com
>>>>>> --
>>>>>> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43982.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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

I got:

"insertTextTest in suite UnitTest.Tests.OperationTest"

on both Javas;

"paddingBottomTest ([object Object]) in suite
UnitTest.Tests.ContainerAttributeTest failed."

only on Java 1.6.

HTH,

EdB


On Tue, Dec 30, 2014 at 11:29 AM, Harbs <ha...@gmail.com> wrote:
> The consistent failure was OperationTest.insertTextTest Right?
>
> The second one should be WritingModeTest.arabicDirection.
>
> It consistently fails for me when I run all the test, but passed when I only run WritingModeTest.
>
> On Dec 30, 2014, at 12:24 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>
>> Java 1.8:
>>
>> Tests run: 428, Failures: 1, Errors: 0, Skipped: 42, Time elapsed: 257.348 sec
>>
>> Java 1.6:
>>
>> Tests run: 428, Failures: 2, Errors: 0, Skipped: 42, Time elapsed: 500.364 sec
>>
>> EdB
>>
>>
>>
>>
>> On Tue, Dec 30, 2014 at 11:09 AM, Harbs <ha...@gmail.com> wrote:
>>> BTW, I just made another commit. The only real error left seems to be an Operation test error where a new span is being inserted into a Link element rather than being inserted after it.
>>>
>>> On Dec 30, 2014, at 12:07 PM, Harbs <ha...@gmail.com> wrote:
>>>
>>>> Okay, but how do we change the order in AllTestsSuite? I want to move WritingModeTest to the top.
>>>>
>>>> Changing the order of the variables does not seem to do anything.
>>>>
>>>> On Dec 30, 2014, at 11:51 AM, piotrz <pi...@gmail.com> wrote:
>>>>
>>>>> Hi Harbs,
>>>>>
>>>>> Yes you can order items in your unit test class. Take a look [1]
>>>>>
>>>>> [1] https://cwiki.apache.org/confluence/display/FLEX/FlexUnit+Order
>>>>>
>>>>> Piotr
>>>>>
>>>>>
>>>>>
>>>>> -----
>>>>> Apache Flex PMC
>>>>> piotrzarzycki21@gmail.com
>>>>> --
>>>>> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43982.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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

The consistent failure was OperationTest.insertTextTest Right?

The second one should be WritingModeTest.arabicDirection.

It consistently fails for me when I run all the test, but passed when I only run WritingModeTest.

On Dec 30, 2014, at 12:24 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> Java 1.8:
> 
> Tests run: 428, Failures: 1, Errors: 0, Skipped: 42, Time elapsed: 257.348 sec
> 
> Java 1.6:
> 
> Tests run: 428, Failures: 2, Errors: 0, Skipped: 42, Time elapsed: 500.364 sec
> 
> EdB
> 
> 
> 
> 
> On Tue, Dec 30, 2014 at 11:09 AM, Harbs <ha...@gmail.com> wrote:
>> BTW, I just made another commit. The only real error left seems to be an Operation test error where a new span is being inserted into a Link element rather than being inserted after it.
>> 
>> On Dec 30, 2014, at 12:07 PM, Harbs <ha...@gmail.com> wrote:
>> 
>>> Okay, but how do we change the order in AllTestsSuite? I want to move WritingModeTest to the top.
>>> 
>>> Changing the order of the variables does not seem to do anything.
>>> 
>>> On Dec 30, 2014, at 11:51 AM, piotrz <pi...@gmail.com> wrote:
>>> 
>>>> Hi Harbs,
>>>> 
>>>> Yes you can order items in your unit test class. Take a look [1]
>>>> 
>>>> [1] https://cwiki.apache.org/confluence/display/FLEX/FlexUnit+Order
>>>> 
>>>> Piotr
>>>> 
>>>> 
>>>> 
>>>> -----
>>>> Apache Flex PMC
>>>> piotrzarzycki21@gmail.com
>>>> --
>>>> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43982.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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Java 1.8:

Tests run: 428, Failures: 1, Errors: 0, Skipped: 42, Time elapsed: 257.348 sec

Java 1.6:

Tests run: 428, Failures: 2, Errors: 0, Skipped: 42, Time elapsed: 500.364 sec

EdB




On Tue, Dec 30, 2014 at 11:09 AM, Harbs <ha...@gmail.com> wrote:
> BTW, I just made another commit. The only real error left seems to be an Operation test error where a new span is being inserted into a Link element rather than being inserted after it.
>
> On Dec 30, 2014, at 12:07 PM, Harbs <ha...@gmail.com> wrote:
>
>> Okay, but how do we change the order in AllTestsSuite? I want to move WritingModeTest to the top.
>>
>> Changing the order of the variables does not seem to do anything.
>>
>> On Dec 30, 2014, at 11:51 AM, piotrz <pi...@gmail.com> wrote:
>>
>>> Hi Harbs,
>>>
>>> Yes you can order items in your unit test class. Take a look [1]
>>>
>>> [1] https://cwiki.apache.org/confluence/display/FLEX/FlexUnit+Order
>>>
>>> Piotr
>>>
>>>
>>>
>>> -----
>>> Apache Flex PMC
>>> piotrzarzycki21@gmail.com
>>> --
>>> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43982.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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

BTW, I just made another commit. The only real error left seems to be an Operation test error where a new span is being inserted into a Link element rather than being inserted after it.

On Dec 30, 2014, at 12:07 PM, Harbs <ha...@gmail.com> wrote:

> Okay, but how do we change the order in AllTestsSuite? I want to move WritingModeTest to the top.
> 
> Changing the order of the variables does not seem to do anything.
> 
> On Dec 30, 2014, at 11:51 AM, piotrz <pi...@gmail.com> wrote:
> 
>> Hi Harbs,
>> 
>> Yes you can order items in your unit test class. Take a look [1]
>> 
>> [1] https://cwiki.apache.org/confluence/display/FLEX/FlexUnit+Order
>> 
>> Piotr
>> 
>> 
>> 
>> -----
>> Apache Flex PMC
>> piotrzarzycki21@gmail.com
>> --
>> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43982.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

Okay, but how do we change the order in AllTestsSuite? I want to move WritingModeTest to the top.

Changing the order of the variables does not seem to do anything.

On Dec 30, 2014, at 11:51 AM, piotrz <pi...@gmail.com> wrote:

> Hi Harbs,
> 
> Yes you can order items in your unit test class. Take a look [1]
> 
> [1] https://cwiki.apache.org/confluence/display/FLEX/FlexUnit+Order
> 
> Piotr
> 
> 
> 
> -----
> Apache Flex PMC
> piotrzarzycki21@gmail.com
> --
> View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43982.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by piotrz <pi...@gmail.com>.

Hi Harbs,

Yes you can order items in your unit test class. Take a look [1]

[1] https://cwiki.apache.org/confluence/display/FLEX/FlexUnit+Order

Piotr



-----
Apache Flex PMC
piotrzarzycki21@gmail.com
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43982.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

It sounds like a timing issue…

I’ll see what I can do about tracking it down.

On Dec 29, 2014, at 8:08 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> Just ran again with 1.8, got the error. Then with 1.6: no error. I
> threw in 1.7 for good measure: zero errors.
> 
> EdB
> 
> 
> 
> On Mon, Dec 29, 2014 at 6:04 PM, Harbs <ha...@gmail.com> wrote:
>> Weird. I think my machine (Mac 10.9.5) uses Java 1.6.
>> 
>> I get the error.
>> 
>> On Dec 29, 2014, at 3:47 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>> 
>>> Fun fact: when run with Java (1.)6, I get:
>>> 
>>> Tests run: 428, Failures: 5, Errors: 0, Skipped: 41, Time elapsed: 246.937 sec
>>> 
>>> Since the Windows build machine also runs Java (1.)6, the error seems
>>> to correlate to the Java edition?
>>> 
>>> Ed
>>> 
>>> On Mon, Dec 29, 2014 at 2:28 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>>> On my Mac, this is the current status:
>>>> 
>>>> Tests run: 428, Failures: 4, Errors: 1, Skipped: 41, Time elapsed: 253.360 sec
>>>> 
>>>> EdB
>>>> 
>>>> 
>>>> 
>>>> On Mon, Dec 29, 2014 at 11:01 AM, Harbs <ha...@gmail.com> wrote:
>>>>> I’ve made some more progress. We’re down to 5 failures and 1 error:
>>>>> [flexunit] Suite: UnitTest.Tests.OperationTest
>>>>> [flexunit] Tests run: 47, Failures: 2, Errors: 0, Skipped: 2, Time elapsed: 5.002 sec
>>>>> [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>>>> [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.409 sec
>>>>> [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.947 sec
>>>>> [flexunit] Suite: UnitTest.Tests.TabTest
>>>>> [flexunit] Tests run: 19, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 0.713 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.794 sec
>>>>> [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>>>> [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.374 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>>>> [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.158 sec
>>>>> [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllEventTest
>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.729 sec
>>>>> [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 0.274 sec
>>>>> [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>>>> [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.178 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>>>> [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.436 sec
>>>>> [flexunit] Suite: UnitTest.Tests.FloatTest
>>>>> [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.313 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AttributeTest
>>>>> [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.778 sec
>>>>> [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>>>> [flexunit] Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.267 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>>>> [flexunit] Tests run: 25, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.772 sec
>>>>> [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>>>> [flexunit] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.549 sec
>>>>> [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.040 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>>>> [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.430 sec
>>>>> [flexunit] Suite: UnitTest.Tests.BoxTest
>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.116 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.738 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>>>> [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 78.049 sec
>>>>> [flexunit] Suite: UnitTest.Tests.CompositionTest
>>>>> [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 17.595 sec
>>>>> [flexunit] Results :
>>>>> [flexunit] Tests run: 428, Failures: 5, Errors: 1, Skipped: 41, Time elapsed: 184.707 sec
>>>>> On Dec 24, 2014, at 9:13 PM, Harbs <ha...@gmail.com> wrote:
>>>>> 
>>>>>> Here’s the current results. I’ll start with the OperationTest results. There’s a good chance that the other issues are related to the one I just fixed...
>>>>>> 
>>>>>> [flexunit] Suite: UnitTest.Tests.OperationTest
>>>>>> [flexunit] Tests run: 47, Failures: 4, Errors: 3, Skipped: 2, Time elapsed: 5.089 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>>>>> [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.339 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 2.887 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.TabTest
>>>>>> [flexunit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.543 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.767 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>>>>> [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.376 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>>>>> [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.152 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AllEventTest
>>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.695 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 1.998 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>>>>> [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.173 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>>>>> [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.313 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.FloatTest
>>>>>> [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.469 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AttributeTest
>>>>>> [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.421 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>>>>> [flexunit] Tests run: 23, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 1.273 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>>>>> [flexunit] Tests run: 25, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 1.363 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>>>>> [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.769 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.BoxTest
>>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.201 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.951 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>>>>> [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 113.957 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.CompositionTest
>>>>>> [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 3.929 sec
>>>>>> [flexunit]
>>>>>> [flexunit] Results :
>>>>>> [flexunit]
>>>>>> [flexunit] Tests run: 428, Failures: 6, Errors: 5, Skipped: 41, Time elapsed: 177.319 sec
>>>>>> [flexunit]
>>>>>> On Dec 24, 2014, at 9:09 PM, Harbs <ha...@gmail.com> wrote:
>>>>>> 
>>>>>>> I’m running the Unit Tests right now. I’ll see what comes up…
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> 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
>> 
> 
> 
> 
> -- 
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

It passes when I run the TabTest alone.
It seems to be testing for a Flash Player bug rather than a TLF bug and the current test does not seem to be doing anything:

            //the long string value is the correct test data.  Since this is a Player bug, we can't check in the correct test data until Player fixes the bug.
            //Need to remove the comment to check in the correct test data once Player fixes the bug.
            tlf.tabStops = "e700 e269";
            //tlf.tabStops = "e700 e269.1499999999998";

I think we can safely ignore this test.

On Dec 29, 2014, at 8:08 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> Just ran again with 1.8, got the error. Then with 1.6: no error. I
> threw in 1.7 for good measure: zero errors.
> 
> EdB
> 
> 
> 
> On Mon, Dec 29, 2014 at 6:04 PM, Harbs <ha...@gmail.com> wrote:
>> Weird. I think my machine (Mac 10.9.5) uses Java 1.6.
>> 
>> I get the error.
>> 
>> On Dec 29, 2014, at 3:47 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>> 
>>> Fun fact: when run with Java (1.)6, I get:
>>> 
>>> Tests run: 428, Failures: 5, Errors: 0, Skipped: 41, Time elapsed: 246.937 sec
>>> 
>>> Since the Windows build machine also runs Java (1.)6, the error seems
>>> to correlate to the Java edition?
>>> 
>>> Ed
>>> 
>>> On Mon, Dec 29, 2014 at 2:28 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>>> On my Mac, this is the current status:
>>>> 
>>>> Tests run: 428, Failures: 4, Errors: 1, Skipped: 41, Time elapsed: 253.360 sec
>>>> 
>>>> EdB
>>>> 
>>>> 
>>>> 
>>>> On Mon, Dec 29, 2014 at 11:01 AM, Harbs <ha...@gmail.com> wrote:
>>>>> I’ve made some more progress. We’re down to 5 failures and 1 error:
>>>>> [flexunit] Suite: UnitTest.Tests.OperationTest
>>>>> [flexunit] Tests run: 47, Failures: 2, Errors: 0, Skipped: 2, Time elapsed: 5.002 sec
>>>>> [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>>>> [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.409 sec
>>>>> [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.947 sec
>>>>> [flexunit] Suite: UnitTest.Tests.TabTest
>>>>> [flexunit] Tests run: 19, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 0.713 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.794 sec
>>>>> [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>>>> [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.374 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>>>> [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.158 sec
>>>>> [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllEventTest
>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.729 sec
>>>>> [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 0.274 sec
>>>>> [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>>>> [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.178 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>>>> [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.436 sec
>>>>> [flexunit] Suite: UnitTest.Tests.FloatTest
>>>>> [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.313 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AttributeTest
>>>>> [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.778 sec
>>>>> [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>>>> [flexunit] Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.267 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>>>> [flexunit] Tests run: 25, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.772 sec
>>>>> [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>>>> [flexunit] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.549 sec
>>>>> [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.040 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>>>> [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.430 sec
>>>>> [flexunit] Suite: UnitTest.Tests.BoxTest
>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.116 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.738 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>>>> [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 78.049 sec
>>>>> [flexunit] Suite: UnitTest.Tests.CompositionTest
>>>>> [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 17.595 sec
>>>>> [flexunit] Results :
>>>>> [flexunit] Tests run: 428, Failures: 5, Errors: 1, Skipped: 41, Time elapsed: 184.707 sec
>>>>> On Dec 24, 2014, at 9:13 PM, Harbs <ha...@gmail.com> wrote:
>>>>> 
>>>>>> Here’s the current results. I’ll start with the OperationTest results. There’s a good chance that the other issues are related to the one I just fixed...
>>>>>> 
>>>>>> [flexunit] Suite: UnitTest.Tests.OperationTest
>>>>>> [flexunit] Tests run: 47, Failures: 4, Errors: 3, Skipped: 2, Time elapsed: 5.089 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>>>>> [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.339 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 2.887 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.TabTest
>>>>>> [flexunit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.543 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.767 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>>>>> [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.376 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>>>>> [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.152 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AllEventTest
>>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.695 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 1.998 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>>>>> [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.173 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>>>>> [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.313 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.FloatTest
>>>>>> [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.469 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AttributeTest
>>>>>> [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.421 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>>>>> [flexunit] Tests run: 23, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 1.273 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>>>>> [flexunit] Tests run: 25, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 1.363 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>>>>> [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.769 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.BoxTest
>>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.201 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.951 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>>>>> [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 113.957 sec
>>>>>> [flexunit] Suite: UnitTest.Tests.CompositionTest
>>>>>> [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 3.929 sec
>>>>>> [flexunit]
>>>>>> [flexunit] Results :
>>>>>> [flexunit]
>>>>>> [flexunit] Tests run: 428, Failures: 6, Errors: 5, Skipped: 41, Time elapsed: 177.319 sec
>>>>>> [flexunit]
>>>>>> On Dec 24, 2014, at 9:09 PM, Harbs <ha...@gmail.com> wrote:
>>>>>> 
>>>>>>> I’m running the Unit Tests right now. I’ll see what comes up…
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> 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
>> 
> 
> 
> 
> -- 
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

Another question:

One of the other failing tests is this one:

        [Test]
        public function bindableSpan():void
        {
            // Bindable span should not lose its formatting
            var textFlow:TextFlow = new TextFlow();
            var paragraph:ParagraphElement = new ParagraphElement();
            var span1:SpanElement = new SpanElement();
            var span2:SpanElement = new SpanElement();
            var format:TextLayoutFormat = new TextLayoutFormat();
            format.fontWeight = FontWeight.BOLD;
            span2.format = format;
            paragraph.mxmlChildren = [ span1, span2 ];
            textFlow.mxmlChildren = [ paragraph ];
            textFlow.flowComposer.addController(new ContainerController(new Sprite()));
            textFlow.flowComposer.compose();		// force normalize
            assertTrue("Spans should not be merged!", span2.parent == span1.parent && paragraph.numChildren == 2);
            assertTrue("Formatting on second span should be preserved!", span2.fontWeight == FontWeight.BOLD);
        }

span2 is removed from the paragraph when the flow is normalized. Can anyone explain why empty spans should not be merged when they are normalized?

On Dec 30, 2014, at 10:54 AM, Harbs <ha...@gmail.com> wrote:

> Question:
> 
> Is there a way to specify the order tests are run?
> One of the failures is in WritingModeTest. The arabicDirection test is failing when all the tests are run, but passing when the WritingModeTest is run by itself.
> 
> I want to see what happens if I run WritingModeTest as the first test suite.
> 
> On Dec 30, 2014, at 12:26 AM, Harbs <ha...@gmail.com> wrote:
> 
>> I just made another commit. Now Down to 3. :-)
>> 
>> [flexunit] Tests run: 428, Failures: 3, Errors: 0, Skipped: 42, Time elapsed: 155.729 sec
>> 
>> On Dec 29, 2014, at 9:53 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>> 
>>> Oh, there are plenty of Mustella tests failing ;-) But those failures
>>> don't seem to be related to TLF, as far as I can tell.
>>> 
>>> So, you're 0.5 errors and 4 failures away from "being done"!
>>> 
>>> EdB
>>> 
>>> 
>>> 
>>> On Mon, Dec 29, 2014 at 8:46 PM, Harbs <ha...@gmail.com> wrote:
>>>> I thought I remembered that besides the unit test, there were mustella tests failing.
>>>> 
>>>> If not, all the better… ;-)
>>>> 
>>>> On Dec 29, 2014, at 9:34 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>>> 
>>>>> Just curious, why are you looking at Mustella tests? There don't seem
>>>>> to be Mustella tests failing in a manner that would indicate a problem
>>>>> with TLF.
>>>>> 
>>>>> EdB
>>>>> 
>>>>> 
>>>>> 
>>>>> On Mon, Dec 29, 2014 at 7:41 PM, Harbs <ha...@gmail.com> wrote:
>>>>>> Is there a way to see what Mustella tests are failing on the CI server? I’d rather know what I’m dealing with before trying to run the full suite of tests on a local machine…
>>>>>> 
>>>>>> On Dec 29, 2014, at 8:08 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>>>>> 
>>>>>>> Just ran again with 1.8, got the error. Then with 1.6: no error. I
>>>>>>> threw in 1.7 for good measure: zero errors.
>>>>>>> 
>>>>>>> EdB
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> 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
>> 
>

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

Question:

Is there a way to specify the order tests are run?
One of the failures is in WritingModeTest. The arabicDirection test is failing when all the tests are run, but passing when the WritingModeTest is run by itself.

I want to see what happens if I run WritingModeTest as the first test suite.

On Dec 30, 2014, at 12:26 AM, Harbs <ha...@gmail.com> wrote:

> I just made another commit. Now Down to 3. :-)
> 
> [flexunit] Tests run: 428, Failures: 3, Errors: 0, Skipped: 42, Time elapsed: 155.729 sec
> 
> On Dec 29, 2014, at 9:53 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
> 
>> Oh, there are plenty of Mustella tests failing ;-) But those failures
>> don't seem to be related to TLF, as far as I can tell.
>> 
>> So, you're 0.5 errors and 4 failures away from "being done"!
>> 
>> EdB
>> 
>> 
>> 
>> On Mon, Dec 29, 2014 at 8:46 PM, Harbs <ha...@gmail.com> wrote:
>>> I thought I remembered that besides the unit test, there were mustella tests failing.
>>> 
>>> If not, all the better… ;-)
>>> 
>>> On Dec 29, 2014, at 9:34 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>> 
>>>> Just curious, why are you looking at Mustella tests? There don't seem
>>>> to be Mustella tests failing in a manner that would indicate a problem
>>>> with TLF.
>>>> 
>>>> EdB
>>>> 
>>>> 
>>>> 
>>>> On Mon, Dec 29, 2014 at 7:41 PM, Harbs <ha...@gmail.com> wrote:
>>>>> Is there a way to see what Mustella tests are failing on the CI server? I’d rather know what I’m dealing with before trying to run the full suite of tests on a local machine…
>>>>> 
>>>>> On Dec 29, 2014, at 8:08 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>>>> 
>>>>>> Just ran again with 1.8, got the error. Then with 1.6: no error. I
>>>>>> threw in 1.7 for good measure: zero errors.
>>>>>> 
>>>>>> EdB
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> 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
>

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

I just made another commit. Now Down to 3. :-)

[flexunit] Tests run: 428, Failures: 3, Errors: 0, Skipped: 42, Time elapsed: 155.729 sec

On Dec 29, 2014, at 9:53 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> Oh, there are plenty of Mustella tests failing ;-) But those failures
> don't seem to be related to TLF, as far as I can tell.
> 
> So, you're 0.5 errors and 4 failures away from "being done"!
> 
> EdB
> 
> 
> 
> On Mon, Dec 29, 2014 at 8:46 PM, Harbs <ha...@gmail.com> wrote:
>> I thought I remembered that besides the unit test, there were mustella tests failing.
>> 
>> If not, all the better… ;-)
>> 
>> On Dec 29, 2014, at 9:34 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>> 
>>> Just curious, why are you looking at Mustella tests? There don't seem
>>> to be Mustella tests failing in a manner that would indicate a problem
>>> with TLF.
>>> 
>>> EdB
>>> 
>>> 
>>> 
>>> On Mon, Dec 29, 2014 at 7:41 PM, Harbs <ha...@gmail.com> wrote:
>>>> Is there a way to see what Mustella tests are failing on the CI server? I’d rather know what I’m dealing with before trying to run the full suite of tests on a local machine…
>>>> 
>>>> On Dec 29, 2014, at 8:08 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>>> 
>>>>> Just ran again with 1.8, got the error. Then with 1.6: no error. I
>>>>> threw in 1.7 for good measure: zero errors.
>>>>> 
>>>>> EdB
>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> 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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Oh, there are plenty of Mustella tests failing ;-) But those failures
don't seem to be related to TLF, as far as I can tell.

So, you're 0.5 errors and 4 failures away from "being done"!

EdB



On Mon, Dec 29, 2014 at 8:46 PM, Harbs <ha...@gmail.com> wrote:
> I thought I remembered that besides the unit test, there were mustella tests failing.
>
> If not, all the better… ;-)
>
> On Dec 29, 2014, at 9:34 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>
>> Just curious, why are you looking at Mustella tests? There don't seem
>> to be Mustella tests failing in a manner that would indicate a problem
>> with TLF.
>>
>> EdB
>>
>>
>>
>> On Mon, Dec 29, 2014 at 7:41 PM, Harbs <ha...@gmail.com> wrote:
>>> Is there a way to see what Mustella tests are failing on the CI server? I’d rather know what I’m dealing with before trying to run the full suite of tests on a local machine…
>>>
>>> On Dec 29, 2014, at 8:08 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>>
>>>> Just ran again with 1.8, got the error. Then with 1.6: no error. I
>>>> threw in 1.7 for good measure: zero errors.
>>>>
>>>> EdB
>>>>
>>>>
>>>
>>
>>
>>
>> --
>> 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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

I thought I remembered that besides the unit test, there were mustella tests failing.

If not, all the better… ;-)

On Dec 29, 2014, at 9:34 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> Just curious, why are you looking at Mustella tests? There don't seem
> to be Mustella tests failing in a manner that would indicate a problem
> with TLF.
> 
> EdB
> 
> 
> 
> On Mon, Dec 29, 2014 at 7:41 PM, Harbs <ha...@gmail.com> wrote:
>> Is there a way to see what Mustella tests are failing on the CI server? I’d rather know what I’m dealing with before trying to run the full suite of tests on a local machine…
>> 
>> On Dec 29, 2014, at 8:08 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>> 
>>> Just ran again with 1.8, got the error. Then with 1.6: no error. I
>>> threw in 1.7 for good measure: zero errors.
>>> 
>>> EdB
>>> 
>>> 
>> 
> 
> 
> 
> -- 
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Just curious, why are you looking at Mustella tests? There don't seem
to be Mustella tests failing in a manner that would indicate a problem
with TLF.

EdB



On Mon, Dec 29, 2014 at 7:41 PM, Harbs <ha...@gmail.com> wrote:
> Is there a way to see what Mustella tests are failing on the CI server? I’d rather know what I’m dealing with before trying to run the full suite of tests on a local machine…
>
> On Dec 29, 2014, at 8:08 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>
>> Just ran again with 1.8, got the error. Then with 1.6: no error. I
>> threw in 1.7 for good measure: zero errors.
>>
>> EdB
>>
>>
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

Is there a way to see what Mustella tests are failing on the CI server? I’d rather know what I’m dealing with before trying to run the full suite of tests on a local machine…

On Dec 29, 2014, at 8:08 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> Just ran again with 1.8, got the error. Then with 1.6: no error. I
> threw in 1.7 for good measure: zero errors.
> 
> EdB
> 
>

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Just ran again with 1.8, got the error. Then with 1.6: no error. I
threw in 1.7 for good measure: zero errors.

EdB



On Mon, Dec 29, 2014 at 6:04 PM, Harbs <ha...@gmail.com> wrote:
> Weird. I think my machine (Mac 10.9.5) uses Java 1.6.
>
> I get the error.
>
> On Dec 29, 2014, at 3:47 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>
>> Fun fact: when run with Java (1.)6, I get:
>>
>> Tests run: 428, Failures: 5, Errors: 0, Skipped: 41, Time elapsed: 246.937 sec
>>
>> Since the Windows build machine also runs Java (1.)6, the error seems
>> to correlate to the Java edition?
>>
>> Ed
>>
>> On Mon, Dec 29, 2014 at 2:28 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>>> On my Mac, this is the current status:
>>>
>>> Tests run: 428, Failures: 4, Errors: 1, Skipped: 41, Time elapsed: 253.360 sec
>>>
>>> EdB
>>>
>>>
>>>
>>> On Mon, Dec 29, 2014 at 11:01 AM, Harbs <ha...@gmail.com> wrote:
>>>> I’ve made some more progress. We’re down to 5 failures and 1 error:
>>>> [flexunit] Suite: UnitTest.Tests.OperationTest
>>>> [flexunit] Tests run: 47, Failures: 2, Errors: 0, Skipped: 2, Time elapsed: 5.002 sec
>>>> [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>>> [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.409 sec
>>>> [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
>>>> [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.947 sec
>>>> [flexunit] Suite: UnitTest.Tests.TabTest
>>>> [flexunit] Tests run: 19, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 0.713 sec
>>>> [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.794 sec
>>>> [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>>> [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.374 sec
>>>> [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>>> [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.158 sec
>>>> [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
>>>> [flexunit] Suite: UnitTest.Tests.AllEventTest
>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.729 sec
>>>> [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 0.274 sec
>>>> [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>>> [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.178 sec
>>>> [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>>> [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.436 sec
>>>> [flexunit] Suite: UnitTest.Tests.FloatTest
>>>> [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.313 sec
>>>> [flexunit] Suite: UnitTest.Tests.AttributeTest
>>>> [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.778 sec
>>>> [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>>> [flexunit] Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.267 sec
>>>> [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>>> [flexunit] Tests run: 25, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.772 sec
>>>> [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>>> [flexunit] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.549 sec
>>>> [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.040 sec
>>>> [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>>> [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.430 sec
>>>> [flexunit] Suite: UnitTest.Tests.BoxTest
>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.116 sec
>>>> [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.738 sec
>>>> [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>>> [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 78.049 sec
>>>> [flexunit] Suite: UnitTest.Tests.CompositionTest
>>>> [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 17.595 sec
>>>> [flexunit] Results :
>>>> [flexunit] Tests run: 428, Failures: 5, Errors: 1, Skipped: 41, Time elapsed: 184.707 sec
>>>> On Dec 24, 2014, at 9:13 PM, Harbs <ha...@gmail.com> wrote:
>>>>
>>>>> Here’s the current results. I’ll start with the OperationTest results. There’s a good chance that the other issues are related to the one I just fixed...
>>>>>
>>>>> [flexunit] Suite: UnitTest.Tests.OperationTest
>>>>> [flexunit] Tests run: 47, Failures: 4, Errors: 3, Skipped: 2, Time elapsed: 5.089 sec
>>>>> [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>>>> [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.339 sec
>>>>> [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 2.887 sec
>>>>> [flexunit] Suite: UnitTest.Tests.TabTest
>>>>> [flexunit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.543 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.767 sec
>>>>> [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>>>> [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.376 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>>>> [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.152 sec
>>>>> [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllEventTest
>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.695 sec
>>>>> [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 1.998 sec
>>>>> [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>>>> [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.173 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>>>> [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.313 sec
>>>>> [flexunit] Suite: UnitTest.Tests.FloatTest
>>>>> [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.469 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AttributeTest
>>>>> [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.421 sec
>>>>> [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>>>> [flexunit] Tests run: 23, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 1.273 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>>>> [flexunit] Tests run: 25, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 1.363 sec
>>>>> [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec
>>>>> [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>>>> [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.769 sec
>>>>> [flexunit] Suite: UnitTest.Tests.BoxTest
>>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.201 sec
>>>>> [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.951 sec
>>>>> [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>>>> [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 113.957 sec
>>>>> [flexunit] Suite: UnitTest.Tests.CompositionTest
>>>>> [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 3.929 sec
>>>>> [flexunit]
>>>>> [flexunit] Results :
>>>>> [flexunit]
>>>>> [flexunit] Tests run: 428, Failures: 6, Errors: 5, Skipped: 41, Time elapsed: 177.319 sec
>>>>> [flexunit]
>>>>> On Dec 24, 2014, at 9:09 PM, Harbs <ha...@gmail.com> wrote:
>>>>>
>>>>>> I’m running the Unit Tests right now. I’ll see what comes up…
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> 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
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Harbs <ha...@gmail.com>.

Weird. I think my machine (Mac 10.9.5) uses Java 1.6.

I get the error.

On Dec 29, 2014, at 3:47 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:

> Fun fact: when run with Java (1.)6, I get:
> 
> Tests run: 428, Failures: 5, Errors: 0, Skipped: 41, Time elapsed: 246.937 sec
> 
> Since the Windows build machine also runs Java (1.)6, the error seems
> to correlate to the Java edition?
> 
> Ed
> 
> On Mon, Dec 29, 2014 at 2:28 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>> On my Mac, this is the current status:
>> 
>> Tests run: 428, Failures: 4, Errors: 1, Skipped: 41, Time elapsed: 253.360 sec
>> 
>> EdB
>> 
>> 
>> 
>> On Mon, Dec 29, 2014 at 11:01 AM, Harbs <ha...@gmail.com> wrote:
>>> I’ve made some more progress. We’re down to 5 failures and 1 error:
>>> [flexunit] Suite: UnitTest.Tests.OperationTest
>>> [flexunit] Tests run: 47, Failures: 2, Errors: 0, Skipped: 2, Time elapsed: 5.002 sec
>>> [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>> [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.409 sec
>>> [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
>>> [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.947 sec
>>> [flexunit] Suite: UnitTest.Tests.TabTest
>>> [flexunit] Tests run: 19, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 0.713 sec
>>> [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.794 sec
>>> [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>> [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.374 sec
>>> [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>> [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.158 sec
>>> [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
>>> [flexunit] Suite: UnitTest.Tests.AllEventTest
>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.729 sec
>>> [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 0.274 sec
>>> [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>> [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.178 sec
>>> [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>> [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.436 sec
>>> [flexunit] Suite: UnitTest.Tests.FloatTest
>>> [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.313 sec
>>> [flexunit] Suite: UnitTest.Tests.AttributeTest
>>> [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.778 sec
>>> [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>> [flexunit] Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.267 sec
>>> [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>> [flexunit] Tests run: 25, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.772 sec
>>> [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>> [flexunit] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.549 sec
>>> [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.040 sec
>>> [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>> [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.430 sec
>>> [flexunit] Suite: UnitTest.Tests.BoxTest
>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.116 sec
>>> [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.738 sec
>>> [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>> [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 78.049 sec
>>> [flexunit] Suite: UnitTest.Tests.CompositionTest
>>> [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 17.595 sec
>>> [flexunit] Results :
>>> [flexunit] Tests run: 428, Failures: 5, Errors: 1, Skipped: 41, Time elapsed: 184.707 sec
>>> On Dec 24, 2014, at 9:13 PM, Harbs <ha...@gmail.com> wrote:
>>> 
>>>> Here’s the current results. I’ll start with the OperationTest results. There’s a good chance that the other issues are related to the one I just fixed...
>>>> 
>>>> [flexunit] Suite: UnitTest.Tests.OperationTest
>>>> [flexunit] Tests run: 47, Failures: 4, Errors: 3, Skipped: 2, Time elapsed: 5.089 sec
>>>> [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>>> [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.339 sec
>>>> [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec
>>>> [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 2.887 sec
>>>> [flexunit] Suite: UnitTest.Tests.TabTest
>>>> [flexunit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.543 sec
>>>> [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.767 sec
>>>> [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>>> [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.376 sec
>>>> [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>>> [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.152 sec
>>>> [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
>>>> [flexunit] Suite: UnitTest.Tests.AllEventTest
>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.695 sec
>>>> [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 1.998 sec
>>>> [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>>> [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.173 sec
>>>> [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>>> [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.313 sec
>>>> [flexunit] Suite: UnitTest.Tests.FloatTest
>>>> [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.469 sec
>>>> [flexunit] Suite: UnitTest.Tests.AttributeTest
>>>> [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.421 sec
>>>> [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>>> [flexunit] Tests run: 23, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 1.273 sec
>>>> [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>>> [flexunit] Tests run: 25, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 1.363 sec
>>>> [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec
>>>> [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>>> [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
>>>> [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>>> [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.769 sec
>>>> [flexunit] Suite: UnitTest.Tests.BoxTest
>>>> [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.201 sec
>>>> [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>>> [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.951 sec
>>>> [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>>> [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 113.957 sec
>>>> [flexunit] Suite: UnitTest.Tests.CompositionTest
>>>> [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 3.929 sec
>>>> [flexunit]
>>>> [flexunit] Results :
>>>> [flexunit]
>>>> [flexunit] Tests run: 428, Failures: 6, Errors: 5, Skipped: 41, Time elapsed: 177.319 sec
>>>> [flexunit]
>>>> On Dec 24, 2014, at 9:09 PM, Harbs <ha...@gmail.com> wrote:
>>>> 
>>>>> I’m running the Unit Tests right now. I’ll see what comes up…
>>>> 
>>> 
>> 
>> 
>> 
>> --
>> 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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Fun fact: when run with Java (1.)6, I get:

Tests run: 428, Failures: 5, Errors: 0, Skipped: 41, Time elapsed: 246.937 sec

Since the Windows build machine also runs Java (1.)6, the error seems
to correlate to the Java edition?

Ed

On Mon, Dec 29, 2014 at 2:28 PM, Erik de Bruin <er...@ixsoftware.nl> wrote:
> On my Mac, this is the current status:
>
> Tests run: 428, Failures: 4, Errors: 1, Skipped: 41, Time elapsed: 253.360 sec
>
> EdB
>
>
>
> On Mon, Dec 29, 2014 at 11:01 AM, Harbs <ha...@gmail.com> wrote:
>> I’ve made some more progress. We’re down to 5 failures and 1 error:
>>  [flexunit] Suite: UnitTest.Tests.OperationTest
>>  [flexunit] Tests run: 47, Failures: 2, Errors: 0, Skipped: 2, Time elapsed: 5.002 sec
>>  [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>  [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.409 sec
>>  [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
>>  [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.947 sec
>>  [flexunit] Suite: UnitTest.Tests.TabTest
>>  [flexunit] Tests run: 19, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 0.713 sec
>>  [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.794 sec
>>  [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>  [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.374 sec
>>  [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>  [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.158 sec
>>  [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
>>  [flexunit] Suite: UnitTest.Tests.AllEventTest
>>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.729 sec
>>  [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 0.274 sec
>>  [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>  [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.178 sec
>>  [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>  [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.436 sec
>>  [flexunit] Suite: UnitTest.Tests.FloatTest
>>  [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.313 sec
>>  [flexunit] Suite: UnitTest.Tests.AttributeTest
>>  [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.778 sec
>>  [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>  [flexunit] Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.267 sec
>>  [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>  [flexunit] Tests run: 25, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.772 sec
>>  [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>  [flexunit] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.549 sec
>>  [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.040 sec
>>  [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>  [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.430 sec
>>  [flexunit] Suite: UnitTest.Tests.BoxTest
>>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.116 sec
>>  [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.738 sec
>>  [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>  [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 78.049 sec
>>  [flexunit] Suite: UnitTest.Tests.CompositionTest
>>  [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 17.595 sec
>>  [flexunit] Results :
>>  [flexunit] Tests run: 428, Failures: 5, Errors: 1, Skipped: 41, Time elapsed: 184.707 sec
>> On Dec 24, 2014, at 9:13 PM, Harbs <ha...@gmail.com> wrote:
>>
>>> Here’s the current results. I’ll start with the OperationTest results. There’s a good chance that the other issues are related to the one I just fixed...
>>>
>>> [flexunit] Suite: UnitTest.Tests.OperationTest
>>>  [flexunit] Tests run: 47, Failures: 4, Errors: 3, Skipped: 2, Time elapsed: 5.089 sec
>>>  [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>>  [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.339 sec
>>>  [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec
>>>  [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 2.887 sec
>>>  [flexunit] Suite: UnitTest.Tests.TabTest
>>>  [flexunit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.543 sec
>>>  [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.767 sec
>>>  [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>>  [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.376 sec
>>>  [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>>  [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.152 sec
>>>  [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
>>>  [flexunit] Suite: UnitTest.Tests.AllEventTest
>>>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.695 sec
>>>  [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 1.998 sec
>>>  [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>>  [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.173 sec
>>>  [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>>  [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.313 sec
>>>  [flexunit] Suite: UnitTest.Tests.FloatTest
>>>  [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.469 sec
>>>  [flexunit] Suite: UnitTest.Tests.AttributeTest
>>>  [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.421 sec
>>>  [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>>  [flexunit] Tests run: 23, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 1.273 sec
>>>  [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>>  [flexunit] Tests run: 25, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 1.363 sec
>>>  [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec
>>>  [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
>>>  [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>>  [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.769 sec
>>>  [flexunit] Suite: UnitTest.Tests.BoxTest
>>>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.201 sec
>>>  [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.951 sec
>>>  [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>>  [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 113.957 sec
>>>  [flexunit] Suite: UnitTest.Tests.CompositionTest
>>>  [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 3.929 sec
>>>  [flexunit]
>>>  [flexunit] Results :
>>>  [flexunit]
>>>  [flexunit] Tests run: 428, Failures: 6, Errors: 5, Skipped: 41, Time elapsed: 177.319 sec
>>>  [flexunit]
>>> On Dec 24, 2014, at 9:09 PM, Harbs <ha...@gmail.com> wrote:
>>>
>>>> I’m running the Unit Tests right now. I’ll see what comes up…
>>>
>>
>
>
>
> --
> 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

Re: TLF status was: [DISCUSS] Release Apache Flex 4.14.0

Posted by Erik de Bruin <er...@ixsoftware.nl>.

On my Mac, this is the current status:

Tests run: 428, Failures: 4, Errors: 1, Skipped: 41, Time elapsed: 253.360 sec

EdB



On Mon, Dec 29, 2014 at 11:01 AM, Harbs <ha...@gmail.com> wrote:
> I’ve made some more progress. We’re down to 5 failures and 1 error:
>  [flexunit] Suite: UnitTest.Tests.OperationTest
>  [flexunit] Tests run: 47, Failures: 2, Errors: 0, Skipped: 2, Time elapsed: 5.002 sec
>  [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>  [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.409 sec
>  [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.033 sec
>  [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.947 sec
>  [flexunit] Suite: UnitTest.Tests.TabTest
>  [flexunit] Tests run: 19, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 0.713 sec
>  [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.794 sec
>  [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>  [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.374 sec
>  [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>  [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.158 sec
>  [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec
>  [flexunit] Suite: UnitTest.Tests.AllEventTest
>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.729 sec
>  [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 0.274 sec
>  [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>  [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.178 sec
>  [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>  [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.436 sec
>  [flexunit] Suite: UnitTest.Tests.FloatTest
>  [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.313 sec
>  [flexunit] Suite: UnitTest.Tests.AttributeTest
>  [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.778 sec
>  [flexunit] Suite: UnitTest.Tests.FlowModelTest
>  [flexunit] Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.267 sec
>  [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>  [flexunit] Tests run: 25, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.772 sec
>  [flexunit] Suite: UnitTest.Tests.WritingModeTest
>  [flexunit] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.549 sec
>  [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.040 sec
>  [flexunit] Suite: UnitTest.Tests.ScrollingTest
>  [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.430 sec
>  [flexunit] Suite: UnitTest.Tests.BoxTest
>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.116 sec
>  [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.738 sec
>  [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>  [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 78.049 sec
>  [flexunit] Suite: UnitTest.Tests.CompositionTest
>  [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 17.595 sec
>  [flexunit] Results :
>  [flexunit] Tests run: 428, Failures: 5, Errors: 1, Skipped: 41, Time elapsed: 184.707 sec
> On Dec 24, 2014, at 9:13 PM, Harbs <ha...@gmail.com> wrote:
>
>> Here’s the current results. I’ll start with the OperationTest results. There’s a good chance that the other issues are related to the one I just fixed...
>>
>> [flexunit] Suite: UnitTest.Tests.OperationTest
>>  [flexunit] Tests run: 47, Failures: 4, Errors: 3, Skipped: 2, Time elapsed: 5.089 sec
>>  [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest
>>  [flexunit] Tests run: 36, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 2.339 sec
>>  [flexunit] Suite: UnitTest.Tests.CrossContainerTest
>>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 sec
>>  [flexunit] Suite: UnitTest.Tests.AllParaAttributeTest
>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 2.887 sec
>>  [flexunit] Suite: UnitTest.Tests.TabTest
>>  [flexunit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.543 sec
>>  [flexunit] Suite: UnitTest.Tests.AllContAttributeTest
>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.767 sec
>>  [flexunit] Suite: UnitTest.Tests.EventOverrideTest
>>  [flexunit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 12, Time elapsed: 0.376 sec
>>  [flexunit] Suite: UnitTest.Tests.AccessibilityMethodsTest
>>  [flexunit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.152 sec
>>  [flexunit] Suite: UnitTest.Tests.FactoryImportTest
>>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
>>  [flexunit] Suite: UnitTest.Tests.AllEventTest
>>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 0.695 sec
>>  [flexunit] Suite: UnitTest.Tests.BoundsAndAlignmentTest
>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 6, Time elapsed: 1.998 sec
>>  [flexunit] Suite: UnitTest.Tests.TextFlowEditTest
>>  [flexunit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.173 sec
>>  [flexunit] Suite: UnitTest.Tests.ContainerTypeTest
>>  [flexunit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.313 sec
>>  [flexunit] Suite: UnitTest.Tests.FloatTest
>>  [flexunit] Tests run: 56, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 21.469 sec
>>  [flexunit] Suite: UnitTest.Tests.AttributeTest
>>  [flexunit] Tests run: 44, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 1.421 sec
>>  [flexunit] Suite: UnitTest.Tests.FlowModelTest
>>  [flexunit] Tests run: 23, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 1.273 sec
>>  [flexunit] Suite: UnitTest.Tests.ElementOperationTest
>>  [flexunit] Tests run: 25, Failures: 0, Errors: 1, Skipped: 1, Time elapsed: 1.363 sec
>>  [flexunit] Suite: UnitTest.Tests.WritingModeTest
>>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec
>>  [flexunit] Suite: UnitTest.Tests.UndoRedoTest
>>  [flexunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
>>  [flexunit] Suite: UnitTest.Tests.ScrollingTest
>>  [flexunit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 4.769 sec
>>  [flexunit] Suite: UnitTest.Tests.BoxTest
>>  [flexunit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.201 sec
>>  [flexunit] Suite: UnitTest.Tests.AllCharAttributeTest
>>  [flexunit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.951 sec
>>  [flexunit] Suite: UnitTest.Tests.ContainerAttributeTest
>>  [flexunit] Tests run: 31, Failures: 0, Errors: 0, Skipped: 2, Time elapsed: 113.957 sec
>>  [flexunit] Suite: UnitTest.Tests.CompositionTest
>>  [flexunit] Tests run: 24, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 3.929 sec
>>  [flexunit]
>>  [flexunit] Results :
>>  [flexunit]
>>  [flexunit] Tests run: 428, Failures: 6, Errors: 5, Skipped: 41, Time elapsed: 177.319 sec
>>  [flexunit]
>> On Dec 24, 2014, at 9:09 PM, Harbs <ha...@gmail.com> wrote:
>>
>>> I’m running the Unit Tests right now. I’ll see what comes up…
>>
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl