Another update.
builds@a.o.: the broken SDK build this morning showed that the new
jobs work as expected (picked up broken-ness, emailed, re-ran when fix
was comitted and email when build succeeded), which gave me the
confidence to disable the 'old' jobs (names starting with capital F)
and put the
I'll try connecting from the office computer tomorrow and see if I have
better luck.
On 5/27/13 10:41 PM, "Erik de Bruin" wrote:
>Wait, I found the wonderful 'results.txt' that seems to contain a lot
>of the console output:
>
>
>=
>Failed:
>===
Wait, I found the wonderful 'results.txt' that seems to contain a lot
of the console output:
=
Failed:
=
components/Alert/Properties/Alert_Properties
Alert_layoutDirection_direction_rtl Failed
The last run was a full run. I started it manually in Cygwin. I'll do
that every day until Jenkins is ready to take over... and I hope I
don't forget to pull the latest source before I run it ;-)
EdB
On Tue, May 28, 2013 at 7:36 AM, Alex Harui wrote:
> But was the last run a full run or are yo
But was the last run a full run or are you mucking with Jenkins and Label
in the same directories? Any non-all run generally wipes out the
bad.png files from previous runs.
On 5/27/13 10:33 PM, "Erik de Bruin" wrote:
>Today is a busy day, so I won't be able to grab what you requested.
>Maybe
Today is a busy day, so I won't be able to grab what you requested.
Maybe Om can fetch it?
EdB
On Tue, May 28, 2013 at 7:22 AM, Alex Harui wrote:
> Couldn't get connected. But it sounds like other runs happened since
> which would have wiped out what I needed.
>
> Next time a full run complet
Couldn't get connected. But it sounds like other runs happened since
which would have wiped out what I needed.
Next time a full run completes, if you can package up the portion of the
console output that describes the failures (failures.txt only lists the
failing tests but doesn't tell me how the
I've posted the RDP login data to 'private', so you can have a look at
the setup for yourself.
EdB
On Mon, May 27, 2013 at 4:31 PM, Erik de Bruin wrote:
> Hold on to your hat, here is 'failures.txt':
>
>
> components/Alert/Properties/Alert_Properties
> Alert_layoutDirection_direction_rtl
> c
Hold on to your hat, here is 'failures.txt':
components/Alert/Properties/Alert_Properties Alert_layoutDirection_direction_rtl
components/Alert/Properties/Alert_Properties
Alert_layoutDirection_direction_rtl_with_alertIcon
components/Alert/Properties/Alert_Properties_Spark
Alert_layoutDirection_di
Can you post the portion of the console output that lists the failures?
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Erik de Bruin wrote:
The change of the Flash Player content debugger and the addition of
the localhost access has reduced the number of failures on the last
run
The change of the Flash Player content debugger and the addition of
the localhost access has reduced the number of failures on the last
run from 280 to 140. I'm now out of my depth on Mustella and I'll
leave the fixing of the rest to the pros ;-)
I will now install Jenkins and try to have it do a
By default mini_run should clean everything up before compiling and
running tests.
It'll be great to see this actually work!
On 5/26/13 11:06 AM, "Erik de Bruin" wrote:
>I was running 11.7 content debugger. Have now switched to
>11.1.whatever. Also installed Apache server, localhost is pointing
I was running 11.7 content debugger. Have now switched to
11.1.whatever. Also installed Apache server, localhost is pointing to
'mustella/tests'. I just started another run, let's see what that
gives us.
One question: after one run, before doing another, is there something
I need to 'clean up' or
Hi,
> This is running on a Windows Azure instance I'm setting up, not on
> builds.apache.org.
Sorry I thought it was on the apache build box.
> Setting up Apache as a web server won't too much trouble, especially since
> we only need localhost.
Yep.
Justin
What FlashPlayer version did you use? I think the bitmaps only work for
11.1/11.2. That might explain why there's a lot of gradient failures.
I guess at some point we should try to get all tests to pass on more
recent players.
On 5/25/13 1:28 AM, "Erik de Bruin" wrote:
>Next update:
>
>Infra
Justin,
On Saturday, May 25, 2013, Justin Mclean wrote:
> Hi,
>
> > Infra installed the Extension Manager, Jenkins job 'flex-sdk_release'
> > now runs cleanly.
> Nice one.
>
> > Mustella successfully completed a full run this night, taking a little
> > under 9 hours to complete.
> Ouch - we may h
Hi,
> Infra installed the Extension Manager, Jenkins job 'flex-sdk_release'
> now runs cleanly.
Nice one.
> Mustella successfully completed a full run this night, taking a little
> under 9 hours to complete.
Ouch - we may have to keep an eye on the queue as there's only one windows box
and it sh
Next update:
Infra installed the Extension Manager, Jenkins job 'flex-sdk_release'
now runs cleanly.
Mustella successfully completed a full run this night, taking a little
under 9 hours to complete. It reports 35,446 success and 228 failures.
I will need help fixing most of these (gradients and s
Looking into that next.
EdB
On Fri, May 24, 2013 at 5:19 PM, Alex Harui wrote:
> Nice!
>
> Are the FalconJX tests failing on your system as well or is this just the
> Jenkins run?
>
> On 5/24/13 7:01 AM, "Erik de Bruin" wrote:
>
>>A little update:
>>
>>- flex-tlf (-): succeeds
>>- flex-sdk (m
Nice!
Are the FalconJX tests failing on your system as well or is this just the
Jenkins run?
On 5/24/13 7:01 AM, "Erik de Bruin" wrote:
>A little update:
>
>- flex-tlf (-): succeeds
>- flex-sdk (main checkintests): succeeds
>- flex-sdk_release (release): waiting for Extension Manager install
>-
I want to use them (Very
> disapointing)
>
> Would have been the ideal setup for CI Flex builds :-|
>
> Chris
>
>
> Von: Erik de Bruin [e...@ixsoftware.nl]
> Gesendet: Freitag, 24. Mai 2013 16:01
> An: dev@flex.apache.org
Betreff: Re: Jenkins builds and Mustella
A little update:
- flex-tlf (-): succeeds
- flex-sdk (main checkintests): succeeds
- flex-sdk_release (release): waiting for Extension Manager install
- flex-sdk_asdoc (asdoc): succeeds
- flex-falcon (all) - succeeds, marked 'unstable' because som
A little update:
- flex-tlf (-): succeeds
- flex-sdk (main checkintests): succeeds
- flex-sdk_release (release): waiting for Extension Manager install
- flex-sdk_asdoc (asdoc): succeeds
- flex-falcon (all) - succeeds, marked 'unstable' because some
FalconJx tests fail
I'll let these run a week or
The only job I saw that had anything to do with release was one that
called 'source-release'.
The full 'release' task requires the Adobe Extension Manager, which
I've asked the people on the build list to install on 'windows1', like
they did for Pixelbender.
EdB
On Fri, May 24, 2013 at 1:23 AM
HI,
> - flex-sdk_release (release): fails, waiting for Extension Manager install
The release target was working before so all the bits should be there? I think
in order to do a release you have to do make main first?
Thanks,
Justin
I'm playing around with Cygwin and Mutt/Fetchmail for the patch server.
We'll see if it works or not.
On 5/23/13 11:28 AM, "Erik de Bruin" wrote:
>Spending Limit is 0 by default (first thing I checked when they asked
>for my creditcard for "verification" ;-)).
>
>My Windows lore is rather stale
On Thu, May 23, 2013 at 11:28 AM, Erik de Bruin wrote:
> Spending Limit is 0 by default (first thing I checked when they asked
> for my creditcard for "verification" ;-)).
>
> My Windows lore is rather stale after a couple of years on a Mac...
> does anyone have an idea on how to report on the Mu
Spending Limit is 0 by default (first thing I checked when they asked
for my creditcard for "verification" ;-)).
My Windows lore is rather stale after a couple of years on a Mac...
does anyone have an idea on how to report on the Mustella runs from
this VM to the dev list (or elsewhere)?
EdB
O
On Thu, May 23, 2013 at 10:57 AM, Erik de Bruin wrote:
> Om,
>
> Since you've looked at Azure before, maybe you can help with this:
>
> On our Enterprise MSDN subscription I have 1500 free 'small instance'
> hours per month. The VM I've set up is a 4 core, 7 GB 'large' machine.
> Best I can tell
Have we ever asked Apache Infra for a VM? I know they've given some to
other projects...
On Thu, May 23, 2013 at 1:57 PM, Erik de Bruin wrote:
> Om,
>
> Since you've looked at Azure before, maybe you can help with this:
>
> On our Enterprise MSDN subscription I have 1500 free 'small instance'
Om,
Since you've looked at Azure before, maybe you can help with this:
On our Enterprise MSDN subscription I have 1500 free 'small instance'
hours per month. The VM I've set up is a 4 core, 7 GB 'large' machine.
Best I can tell there is a 4x multiplier for that type of
instance/hour or 375 hours
Anything to make it easier to test using Mustella would be awesome. Thanks
:)
On Thu, May 23, 2013 at 1:40 PM, Alex Harui wrote:
> Excellent. Thanks for working on this stuff.
>
> Recently, I checked in some shell scripts that I only tested on Mac that
> take a patch file, run MustellaTestCho
Excellent. Thanks for working on this stuff.
Recently, I checked in some shell scripts that I only tested on Mac that
take a patch file, run MustellaTestChooser and run the tests it finds. It
expects 'git status' format which is different from 'git log' format, but
maybe you can leverage some of
On Thu, May 23, 2013 at 10:31 AM, Erik de Bruin wrote:
> Hi,
>
> Just to let you know what I'm working on:
>
> I'm working on the build machines to create new/updated Jenkins jobs
> for the following builds:
> - flex-tlf (-): succeeds
> - flex-sdk (main checkintests): succeeds
> - flex-sdk_releas
Hi,
Just to let you know what I'm working on:
I'm working on the build machines to create new/updated Jenkins jobs
for the following builds:
- flex-tlf (-): succeeds
- flex-sdk (main checkintests): succeeds
- flex-sdk_release (release): fails, waiting for Extension Manager install
- flex-sdk_asdo
35 matches
Mail list logo
