On 1/29/15, 12:38 AM, "Harbs" wrote:
>The last build has just those two tests failing:
>http://apacheflexbuild.cloudapp.net:8080/job/flex-tlf/321/
>
>There were others as well.
OK, well, at least we know it isn’t a side-effect.
I poked around the code a bit. Have you tried adding more assert
;>
>>> On Jan 28, 2015, at 11:00 PM, Chris Martin wrote:
>>>
>>>> How can I run these tests locally on my machine? :)
>>>>
>>>> Chris
>>>>
>>>>> From: harbs.li...@gmail.com
>>>>> Subject: Re: Failing TLF Bu
://apache-flex-development.247.n4.nabble.com/Failing-TLF-Builds-tp44697p44742.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
s Martin wrote:
>>
>>> How can I run these tests locally on my machine? :)
>>>
>>> Chris
>>>
>>>> From: harbs.li...@gmail.com
>>>> Subject: Re: Failing TLF Builds
>>>> Date: Wed, 28 Jan 2015 22:31:30 +0200
>>>> To: dev@fl
.
Chris
> Subject: Re: Failing TLF Builds
> From: harbs.li...@gmail.com
> Date: Wed, 28 Jan 2015 23:02:16 +0200
> To: dev@flex.apache.org
>
> run “ant all” on TLF.
>
> On Jan 28, 2015, at 11:00 PM, Chris Martin wrote:
>
> > How can I run these tests locally
Harbs" wrote:
>run “ant all” on TLF.
>
>On Jan 28, 2015, at 11:00 PM, Chris Martin wrote:
>
>> How can I run these tests locally on my machine? :)
>>
>> Chris
>>
>>> From: harbs.li...@gmail.com
>>> Subject: Re: Failing TLF Builds
>&
run “ant all” on TLF.
On Jan 28, 2015, at 11:00 PM, Chris Martin wrote:
> How can I run these tests locally on my machine? :)
>
> Chris
>
>> From: harbs.li...@gmail.com
>> Subject: Re: Failing TLF Builds
>> Date: Wed, 28 Jan 2015 22:31:30 +0200
>> To: dev@
How can I run these tests locally on my machine? :)
Chris
> From: harbs.li...@gmail.com
> Subject: Re: Failing TLF Builds
> Date: Wed, 28 Jan 2015 22:31:30 +0200
> To: dev@flex.apache.org
>
> So maybe this is something that needs to be fixed to make the tests more
> s
So maybe this is something that needs to be fixed to make the tests more stable.
On Jan 28, 2015, at 10:02 PM, Alex Harui wrote:
> Actually, in the little I’ve looked at the test so far, I
> have concerns that a failing test could leave the suite in a bad state so
> the only important thing is t
They all pass for me:
[flexunit] Tests run: 428, Failures: 0, Errors: 0, Skipped: 22, Time elapsed:
340.071 sec
On Jan 28, 2015, at 10:02 PM, Alex Harui wrote:
> I’m also seeing that columnContainerBreakTest2000 failed in the last two
> runs. It and several others are failing for me too. Are
I’m also seeing that columnContainerBreakTest2000 failed in the last two
runs. It and several others are failing for me too. Are they passing for
you? Maybe if I look to see why they fail it will shed light on the
Arrows test. Actually, in the little I’ve looked at the test so far, I
have conce
There are about 20 tests that are ignored because they had issues when they
were ported.
My concern is actually two specific tests:
GeneralFunctionsTest.arrowDown
GeneralFunctionsTest.arrowUp
These are passing for me locally, but are failing on the CI server.
The reason I suspect there’s a rea
I just ran the tests myself. I get:
[flexunit] FlexUnit test spanElementReplaceTextInvalidPos in suite
UnitTest.Tests.ElementOperationTest was ignored.
[flexunit] FlexUnit test testAllEnumProps in suite
UnitTest.Tests.AllParaAttributeTest was ignored.
[flexunit] FlexUnit test endTabLongStringTe
Arg!
Now the arrow tests are failing again.
I have a feeling that this is a legitimate failure, but it’s a sometimes/some
machine failure.
If someone is constantly getting these failures, I have something I’d like them
to try.
Thanks,
Harbs
On Jan 28, 2015, at 9:23 AM, Harbs wrote:
> At le
At least the arrow tests are passing now.
I just disabled the paddingBottomTest.
On Jan 28, 2015, at 6:39 AM, Alex Harui wrote:
> That last failure was after rebooting.
>
> On 1/27/15, 11:20 AM, "Alex Harui" wrote:
>
>> If Erik doesn’t get to it first, I’ll try to remember to reboot the
>> m
That last failure was after rebooting.
On 1/27/15, 11:20 AM, "Alex Harui" wrote:
>If Erik doesn’t get to it first, I’ll try to remember to reboot the
>mustella server tonight (about 10 hours from now).
>
>On 1/27/15, 11:02 AM, "Harbs" wrote:
>
>>The last three builds of TLF failed on Jenkins. T
On 1/27/15, 11:49 AM, "Erik de Bruin" wrote:
>The TLF tests are not running on the Mustella VM, but on the Builds
>machine.
Ah, ok. I won’t be able to reboot that one either until about 9 hours
from now. If you want to do it sooner, I can post the credentials again
on the private list.
-Ale
The TLF tests are not running on the Mustella VM, but on the Builds
machine.
EdB
On Tuesday, January 27, 2015, Alex Harui wrote:
> If Erik doesn’t get to it first, I’ll try to remember to reboot the
> mustella server tonight (about 10 hours from now).
>
> On 1/27/15, 11:02 AM, "Harbs" >
> wro
rzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Failing-TLF-Builds-tp44697p44703.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
If Erik doesn’t get to it first, I’ll try to remember to reboot the
mustella server tonight (about 10 hours from now).
On 1/27/15, 11:02 AM, "Harbs" wrote:
>The last three builds of TLF failed on Jenkins. There’s three tests
>failing on the server, but are passing locally for me.
>
>Is there any
The last three builds of TLF failed on Jenkins. There’s three tests failing on
the server, but are passing locally for me.
Is there any way to restart the server to try to get them to pass? Or should we
just disable the tests on the server?
Maybe there’s some way that we can include the problem
21 matches
Mail list logo
