On 5/27/15, 1:11 AM, "Tom Chiverton" wrote:
>
>It seems happier overall now since you threatened it any way :-)
I know for sure there was at least one other time where, without any code
changes, things started working again for a while. So I’ll bet we start
seeing the failures again eventually
On 26/05/15 16:46, Alex Harui wrote:
On 5/26/15, 2:49 AM, "Tom Chiverton" wrote:
But the current run has already logged some failures:
The only thing that really matters is the final result. Some tests always
fail on the first run and pass on the second run when only failing tests
are run.
On 5/26/15, 2:49 AM, "Tom Chiverton" wrote:
>But the current run has already logged some failures:
The only thing that really matters is the final result. Some tests always
fail on the first run and pass on the second run when only failing tests
are run. Usually that’s because some previous
On 26/05/15 10:49, Tom Chiverton wrote:
On 24/05/15 17:53, OmPrakash Muppirala wrote:
Great, I nominate you to fix all Mustella tests going forward
He does have the magic touch :-)
This might be player version related if it ran OK the run before ?
And the most recent run has passed f
+1 lol
-Mark
-Original Message-
From: omup...@gmail.com [mailto:omup...@gmail.com] On Behalf Of OmPrakash
Muppirala
Sent: Sunday, May 24, 2015 12:53 PM
To: dev@flex.apache.org
Subject: Re: Mustella SDK tests
Great, I nominate you to fix all Mustella tests going forward ;-)
On 24/05/15 17:53, OmPrakash Muppirala wrote:
Great, I nominate you to fix all Mustella tests going forward
He does have the magic touch :-)
But the current run has already logged some failures:
[java] Wrote file:
c:/jenkins_slave/workspace/flex-sdk_mustella/mustella/tests/gumbo/componen
Great, I nominate you to fix all Mustella tests going forward ;-)
On May 23, 2015 9:52 PM, "Alex Harui" wrote:
> Well, I must have magical powers because I did some digging last night and
> upon running a test that failed in the main SDK run in FDB, it passed.
> Then I restarted the main SDK run
Well, I must have magical powers because I did some digging last night and
upon running a test that failed in the main SDK run in FDB, it passed.
Then I restarted the main SDK run and it started passing!
I’ve put some diagnostic trace statements in CompareBitmap so when it
starts failing again we
I have shut down jenkins slave agent so no mustella runs for a while.
Please don’t restart jenkins as I may not have time to finish the
investigation tonight and will continue over the weekend. I’ll restart it
myself when I’m done digging.
Thanks,
-Alex
On 5/22/15, 5:47 AM, "Alex Harui" wrote:
OK, go shut down Jenkins. I hope to get this FlexJS fix in today and then
I’ll look at Mustella.
-Alex
On 5/22/15, 5:31 AM, "Tom Chiverton" wrote:
>
>On 21/05/15 16:13, Alex Harui wrote:
>> On 5/21/15, 8:01 AM, "Tom Chiverton" wrote:
>>
>>> I've pressed 'keep forever' on
>>> http://flex-muste
On 21/05/15 16:13, Alex Harui wrote:
On 5/21/15, 8:01 AM, "Tom Chiverton" wrote:
I've pressed 'keep forever' on
http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/1484/
OK, not sure what that button does, but I need the workspace not the
artifacts.
Well the most recent build appears
On 5/21/15, 8:01 AM, "Tom Chiverton" wrote:
>I've pressed 'keep forever' on
>http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/1484/
OK, not sure what that button does, but I need the workspace not the
artifacts.
-Alex
I've pressed 'keep forever' on
http://flex-mustella.cloudapp.net/job/flex-sdk_mustella/1484/
Tom
On 21/05/15 13:43, Alex Harui wrote:
OK, I want to fix one more FlexJS bug first. Then we have to stop Jenkins
after an SDK run completes with failures so the SWFs are still sitting
around on the
On 5/21/15, 4:11 AM, "Tom Chiverton" wrote:
>Feel free to poke at it ;-)
OK, I want to fix one more FlexJS bug first. Then we have to stop Jenkins
after an SDK run completes with failures so the SWFs are still sitting
around on the machine.
>
>Would it maybe also be possible to run it in par
Feel free to poke at it ;-)
Would it maybe also be possible to run it in parallel on the other build
machine ?
That would rule out the issues we sometimes have where it's just
flex-mustella that has an issue and it fixes it self when it cycles
round to the same Player version again.
I think ap
On 5/20/15, 3:52 AM, "Tom Chiverton" wrote:
>Is it hard to kinda destroy the checkout and start again ?
Don’t know. I’m not sure the bitmap failures have anything to do with the
contents of the repo, but I could be wrong about that.
>
>We're going to struggle to do more releases if we have a
;
Reply-To: "dev@flex.apache.org <mailto:dev@flex.apache.org>"
mailto:dev@flex.apache.org>>
Date: Friday, May 15, 2015 at 1:24 AM
To: "dev@flex.apache.org <mailto:dev@flex.apache.org>"
mailto:dev@flex.apache.org>>
Subject: Mustella SDK tests
Can someone on
...@extravision.com>>
Reply-To: "dev@flex.apache.org<mailto:dev@flex.apache.org>"
mailto:dev@flex.apache.org>>
Date: Friday, May 15, 2015 at 1:24 AM
To: "dev@flex.apache.org<mailto:dev@flex.apache.org>"
mailto:dev@flex.apache.org>>
Subject: Mustella SDK tests
Can someone on a Windows machine try some of the following Mustella
tests ? They are consistently failing on the Jenkins job.
spark/core/fxg/properties/fxgtemplate_masks mask_clip_mask
spark/core/fxg/properties/fxgtemplate_tester
blend_mode_radial_gradient_blends_blend_difference_radialgradient
19 matches
Mail list logo
