Hi,
> If you are going to ask, you may want to ask that you also have access to
> wherever the flashlog.txt is going to end up.
We do, the script currently copies it into the Jenkins workspace (assuming I
got the paths etc right).
Justin
Hi,
> I believe that the mm.cfg file is missing on the windows slave. How would
> I get this added on to that server? Should I send an email to
> bui...@apache.org?
That's how I got the debug player installed on the box, so yes I give that a go.
Justin
If you are going to ask, you may want to ask that you also have access to
wherever the flashlog.txt is going to end up.
BTW, I briefly considered the idea that we collect all mustella output some
other way. Mustella is already set up to send its output over a socket, for
example. However, one of
On Thu, Dec 13, 2012 at 1:19 PM, Om wrote:
> I believe that the mm.cfg file is missing on the windows slave. How would
> I get this added on to that server? Should I send an email to
> bui...@apache.org?
>
> Once we have that, we should at least get to know what is happening by
> looking at the
On 12/13/12 1:17 PM, "Justin Mclean" wrote:
> Hi,
>
>>> Can you add a trusted location via the command line/parameters to the
>>> debug player in any way?
>> If that was possible, it would be a major security flaw :-)
>
> For the release player sure. :-)
>
I don't know of any way to do that
I believe that the mm.cfg file is missing on the windows slave. How would
I get this added on to that server? Should I send an email to
bui...@apache.org?
Once we have that, we should at least get to know what is happening by
looking at the flashlog.txt dump.
Thanks,
Om
On Thu, Dec 13, 2012 at
Hi,
>> Can you add a trusted location via the command line/parameters to the
>> debug player in any way?
> If that was possible, it would be a major security flaw :-)
For the release player sure. :-)
Justin
On Thu, Dec 13, 2012 at 1:11 PM, Justin Mclean wrote:
> Hi,
>
> > Yeah, it seems like there is some secret place that the Global Settings
> are
> > stored. You might want to run a dummy swf and see what the right-click
> > global settings say are trusted locations.
>
> Can you add a trusted locat
Hi,
> Yeah, it seems like there is some secret place that the Global Settings are
> stored. You might want to run a dummy swf and see what the right-click
> global settings say are trusted locations.
Can you add a trusted location via the command line/parameters to the debug
player in any way?
On 12/13/12 11:09 AM, "Om" wrote:
>
> Now that the sdk build problem is fixed, I will try to reproduce the flash
> player security error on my local machine.
>
> I have removed the reference to the mustella/tests directory from these
> two locations (from any and all cfg files):
>
> C:\Wi
On Thu, Dec 13, 2012 at 12:15 AM, Om wrote:
> On Thu, Dec 13, 2012 at 12:03 AM, Alex Harui wrote:
>
>> Ant main checkintests takes like 12 minutes for me. The checkintests take
>> only the last two minutes or so. It sure seems like the player is hanging
>> on
>> the security exception dialog.
On Thu, Dec 13, 2012 at 12:03 AM, Alex Harui wrote:
> Ant main checkintests takes like 12 minutes for me. The checkintests take
> only the last two minutes or so. It sure seems like the player is hanging
> on
> the security exception dialog. I would see if there is a way to verify the
> trust f
I checked my windows box. In
c:\Windows\SysWow64\Macromed\Flash\FlashPlayerTrust
you can add a flex.cfg file with the path to the build
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests
On 12/13/12 12:03 AM, "Alex Harui" wrote:
> Ant main checkintests takes like 12 minutes for me. The
Ant main checkintests takes like 12 minutes for me. The checkintests take
only the last two minutes or so. It sure seems like the player is hanging on
the security exception dialog. I would see if there is a way to verify the
trust file settings.
On 12/12/12 11:55 PM, "Justin Mclean" wrote:
>
Looks like it froze and didn't run any tests to me which was the issue I
was having before.
Hi,
>> For those interested this is the magic combination of slashes:
>> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
>> CS5/Pixel\ Bender\ Toolkit\ 2
Both Jenkins job are currently set up like this - although I'm not 100% sure if
getting it wrong causes the AIF error.
J
There's an old email from Justin saying he had to set up PixelBender like
this:
> For those interested this is the magic combination of slashes:
> PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\
> CS5/Pixel\ Bender\ Toolkit\ 2
On 12/12/12 10:23 PM, "Om" wrote:
> ant main f
Hi,
> On a bad day for me, when I have to download the entire Adobe SDK, it can
> take longer than 30 minutes.
The Jenkins job only does a SVN update and doesn't download anything it doesn't
already have, so that should be OK 99% of the time.
We can increate the timeout if need be but do need to
On 12/12/12 8:58 PM, "Justin Mclean" wrote:
> Hi,
>
>> The only problem is that each complete run of mustella would take hours.
>> Or does checkintests have a shorter run time?
> Checkin tests take only a few minutes. This is a shared server, it expect that
> all jobs run in under 30 minutes.
I always run:
ant main checkintests
Or
ant clean main checkintests
Can we have it do something like that? It might need to run super-clean
instead of clean.
On 12/12/12 8:22 PM, "Om" wrote:
> Okay, here is the problem.
>
> sdk/build.xml -checkintests calls sdk/mustella/makemustella.s
Hi,
> The only problem is that each complete run of mustella would take hours.
> Or does checkintests have a shorter run time?
Checkin tests take only a few minutes. This is a shared server, it expect that
all jobs run in under 30 minutes. There are a few that run longer than that but
running th
On Wed, Dec 12, 2012 at 8:30 PM, Justin Mclean wrote:
> Hi,
>
> > sdk/build.xml -checkintests calls sdk/mustella/makemustella.swc before it
> > can run the tests.
> So just add the required target before the checkintests target. you can
> build multiple targets one after the other in Jenkins (as I
Hi,
> sdk/build.xml -checkintests calls sdk/mustella/makemustella.swc before it
> can run the tests.
So just add the required target before the checkintests target. you can build
multiple targets one after the other in Jenkins (as I'm sure you know).
> The other option is to modify the Flex_SDK_
Okay, here is the problem.
sdk/build.xml -checkintests calls sdk/mustella/makemustella.swc before it
can run the tests. In order to make the mustella.swc, the flex sdk should
be built first. Right now, it is not and hence mustella.swc cannot be
built.
I am testing a fix on my local jenkins that
Good news. I ran the same job locally on my instance of Jenkins and I am
getting the same exact error . Will debug it on my machine by this
evening.
Thanks,
Om
On Wed, Dec 12, 2012 at 1:39 PM, Alex Harui wrote:
> BTW, the flashplayer trust folder might be in
> %systemroot%\syswow64\macromed
>
BTW, the flashplayer trust folder might be in %systemroot%\syswow64\macromed
On 12/12/12 1:31 PM, "Alex Harui" wrote:
>
>
>
> On 12/12/12 1:23 PM, "Justin Mclean" wrote:
>
>> Hi,
>>
>>> {sdk_folder}/build.xml - checkintests task
>> I'd give that a go first, but either is probably fine. A
On 12/12/12 1:23 PM, "Justin Mclean" wrote:
> Hi,
>
>> {sdk_folder}/build.xml - checkintests task
> I'd give that a go first, but either is probably fine. Any automated testing
> we have is far better than none.
Yes, the one from the top level build.xml. It might call into sub-folder
targets
Hi,
> {sdk_folder}/build.xml - checkintests task
I'd give that a go first, but either is probably fine. Any automated testing we
have is far better than none.
Thanks,
Justin
Okay, I need a reset now. What exactly are we trying to do in checkintests
CI task?
Are we running
{sdk_folder}/build.xml - checkintests task
or
{sdk_folder}/mustella/build.xml - checkintests task?
On Wed, Dec 12, 2012 at 1:06 PM, Alex Harui wrote:
> Double backslash on path to compc.jar?
Double backslash on path to compc.jar?
On 12/12/12 1:03 PM, "Om" wrote:
> This is why the checkin tests are failing on Jenkins:
>
> Before I dig in deeper, anyone see any obvious problem here?
>
> makemustellaswc:
> [loadfile]
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustel
@justin,
Am I wrong reading that [1] you can access the jenkins slave ?
[1] http://wiki.apache.org/general/Jenkins
- Fred
-Message d'origine-
From: Justin Mclean
Sent: Wednesday, December 12, 2012 9:56 PM
To: flex-dev@incubator.apache.org
Subject: Re: Release target and Jenekin
Hi,
> I've had trouble figuring out where the trust files go on Win64 systems.
> What I've had to do is launch a simple SWF and use the Global Settings from
> the right-click menu to set my trusted dirs.
We have no access to the machine so may be a little difficult to do that, but
that's somethin
On 12/12/12 12:23 PM, "Justin Mclean" wrote:
> Hi,
>
>> And is there a flashplayer trust file in the right place with the right
>> settings?
> It's likely that say is the issue.
I've had trouble figuring out where the trust files go on Win64 systems.
What I've had to do is launch a simple SWF
Hi,
> And is there a flashplayer trust file in the right place with the right
> settings?
It's likely that say is the issue.
Justin
On Wed, Dec 12, 2012 at 12:57 AM, Justin Mclean wrote:
> Hi,
>
> > This job is looking at
> > https://svn.apache.org/repos/asf/incubator/flex/trunk which
> > seems outdated.
>
> The Flex_SDK_build job is using:
> https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/develop
>
> It has the s
Is there an mm.cfg file in the right place with the right settings?
And is there a flashplayer trust file in the right place with the right
settings?
The lack of trust file would likely cause an exception and halt the test
"forever".
On 12/12/12 12:19 AM, "Om" wrote:
> On Tue, Dec 11, 2012 at
Hi,
> This job is looking at
> https://svn.apache.org/repos/asf/incubator/flex/trunk which
> seems outdated.
The Flex_SDK_build job is using:
https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/develop
It has the same issue when I tried 2 days ago, so that's not the issue.
Justin
On Wed, Dec 12, 2012 at 12:28 AM, Justin Mclean wrote:
> Hi,
>
> > There is no flashlog.txt output since the file was not found.
>
> The job timed out and as a result of that error occurred next.
>
> Justin
>
This job is looking at
https://svn.apache.org/repos/asf/incubator/flex/trunk which
seem
Hi,
> There is no flashlog.txt output since the file was not found.
The job timed out and as a result of that error occurred next.
Justin
On Tue, Dec 11, 2012 at 11:50 PM, Alex Harui wrote:
> Can we get the ant output in the console and the flashlog.txt?
There is no flashlog.txt output since the file was not found. Here is the
console output:
Started by user jmclean
Building remotely on windows1 in workspace
f:\hudson\hudson-sl
My username: fthomas
- Fred
-Message d'origine-
From: Bertrand Delacretaz
Sent: Wednesday, December 12, 2012 8:51 AM
To: flex-dev@incubator.apache.org
Subject: Re: Release target and Jenekins
On Wed, Dec 12, 2012 at 7:53 AM, Justin Mclean
wrote:
...Not 100% sure what you need
Can we get the ant output in the console and the flashlog.txt?
On 12/11/12 10:24 PM, "Justin Mclean" wrote:
> Hi,
>
> Currently we can't run the checkin tests on the Jenkins build machine., that
> also means we can't also can't check the release build as it runs the checkin
> tests as part of
On Wed, Dec 12, 2012 at 7:53 AM, Justin Mclean wrote:
> ...Not 100% sure what you need to do to get admin access (sorry I've
> forgotten)
Details at https://builds.apache.org/ which links to
http://wiki.apache.org/general/Jenkins
-Bertrand
Hi,
> In the meantime, I will try to replicate it on my windows machine + Jenkins
> and see if I can run the checkin tests
Much appreciated, hopefully that will point out if any is wrong. I've
builds@a.o again and asked if anyone there has any ideas.
Thanks,
Justin
ator.apache.org
Subject: Re: Release target and Jenekins
Hi,
As it says it can't access the flashlog.txt,
I think the script timed out before that error so that may not be the cause.
Thanks,
Justin
to the server, it's difficult to say why.
>
>
> - Fred
>
> -Message d'origine- From: Justin Mclean
> Sent: Wednesday, December 12, 2012 8:27 AM
>
> To: flex-dev@incubator.apache.org
> Subject: Re: Release target and Jenekins
>
> Hi,
>
> As it sa
ubject: Re: Release target and Jenekins
Hi,
As it says it can't access the flashlog.txt,
I think the script timed out before that error so that may not be the cause.
Thanks,
Justin
Hi,
> Then, maybe see with infra why it can't access the flashlog.txt.
I got no reply last time I asked, I'll try again.
Thanks,
Justin
Hi,
> As it says it can't access the flashlog.txt,
I think the script timed out before that error so that may not be the cause.
Thanks,
Justin
Then, maybe see with infra why it can't access the flashlog.txt.
[1] https://builds.apache.org/job/Flex_SDK_checkin_tests/16/console
- Fred
-Message d'origine-
From: Justin Mclean
Sent: Wednesday, December 12, 2012 8:23 AM
To: flex-dev@incubator.apache.org
Subject: Re: Rele
Hi,
> As it says it can't access the flashlog.txt, I need to access the server too,
> how can I do that ?
We have no direct access to the server, it's a shared server and run by
infrastructure.
Justin
As it says it can't access the flashlog.txt, I need to access the server
too, how can I do that ?
- Fred
-Message d'origine-
From: Justin Mclean
Sent: Wednesday, December 12, 2012 7:55 AM
To: flex-dev@incubator.apache.org
Subject: Re: Release target and Jenekins
Hi,
I
Hi,
Here's the job configuration, perhaps that will help?
Build the Apache Flex SDK nightly or on the hour if code has been committed to
SVN
7
10
-1
-1
false
false
https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/develop
.
http://svn.apache.org/viewvc/
Windo
rg
Subject: Re: Release target and Jenekins
Hi,
I have been meaning to get myself familiar with our Jenkins setup. This
might be a good opportunity. Can you please send me the access details?
Job can be found here:
https://builds.apache.org/job/Flex_SDK_build
366 builds so far!
Not 100% sur
org
Subject: Re: Release target and Jenekins
I have been meaning to get myself familiar with our Jenkins setup. This
might be a good opportunity. Can you please send me the access details? I
will poke around and see if I can do something.
Thanks,
Om
On Dec 11, 2012 10:25 PM, "Justin
Hi,
> I have been meaning to get myself familiar with our Jenkins setup. This
> might be a good opportunity. Can you please send me the access details?
Also this to run the checkin tests, it;s currently disables as it freezes and
times out after 30 minutes.
https://builds.apache.org/job/Flex_
Hi,
> I have been meaning to get myself familiar with our Jenkins setup. This
> might be a good opportunity. Can you please send me the access details?
Job can be found here:
https://builds.apache.org/job/Flex_SDK_build
366 builds so far!
Not 100% sure what you need to do to get admin access
I have been meaning to get myself familiar with our Jenkins setup. This
might be a good opportunity. Can you please send me the access details? I
will poke around and see if I can do something.
Thanks,
Om
On Dec 11, 2012 10:25 PM, "Justin Mclean" wrote:
> Hi,
>
> Currently we can't run the ch
Hi,
Currently we can't run the checkin tests on the Jenkins build machine., that
also means we can't also can't check the release build as it runs the checkin
tests as part of the release process.
It would be great if we could get the checkin tests working on Jenkins, it
should be possible an
59 matches
Mail list logo
