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

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 o

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

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 wrote: > Ah,

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

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.Gen

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

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 wrote: > ... > [flexunit] Suite: UnitTest.Tests.GeneralFunctionsTest > [flexunit] Tests run: 36, Failures: 2, Errors: 0, Skipped: 0, Time > elapsed: 3.603 sec > ... > [fl

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

... [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 ... [fl

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

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 wrote: > Harbs, > > When I ran the tests with Java 1.8 on my Mac (Yosemite), I still see failures: > > ... > [flexunit] Suite: UnitTest.Te

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

Erik, I have just tried on Windows with Java 1.8 and I don't have any errors... Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p44073.html Sent from the Apach

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

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

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

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 [flexun

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

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 n

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

Piotr, I have a question: I’m looking at the EventOverrideTest. The old tests look like they were run via xml like this: true false empty.xml false false These values were different for the different test cases. How is TestData.overrideEditManager suppo

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

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 wrote: > Harbs, > > Congratulations!

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

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

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

Harbs, Congratulations! You are absolutly the best! :) Do you still want me to look into tests ordering? Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p44

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

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:

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

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 oper

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

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 [fle

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

Jup, that last commit took care of that "problem" ;-) EdB On Tue, Dec 30, 2014 at 12:35 PM, Harbs 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, 2

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

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 wrote: > I got: > > "insertTextTest in suite UnitTest.Tests.OperationTest" > > on bo

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

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 wrote: > The consistent failure was OperationTest.ins

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

Ok. I will have some time on Saturday or Sunday and will try to look into that. - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43995.html Sent from the Apache Flex

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

It did not help. On Dec 30, 2014, at 12:45 PM, piotrz wrote: > Put it in the WritingModeTest > > [TestCase(order=1)] > public class WritingModeTest

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

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 piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabb

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

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 wrote: > Ok so try to add [TestCase(order=1)] tag to WritingModeT

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

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 wrote: > Java 1.8: > > Tests

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

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

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

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 wrote: > BTW, I just made another commit. The only real error left s

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

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 wrote: > I tried that. It did not make a difference. > > On Dec 30, 2014, at 12:17 PM, piotrz wrote: > >> Try to put public var writingModeTest:Writi

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

I tried that. It did not make a difference. On Dec 30, 2014, at 12:17 PM, piotrz 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 > piotrzarzyck...

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

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 piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Relea

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

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 wrote: > Okay, but how do we change the order in AllTestsSuite? I want t

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

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 wrote: > Hi Harbs, > > Yes you can order items in your unit test class. Take a look [1] > >

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

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 piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-R

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

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 Parag

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

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 su

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

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 wrote: > Oh, there are plenty of Mustella tests failing ;-) But those failures > don't seem to be related to TLF,

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

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 wrote: > I thought I remembered that besides the unit test, ther

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

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 wrote: > Just curious, why are you looking at Mustella tests? There don't seem > to be Mustella tests failing in a manner that would indi

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

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 wrote: > Is there a way to see what Mustella tests are failing on the CI server? I’d > rather know

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

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

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

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 wrote: > Just ran again with 1.8, got the error. Then with 1.6: no error. I

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

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 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,

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

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 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 wrote: >

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

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 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 run

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

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 wrote: > On my Mac

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

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 wrote: > I’ve made some more progress. We’re down to 5 failures and 1 error: > [flexunit] Suite: UnitTest.Tests.OperationTest > [

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

Hi Harbs, It's even better - In jenkins build we do not have these 1 error :) Great job! Piotr - Apache Flex PMC piotrzarzyck...@gmail.com -- View this message in context: http://apache-flex-development.247.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43943.html Sent from

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,