You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Justin Mclean <ju...@classsoftware.com> on 2012/12/12 07:24:38 UTC
Release target and Jenekins
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 and the flash debug player has been installed on the windows build box and the Jenkins job is configured with the correct path to it. Currently the tests hang if you try and run them - no further information is given so it's a little hard to debug. Any one have any experience with running anything similar on Jenkins?
Justin
Re: Release target and Jenekins
Posted by Frédéric THOMAS <we...@hotmail.com>.
It might be as well because of the HelloWorld.swf, but once again, without
any access to the server, difficult to figure out why.
- Fred
-----Message d'origine-----
From: Frédéric THOMAS
Sent: Wednesday, December 12, 2012 8:33 AM
To: flex-dev@incubator.apache.org
Subject: Re: Release target and Jenekins
Yeah, you right but it seems it hangs out for some reasons realtive to
flashplayer so, without any access 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 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
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
In the meantime, I will try to replicate it on my windows machine + Jenkins
and see if I can run the checkin tests
Om
On Tue, Dec 11, 2012 at 11:33 PM, Frédéric THOMAS
<we...@hotmail.com>wrote:
> Yeah, you right but it seems it hangs out for some reasons realtive to
> flashplayer so, without any access 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 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
>
Re: Release target and Jenekins
Posted by Frédéric THOMAS <we...@hotmail.com>.
Yeah, you right but it seems it hangs out for some reasons realtive to
flashplayer so, without any access 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 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
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: Release target and Jenekins
Posted by Frédéric THOMAS <we...@hotmail.com>.
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: Release target and Jenekins
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
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: Release target and Jenekins
Posted by Frédéric THOMAS <we...@hotmail.com>.
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 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_SDK_checkin_tests/
Justin
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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_SDK_checkin_tests/
Justin
Re: Release target and Jenekins
Posted by Frédéric THOMAS <we...@hotmail.com>.
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 <ju...@classsoftware.com>
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
Re: Release target and Jenekins
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Dec 12, 2012 at 7:53 AM, Justin Mclean <ju...@classsoftware.com> 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
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Here's the job configuration, perhaps that will help?
<project>
<actions/>
<description>
Build the Apache Flex SDK nightly or on the hour if code has been committed to SVN
</description>
<logRotator>
<daysToKeep>7</daysToKeep>
<numToKeep>10</numToKeep>
<artifactDaysToKeep>-1</artifactDaysToKeep>
<artifactNumToKeep>-1</artifactNumToKeep>
</logRotator>
<keepDependencies>false</keepDependencies>
<properties>
<org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerProperty plugin="maven-repo-cleaner@1.1">
<notOnThisProject>false</notOnThisProject>
</org.jenkinsci.plugins.mavenrepocleaner.MavenRepoCleanerProperty>
</properties>
<scm class="hudson.scm.SubversionSCM" plugin="subversion@1.39">
<locations>
<hudson.scm.SubversionSCM_-ModuleLocation>
<remote>
https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/develop
</remote>
<local>.</local>
</hudson.scm.SubversionSCM_-ModuleLocation>
</locations>
<browser class="hudson.scm.browsers.ViewSVN">
<url>http://svn.apache.org/viewvc/</url>
</browser>
<excludedRegions/>
<includedRegions/>
<excludedUsers/>
<excludedRevprop/>
<excludedCommitMessages/>
<workspaceUpdater class="hudson.scm.subversion.UpdateUpdater"/>
</scm>
<assignedNode>Windows</assignedNode>
<canRoam>false</canRoam>
<disabled>false</disabled>
<blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
<blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
<jdk>JDK 1.6 (latest)</jdk>
<triggers class="vector">
<hudson.triggers.TimerTrigger>
<spec>
# run once per day at no particular specific time H H * * *
</spec>
</hudson.triggers.TimerTrigger>
<hudson.triggers.SCMTrigger>
<spec>
# poll every hour and build if required 0 0-23 * * *
</spec>
<ignorePostCommitHooks>false</ignorePostCommitHooks>
</hudson.triggers.SCMTrigger>
</triggers>
<concurrentBuild>false</concurrentBuild>
<builders>
<hudson.tasks.Ant plugin="ant@1.1">
<targets>main</targets>
<antName>Ant 1.7.0</antName>
<buildFile>jenkins.xml</buildFile>
</hudson.tasks.Ant>
<hudson.tasks.Ant plugin="ant@1.1">
<targets>clean main source-release</targets>
<antName>Ant 1.7.0</antName>
<buildFile>build.xml</buildFile>
<properties>build.number=${SVN_REVISION} build.noprompt=</properties>
</hudson.tasks.Ant>
</builders>
<publishers>
<hudson.tasks.Mailer>
<recipients>
justin@classsoftware.com cframpto@adobe.com jonbcampos@gmail.com christophe.herreman@gmail.com
</recipients>
<dontNotifyEveryUnstableBuild>false</dontNotifyEveryUnstableBuild>
<sendToIndividuals>true</sendToIndividuals>
</hudson.tasks.Mailer>
</publishers>
<buildWrappers>
<hudson.plugins.build__timeout.BuildTimeoutWrapper plugin="build-timeout@1.11">
<timeoutMinutes>30</timeoutMinutes>
<failBuild>false</failBuild>
<writingDescription>false</writingDescription>
<timeoutPercentage>0</timeoutPercentage>
<timeoutType>absolute</timeoutType>
<timeoutMinutesElasticDefault>3</timeoutMinutesElasticDefault>
</hudson.plugins.build__timeout.BuildTimeoutWrapper>
<hudson.plugins.setenv.SetEnvBuildWrapper plugin="setenv@1.1">
<localVarText>
AIR_HOME=${WORKSPACE}/air/AIR Integration Kit FLASHPLAYER_DEBUGGER=C\:/Program\ Files\ (x86)/Adobe/flashplayer_11_sa_debug_32bit.exe PLAYERGLOBAL_HOME=${WORKSPACE}/lib/player PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\ CS5/Pixel\ Bender\ Toolkit\ 2
</localVarText>
</hudson.plugins.setenv.SetEnvBuildWrapper>
</buildWrappers>
</project>
Justin
Re: Release target and Jenekins
Posted by Frédéric THOMAS <we...@hotmail.com>.
@Justin
Without any rights, I can't even see the configure link, have you got a
pointer to a doc or something that say how to get rights on Jenkins ?
- Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Wednesday, December 12, 2012 7:53 AM
To: flex-dev@incubator.apache.org
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% sure what you need to do to get admin access (sorry I've
forgotten).
Justin
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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 (sorry I've forgotten).
Justin
Re: Release target and Jenekins
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi Justin,
The same for me, I'd like to have a look at the conf, not sure I can do
something but I'd like to get familiar with, so, how can I access it ?
- Fred
-----Message d'origine-----
From: Om
Sent: Wednesday, December 12, 2012 7:37 AM
To: flex-dev@incubator.apache.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 Mclean" <ju...@classsoftware.com> 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 the release process.
>
> It would be great if we could get the checkin tests working on Jenkins, it
> should be possible and the flash debug player has been installed on the
> windows build box and the Jenkins job is configured with the correct path
> to it. Currently the tests hang if you try and run them - no further
> information is given so it's a little hard to debug. Any one have any
> experience with running anything similar on Jenkins?
>
> Justin
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
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" <ju...@classsoftware.com> 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 the release process.
>
> It would be great if we could get the checkin tests working on Jenkins, it
> should be possible and the flash debug player has been installed on the
> windows build box and the Jenkins job is configured with the correct path
> to it. Currently the tests hang if you try and run them - no further
> information is given so it's a little hard to debug. Any one have any
> experience with running anything similar on Jenkins?
>
> Justin
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Wed, Dec 12, 2012 at 12:57 AM, Justin Mclean <ju...@classsoftware.com>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 same issue when I tried 2 days ago, so that's not the issue.
>
> Justin
>
After you changed the repo location for Flex_SDK_checkin_tests, there is a
different error now. Looks like an issue with the paths (cant find compc,
mxmlc, etc) I am trying to fix the paths now.
https://builds.apache.org/job/Flex_SDK_checkin_tests/18/consoleText
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Wed, Dec 12, 2012 at 12:28 AM, Justin Mclean <ju...@classsoftware.com>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
seems outdated. Can you try updating it to the correct location and try
again?
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Wed, Dec 12, 2012 at 12:47 PM, Alex Harui <ah...@adobe.com> wrote:
>
>
>
> On 12/12/12 12:23 PM, "Justin Mclean" <ju...@classsoftware.com> 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 and use the Global Settings from
> the right-click menu to set my trusted dirs. There is a simple SWF in
> frameworks/tests/BasicTests/basicLoader.swf
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
I am on Win64. This is where the trust file
is: C:\Users\{username}\AppData\Roaming\Macromedia\Flash
Player\#Security\FlashPlayerTrust
Re: Release target and Jenekins
Posted by Frédéric THOMAS <we...@hotmail.com>.
@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 Jenekins
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 something I should be able to ask builds@a.o to do for us.
Thanks,
Justin
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
On 12/13/12 1:17 PM, "Justin Mclean" <ju...@classsoftware.com> 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.
It just occurred to me that I have never tried running BasicTests after
compiling it with useNetwork=false. I don't think the test needs the
network, and I think then that it won't need trust files, IIRC.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Thu, Dec 13, 2012 at 1:32 PM, Alex Harui <ah...@adobe.com> wrote:
> 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 already have a copy task at the end of the checkintests that copies the
file into the current build workspace. It is just that the flashlog.txt
never gets created (because of the absence of mm.cfg)
> 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 the goals of BasicTests was to examine the
> flashlog for extraneous trace statements in the common code paths that
> BasicTests runs. Flashlog also contains the stacktraces of any unhandled
> exception during the test.
>
> We could (should?) solve the trace problem by doing some other analysis on
> the source or swcs. After all, BasicTests won't catch every trace
> statement
> left in the code. We do leave trace statements commented out for
> debugging,
> though.
>
> And now that we have 10.2 as the min player version, we might be able to
> use
> the UncaughtError subsystem to catch exceptions during the test.
>
> It is work, but maybe less work that trying to figure out Jenkins?
>
>
As I was working on OneClickMustella, I was thinking about something
similar as well. We might as well trap the uncaughterrors and push it out
over a localconnection and my app could catch it and write it to a file in
the workspace.
But I would first try the current set up as is on Jenkins. I think we are
close.
>
> On 12/13/12 1:19 PM, "Om" <bi...@gmail.com> 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
> > builds@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 1:15 PM, Om <bi...@gmail.com> wrote:
> >
> >> On Thu, Dec 13, 2012 at 1:11 PM, Justin Mclean
> >> <ju...@classsoftware.com>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 location via the command line/parameters to the
> >>> debug player in any way?
> >>>
> >>>
> >> If that was possible, it would be a major security flaw :-)
> >>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
> builds@apache.org?
That's how I got the debug player installed on the box, so yes I give that a go.
Justin
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Thu, Dec 13, 2012 at 1:19 PM, Om <bi...@gmail.com> 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
> builds@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
>
>
Never mind. I have created this bug in JIRA [1] for this.
Thanks,
Om
[1] https://issues.apache.org/jira/browse/INFRA-5652
>
> On Thu, Dec 13, 2012 at 1:15 PM, Om <bi...@gmail.com> wrote:
>
>> On Thu, Dec 13, 2012 at 1:11 PM, Justin Mclean <ju...@classsoftware.com>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 location via the command line/parameters to the
>>> debug player in any way?
>>>
>>>
>> If that was possible, it would be a major security flaw :-)
>>
>
>
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
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 the goals of BasicTests was to examine the
flashlog for extraneous trace statements in the common code paths that
BasicTests runs. Flashlog also contains the stacktraces of any unhandled
exception during the test.
We could (should?) solve the trace problem by doing some other analysis on
the source or swcs. After all, BasicTests won't catch every trace statement
left in the code. We do leave trace statements commented out for debugging,
though.
And now that we have 10.2 as the min player version, we might be able to use
the UncaughtError subsystem to catch exceptions during the test.
It is work, but maybe less work that trying to figure out Jenkins?
On 12/13/12 1:19 PM, "Om" <bi...@gmail.com> 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
> builds@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 1:15 PM, Om <bi...@gmail.com> wrote:
>
>> On Thu, Dec 13, 2012 at 1:11 PM, Justin Mclean
>> <ju...@classsoftware.com>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 location via the command line/parameters to the
>>> debug player in any way?
>>>
>>>
>> If that was possible, it would be a major security flaw :-)
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
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
builds@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 1:15 PM, Om <bi...@gmail.com> wrote:
> On Thu, Dec 13, 2012 at 1:11 PM, Justin Mclean <ju...@classsoftware.com>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 location via the command line/parameters to the
>> debug player in any way?
>>
>>
> If that was possible, it would be a major security flaw :-)
>
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Thu, Dec 13, 2012 at 1:11 PM, Justin Mclean <ju...@classsoftware.com>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 location via the command line/parameters to the
> debug player in any way?
>
>
If that was possible, it would be a major security flaw :-)
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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?
Thanks,
Justin
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
On 12/13/12 11:09 AM, "Om" <bi...@gmail.com> 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:\Windows\SysWOW64\Macromed\Flash\FlashPlayerTrust
> C:\Users\user\AppData\Roaming\Macromedia\Flash
> Player\#Security\FlashPlayerTrust
>
> I then proceeded to close all browsers and restarted the computer.
>
> And then I ran ant checkintests, the flash player is still opening up the
> tests and everything goes fine. The build is successful.
>
> What am I missing? How exactly can I repro the flash player not responding
> issue locally?
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.
Also note that in the FlashPlayerTrust folders, I think it reads all files,
not just .cfg files and uses any path it finds, and that any higher-up path
allows all of its child folders so if there is one statement allowing the
entire c: drive, it doesn't matter what other entries there are.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Thu, Dec 13, 2012 at 12:15 AM, Om <bi...@gmail.com> wrote:
> On Thu, Dec 13, 2012 at 12:03 AM, Alex Harui <ah...@adobe.com> 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 file settings.
>>
>>
> This was the first time the sdk was built in that workspace, so it was
> downloading a lot of stuff. I am going to try it again and see if it does
> not time out at least.
>
>
Yup, that failed as well.
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:\Windows\SysWOW64\Macromed\Flash\FlashPlayerTrust
C:\Users\user\AppData\Roaming\Macromedia\Flash
Player\#Security\FlashPlayerTrust
I then proceeded to close all browsers and restarted the computer.
And then I ran ant checkintests, the flash player is still opening up the
tests and everything goes fine. The build is successful.
What am I missing? How exactly can I repro the flash player not responding
issue locally?
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Thu, Dec 13, 2012 at 12:03 AM, Alex Harui <ah...@adobe.com> 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 file settings.
>
>
This was the first time the sdk was built in that workspace, so it was
downloading a lot of stuff. I am going to try it again and see if it does
not time out at least.
>
> On 12/12/12 11:55 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
> > Looks like it froze and didn't run any tests to me which was the issue I
> > was having before.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
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" <ah...@adobe.com> 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 file settings.
>
>
> On 12/12/12 11:55 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
>> Looks like it froze and didn't run any tests to me which was the issue I
>> was having before.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
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" <ju...@classsoftware.com> wrote:
> Looks like it froze and didn't run any tests to me which was the issue I
> was having before.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
Looks like it froze and didn't run any tests to me which was the issue I
was having before.
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
Okay, I believe that the checkintests job has been fixed.... BUT, it took
longer than 30 minutes and was killed.
I am going to poke around the Apache Jenkins wiki to see what we can do
now...
...
<snip>
...
*compilemustellaswc*:
[exec] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config.xml
[exec] F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\mustella.swc
(84348 bytes)
*load-task*:
*basictests*:
[mxmlc] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config.xml
[mxmlc] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basicTests\BasicTests-config.xml
[mxmlc] F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basicTests\BasicTests.swf
(3652927 bytes)
[mxmlc] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config.xml
[mxmlc] F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basicTests\basicLoader.swf
(971 bytes)
[mxmlc] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config.xml
[mxmlc] F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basicTests\spark\views\StyleManagerModuleTest.swf
(505729 bytes)
[mxmlc] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config.xml
[mxmlc] Required RSLs:
[mxmlc] framework_1420998.swf
[mxmlc] textLayout_1420998.swf
[mxmlc] spark_1420998.swf
[mxmlc] osmf_1420998.swf
[mxmlc] F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basicTests\spark\views\HelloWorld.swf
(48989 bytes)
[echo] launching player and swf
Build timed out (after 30 minutes). Marking the build as failed.
Performing Post build task...
Match found for :Build timed out : True
Logical operation result is TRUE
Running script : copy "C:\Documents and Settings\hudson\Application
Data\Macromedia\Flash Player\Logs\flashlog.txt" .
[Flex_SDK_checkin_tests] $ cmd /c call
C:\Users\hudson\AppData\Local\Temp\hudson6143077157482494073.bat
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests>copy
"C:\Documents and Settings\hudson\Application Data\Macromedia\Flash
Player\Logs\flashlog.txt" .
The system cannot find the path specified.
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests>exit 1
POST BUILD TASK : FAILURE
END OF POST BUILD TASK : 0
On Wed, Dec 12, 2012 at 10:54 PM, Om <bi...@gmail.com> wrote:
> On Wed, Dec 12, 2012 at 10:47 PM, Justin Mclean <ju...@classsoftware.com>wrote:
>
>> 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.
>>
>> Justin
>
>
> No luck for me after changing it locally. I looked at the Flex_SDK_Build
> job on Apache's Jenkins and it seems to be running pixelbuilder-compile
> just fine. I am now going to try the fix directly on Apache's Jenkins CI
> server.
>
> I am fairly certain that this is a local problem and it should not occur
> on Apache's Jenkins server.
>
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Wed, Dec 12, 2012 at 10:47 PM, Justin Mclean <ju...@classsoftware.com>wrote:
> 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.
>
> Justin
No luck for me after changing it locally. I looked at the Flex_SDK_Build
job on Apache's Jenkins and it seems to be running pixelbuilder-compile
just fine. I am now going to try the fix directly on Apache's Jenkins CI
server.
I am fairly certain that this is a local problem and it should not occur on
Apache's Jenkins server.
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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.
Justin
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
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" <bi...@gmail.com> wrote:
> ant main failed on jenkins with these errors. But it works fine on cygwin.
> Has anyone tried running pixel bender via jenkins?
>
> ...<snip>
>
> *pixelbender-compile*:
>
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
>
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
>
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
>
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
>
> [exec] ERROR: AIF Internal exception
> [exec] Result: 1
> *compile*:
> [echo] Compiling frameworks/libs/framework.swc
> [compc] Loading configuration file C:\Program Files
> (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\flex-config.xml
> [compc] Loading configuration file C:\Program Files
> (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\framework-config.xml
> [compc] Loading configuration file C:\Program Files
> (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\compile-config.xml
>
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Lu
> minosityShader.as(43):
> col: 5: Error: unable to resolve 'Luminosity.pbj' for transcoding
> [compc]
> [compc] [Embed(source="Luminosity.pbj",
> mimeType="application/octet-stream")]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Lu
> minosityShader.as(43):
> col: 5: Error: Unable to transcode Luminosity.pbj.
> [compc]
> [compc]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\So
> ftLightShader.as(43):
> col: 5: Error: unable to resolve 'SoftLight.pbj' for transcoding
> [compc]
> [compc] [Embed(source="SoftLight.pbj",
> mimeType="application/octet-stream")]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\So
> ftLightShader.as(43):
> col: 5: Error: Unable to transcode SoftLight.pbj.
> [compc]
> [compc]
> [compc] ^
> [compc]
>
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Co
> lorShader.as(43):
> col: 5: Error: unable to resolve 'Color.pbj' for transcoding
> [compc]
> [compc] [Embed(source="Color.pbj",
> mimeType="application/octet-stream")]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Co
> lorShader.as(43):
> col: 5: Error: Unable to transcode Color.pbj.
> [compc]
> [compc]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Ex
> clusionShader.as(43):
> col: 5: Error: unable to resolve 'Exclusion.pbj' for transcoding
> [compc]
> [compc] [Embed(source="Exclusion.pbj",
> mimeType="application/octet-stream")]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Ex
> clusionShader.as(43):
> col: 5: Error: Unable to transcode Exclusion.pbj.
> [compc]
> [compc]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Sa
> turationShader.as(43):
> col: 5: Error: unable to resolve 'Saturation.pbj' for transcoding
> [compc]
> [compc] [Embed(source="Saturation.pbj",
> mimeType="application/octet-stream")]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Sa
> turationShader.as(43):
> col: 5: Error: Unable to transcode Saturation.pbj.
> [compc]
> [compc]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Co
> lorDodgeShader.as(43):
> col: 5: Error: unable to resolve 'ColorDodge.pbj' for transcoding
> [compc]
> [compc] [Embed(source="ColorDodge.pbj",
> mimeType="application/octet-stream")]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Co
> lorDodgeShader.as(43):
> col: 5: Error: Unable to transcode ColorDodge.pbj.
> [compc]
> [compc]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Lu
> minosityMaskShader.as(47):
> col: 5: Error: unable to resolve 'LuminosityMaskFilter.pbj' for
> transcoding
> [compc]
> [compc] [Embed(source="LuminosityMaskFilter.pbj",
> mimeType="application/octet-stream")]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Lu
> minosityMaskShader.as(47):
> col: 5: Error: Unable to transcode LuminosityMaskFilter.pbj.
> [compc]
> [compc]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Hu
> eShader.as(43):
> col: 5: Error: unable to resolve 'Hue.pbj' for transcoding
> [compc]
> [compc] [Embed(source="Hue.pbj", mimeType="application/octet-stream")]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Hu
> eShader.as(43):
> col: 5: Error: Unable to transcode Hue.pbj.
> [compc]
> [compc]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Co
> lorBurnShader.as(43):
> col: 5: Error: unable to resolve 'ColorBurn.pbj' for transcoding
> [compc]
> [compc] [Embed(source="ColorBurn.pbj",
> mimeType="application/octet-stream")]
> [compc] ^
> [compc]
> [compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
> local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\Co
> lorBurnShader.as(43):
> col: 5: Error: Unable to transcode ColorBurn.pbj.
> [compc]
> [compc]
> [compc] ^
> [compc]
> BUILD FAILED
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
ant main failed on jenkins with these errors. But it works fine on cygwin.
Has anyone tried running pixel bender via jenkins?
...<snip>
*pixelbender-compile*:
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
[exec] ERROR: AIF Internal exception
[exec] Result: 1
*compile*:
[echo] Compiling frameworks/libs/framework.swc
[compc] Loading configuration file C:\Program Files
(x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\flex-config.xml
[compc] Loading configuration file C:\Program Files
(x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\framework-config.xml
[compc] Loading configuration file C:\Program Files
(x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\compile-config.xml
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\LuminosityShader.as(43):
col: 5: Error: unable to resolve 'Luminosity.pbj' for transcoding
[compc]
[compc] [Embed(source="Luminosity.pbj",
mimeType="application/octet-stream")]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\LuminosityShader.as(43):
col: 5: Error: Unable to transcode Luminosity.pbj.
[compc]
[compc]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\SoftLightShader.as(43):
col: 5: Error: unable to resolve 'SoftLight.pbj' for transcoding
[compc]
[compc] [Embed(source="SoftLight.pbj",
mimeType="application/octet-stream")]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\SoftLightShader.as(43):
col: 5: Error: Unable to transcode SoftLight.pbj.
[compc]
[compc]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\ColorShader.as(43):
col: 5: Error: unable to resolve 'Color.pbj' for transcoding
[compc]
[compc] [Embed(source="Color.pbj", mimeType="application/octet-stream")]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\ColorShader.as(43):
col: 5: Error: Unable to transcode Color.pbj.
[compc]
[compc]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\ExclusionShader.as(43):
col: 5: Error: unable to resolve 'Exclusion.pbj' for transcoding
[compc]
[compc] [Embed(source="Exclusion.pbj",
mimeType="application/octet-stream")]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\ExclusionShader.as(43):
col: 5: Error: Unable to transcode Exclusion.pbj.
[compc]
[compc]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\SaturationShader.as(43):
col: 5: Error: unable to resolve 'Saturation.pbj' for transcoding
[compc]
[compc] [Embed(source="Saturation.pbj",
mimeType="application/octet-stream")]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\SaturationShader.as(43):
col: 5: Error: Unable to transcode Saturation.pbj.
[compc]
[compc]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\ColorDodgeShader.as(43):
col: 5: Error: unable to resolve 'ColorDodge.pbj' for transcoding
[compc]
[compc] [Embed(source="ColorDodge.pbj",
mimeType="application/octet-stream")]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\ColorDodgeShader.as(43):
col: 5: Error: Unable to transcode ColorDodge.pbj.
[compc]
[compc]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\LuminosityMaskShader.as(47):
col: 5: Error: unable to resolve 'LuminosityMaskFilter.pbj' for
transcoding
[compc]
[compc] [Embed(source="LuminosityMaskFilter.pbj",
mimeType="application/octet-stream")]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\LuminosityMaskShader.as(47):
col: 5: Error: Unable to transcode LuminosityMaskFilter.pbj.
[compc]
[compc]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\HueShader.as(43):
col: 5: Error: unable to resolve 'Hue.pbj' for transcoding
[compc]
[compc] [Embed(source="Hue.pbj", mimeType="application/octet-stream")]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\HueShader.as(43):
col: 5: Error: Unable to transcode Hue.pbj.
[compc]
[compc]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\ColorBurnShader.as(43):
col: 5: Error: unable to resolve 'ColorBurn.pbj' for transcoding
[compc]
[compc] [Embed(source="ColorBurn.pbj",
mimeType="application/octet-stream")]
[compc] ^
[compc]
[compc] C:\Program Files (x86)\Jenkins\jobs\checkintest -
local\workspace\frameworks\projects\framework\src\mx\graphics\shaderClasses\ColorBurnShader.as(43):
col: 5: Error: Unable to transcode ColorBurn.pbj.
[compc]
[compc]
[compc] ^
[compc]
BUILD FAILED
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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 play nice with other jobs on the box, some of them do run for more than 30 minutes. The box run 2 jobs at once so if you get 2 long running jobs the queue builds up fairly quickly.
> Someone suggested a while ago about running the full mustella suite in
> parallel on a bunch of computers.
That would be great if we had them :-)
Thanks,
Justin
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
On 12/12/12 8:58 PM, "Justin Mclean" <ju...@classsoftware.com> 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.
On a bad day for me, when I have to download the entire Adobe SDK, it can
take longer than 30 minutes. Will it kill the job or let it run longer?
> There are a few that run longer than that
> but running the full mustella tests I'm fairly sure overload the queue and
> make quite a few projects unhappy with us.
>
> Once we have it running let see if Infrastructure can set up another windows
> Jenkins server.
Someone suggested a while ago about running the full mustella suite in
parallel on a bunch of computers. Not sure what that would involve, but
sure would be interesting.
>
> Thanks,
> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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 the full mustella tests I'm fairly sure overload the queue and make quite a few projects unhappy with us.
Once we have it running let see if Infrastructure can set up another windows Jenkins server.
Thanks,
Justin
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Wed, Dec 12, 2012 at 8:30 PM, Justin Mclean <ju...@classsoftware.com>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'm sure you
> know).
>
>
Yup, that is the fix I am testing locally.
> > The other option is to modify the Flex_SDK_Build job to run checkintests
> > after building.
> Think we should keep the 2 tasks separate but up to you.
>
>
The only problem is that each complete run of mustella would take hours.
Or does checkintests have a shorter run time?
FYI, I am also planning to work on running a shorter version of mustella
that would run only the required tests for each checkin. Look at
mustella/utils/OneClickMustella for more details.
> Thanks,
> Justin
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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_Build job to run checkintests
> after building.
Think we should keep the 2 tasks separate but up to you.
Thanks,
Justin
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Wed, Dec 12, 2012 at 8:22 PM, Om <bi...@gmail.com> wrote:
> sdk/build.xml -checkintests calls sdk/mustella/makemustella.swc
should be:
sdk/build.xml checkintests calls sdk/mustella/build.xml makemustellaswc
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
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" <bi...@gmail.com> wrote:
> 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 builds the sdk before calling
> checkintests.
>
> The other option is to modify the Flex_SDK_Build job to run checkintests
> after building.
>
> Which would be preferable?
>
>
>
>
> On Wed, Dec 12, 2012 at 2:28 PM, Om <bi...@gmail.com> wrote:
>
>> 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 <ah...@adobe.com> wrote:
>>
>>> BTW, the flashplayer trust folder might be in
>>> %systemroot%\syswow64\macromed
>>>
>>>
>>>
>>> On 12/12/12 1:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>>
>>>>
>>>>
>>>>
>>>> On 12/12/12 1:23 PM, "Justin Mclean" <ju...@classsoftware.com> 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, but the true test is getting it to work from the top-level.
>>>>>
>>>>> Thanks,
>>>>> Justin
>>>
>>> --
>>> Alex Harui
>>> Flex SDK Team
>>> Adobe Systems, Inc.
>>> http://blogs.adobe.com/aharui
>>>
>>>
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
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 builds the sdk before calling
checkintests.
The other option is to modify the Flex_SDK_Build job to run checkintests
after building.
Which would be preferable?
On Wed, Dec 12, 2012 at 2:28 PM, Om <bi...@gmail.com> wrote:
> 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 <ah...@adobe.com> wrote:
>
>> BTW, the flashplayer trust folder might be in
>> %systemroot%\syswow64\macromed
>>
>>
>>
>> On 12/12/12 1:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>> >
>> >
>> >
>> > On 12/12/12 1:23 PM, "Justin Mclean" <ju...@classsoftware.com> 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, but the true test is getting it to work from the top-level.
>> >>
>> >> Thanks,
>> >> Justin
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
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 <ah...@adobe.com> wrote:
> BTW, the flashplayer trust folder might be in
> %systemroot%\syswow64\macromed
>
>
>
> On 12/12/12 1:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
> >
> >
> >
> > On 12/12/12 1:23 PM, "Justin Mclean" <ju...@classsoftware.com> 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, but the true test is getting it to work from the top-level.
> >>
> >> Thanks,
> >> Justin
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
BTW, the flashplayer trust folder might be in %systemroot%\syswow64\macromed
On 12/12/12 1:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>
>
> On 12/12/12 1:23 PM, "Justin Mclean" <ju...@classsoftware.com> 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, but the true test is getting it to work from the top-level.
>>
>> Thanks,
>> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
On 12/12/12 1:23 PM, "Justin Mclean" <ju...@classsoftware.com> 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, but the true test is getting it to work from the top-level.
>
> Thanks,
> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
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 <ah...@adobe.com> wrote:
> Double backslash on path to compc.jar?
>
>
> On 12/12/12 1:03 PM, "Om" <bi...@gmail.com> 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\mustella\local.propert
> > ies
> > doesn't exist
> >
> > compilemustellaswc:
> > [exec] Unable to access jarfile
> >
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\bin\\..\lib\compc.jar
> > [exec] Result: 1
> > [javac] Compiling 1 source file
> >
> > load-task:
> > [taskdef] Could not load definitions from resource flexTasks.tasks.
> > It could not be found.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
Double backslash on path to compc.jar?
On 12/12/12 1:03 PM, "Om" <bi...@gmail.com> 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\mustella\local.propert
> ies
> doesn't exist
>
> compilemustellaswc:
> [exec] Unable to access jarfile
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\bin\\..\lib\compc.jar
> [exec] Result: 1
> [javac] Compiling 1 source file
>
> load-task:
> [taskdef] Could not load definitions from resource flexTasks.tasks.
> It could not be found.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
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\mustella\local.properties
doesn't exist
compilemustellaswc:
[exec] Unable to access jarfile
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\bin\\..\lib\compc.jar
[exec] Result: 1
[javac] Compiling 1 source file
load-task:
[taskdef] Could not load definitions from resource flexTasks.tasks.
It could not be found.
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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 something I should be able to ask builds@a.o to do for us.
Thanks,
Justin
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
On 12/12/12 12:23 PM, "Justin Mclean" <ju...@classsoftware.com> 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 and use the Global Settings from
the right-click menu to set my trusted dirs. There is a simple SWF in
frameworks/tests/BasicTests/basicLoader.swf
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Justin Mclean <ju...@classsoftware.com>.
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
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
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" <bi...@gmail.com> wrote:
> On Tue, Dec 11, 2012 at 11:50 PM, Alex Harui <ah...@adobe.com> 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-slave\workspace\Flex_SDK_checkin_tests
> Location 'https://svn.apache.org/repos/asf/incubator/flex/trunk' does not
> exist
> Updating https://svn.apache.org/repos/asf/incubator/flex/trunk
> ERROR: Failed to update
> https://svn.apache.org/repos/asf/incubator/flex/trunk
> org.tmatesoft.svn.core.SVNException: svn: Target path
> '/incubator/flex/trunk' does not exist
> svn: REPORT of /repos/asf/!svn/vcc/default: 500 Internal Server Error (
> https://svn.apache.org)
> at
> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:
> 64)
> at
> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:
> 51)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.j
> ava:1284)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java
> :830)
> at
> org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:564)
> at
> org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:401)
> at
> hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136)
> at
> hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.
> java:136)
> at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:788)
> at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:769)
> at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309)
> at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> at hudson.remoting.Request$2.run(Request.java:326)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService
> .java:72)
> at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at hudson.remoting.Engine$1$1.run(Engine.java:60)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: Target path
> '/incubator/flex/trunk' does not exist
> at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
> at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:146)
> at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:89)
> at
> org.tmatesoft.svn.core.internal.io.dav.handlers.DAVErrorHandler.endElement(DAV
> ErrorHandler.java:72)
> at
> org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(Bas
> icDAVHandler.java:99)
> at
>
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknow>
n
> Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEnd
> Element(Unknown
> Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$Fragmen
> tContentDriver.next(Unknown
> Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown
> Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown
> Source)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDoc
> ument(Unknown
> Source)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
> Source)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
> Source)
> at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown
> Source)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
> Source)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unkn
> own
> Source)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnec
> tion.java:776)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnec
> tion.java:741)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readError(HTTPConne
> ction.java:222)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.readError(HTTPRequest.
> java:290)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.j
> ava:213)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnec
> tion.java:379)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnect
> ion.java:292)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnect
> ion.java:283)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnect
> ion.java:271)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.ja
> va:283)
> at
> org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.j
> ava:1282)
> ... 19 more
> Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: REPORT of
> /repos/asf/!svn/vcc/default: 500 Internal Server Error (
> https://svn.apache.org)
> at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
> at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:181)
> at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:133)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.createDefaultErrorMess
> age(HTTPRequest.java:444)
> at
> org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.readError(HTTPRequest.
> java:288)
> ... 26 more
> no change for https://svn.apache.org/repos/asf/incubator/flex/trunk since
> the previous build
> [Flex_SDK_checkin_tests] $ cmd.exe /C
> '"f:\hudson\tools\ant\apache-ant-1.7.0\bin\ant.bat -file jenkins.xml main
> && exit %%ERRORLEVEL%%"'
> Buildfile: jenkins.xml
>
> airsdk-check:
>
> airsdk-download:
>
> playerglobal-check:
>
> playerglobal-settarget:
>
> playerglobal10.3-download:
>
> playerglobal11.0-download:
>
> playerglobal11.1-download:
>
> playerglobal11.2-download:
>
> playerglobal11.3-download:
>
> playerglobal-download:
>
> thirdparty-downloads:
>
> main:
>
> BUILD SUCCESSFUL
> Total time: 0 seconds
> [Flex_SDK_checkin_tests] $ cmd.exe /C
> '"f:\hudson\tools\ant\apache-ant-1.7.0\bin\ant.bat -file build.xml
> -Dfont.donot.ask="" -Dbuild.number=1373096 -Dblazeds.donot.ask=""
> checkintests && exit %%ERRORLEVEL%%"'
> Buildfile: build.xml
>
> check-air-home:
> [echo] AIR_HOME is
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests/air/AIR Integration
> Kit
>
> check-runtime-env:
>
> runtime-setup:
>
> mustella-setup:
> [echo] exclude file will be:
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella/tests/Exclude
> ListWin.txt
> [loadfile]
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\local.propert
> ies
> doesn't exist
>
> cleanmustellaswc:
> [delete] Deleting:
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\mustella.swc
> [echo] exclude file will be:
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella/tests/Exclude
> ListWin.txt
> [loadfile]
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\local.propert
> ies
> doesn't exist
>
> get_date:
>
> get_os:
>
> setup_mac:
>
> setup_windows:
> [echo] doing windows setup
> [echo] homepath: C:\Users\hudson
> [echo] trace output file: ${TraceOutputFileEnable}
> [echo] apollo_exe: adl.exe
> [echo] player is C:/Program Files
> (x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
>
> setup_linux:
>
> db_time:
> [echo] db_time=2012/12/12 07:31:44
>
> get_mobile_data:
>
> device_fail:
>
> handle_mobile_config:
>
> echo-browser:
>
> echo-apollo:
>
> setup:
> [echo] player is C:/Program Files
> (x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
> [echo] fileset:
>
> makemustellaswc:
> [echo] exclude file will be:
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella/tests/Exclude
> ListWin.txt
> [loadfile]
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\local.propert
> ies
> doesn't exist
>
> compilemustellaswc:
> [exec] Loading configuration file
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config
> .xml
> [exec]
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\mustella.swc
> (80482 bytes)
>
> load-task:
>
> basictests:
> [mxmlc] Loading configuration file
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config
> .xml
> [mxmlc] Loading configuration file
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basic
> Tests\BasicTests-config.xml
> [mxmlc]
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basic
> Tests\BasicTests.swf
> (3634262 bytes)
> [mxmlc] Loading configuration file
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config
> .xml
> [mxmlc]
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basic
> Tests\basicLoader.swf
> (990 bytes)
> [mxmlc] Loading configuration file
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config
> .xml
> [mxmlc]
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basic
> Tests\spark\views\StyleManagerModuleTest.swf
> (498330 bytes)
> [mxmlc] Loading configuration file
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config
> .xml
> [mxmlc] Required RSLs:
> [mxmlc] framework_1347387.swf
> [mxmlc] textLayout_1347387.swf
> [mxmlc] spark_1347387.swf
> [mxmlc] osmf_1347387.swf
> [mxmlc]
> F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basic
> Tests\spark\views\HelloWorld.swf
> (49319 bytes)
> [echo] launching player and swf
> Build timed out (after 5 minutes). Marking the build as aborted.
> Build was aborted
> Performing Post build task...
> Match found for :Build timed out : True
> Logical operation result is TRUE
> Running script : copy "C:\Documents and Settings\hudson\Application
> Data\Macromedia\Flash Player\Logs\flashlog.txt" .
> [Flex_SDK_checkin_tests] $ cmd /c call
> C:\Users\hudson\AppData\Local\Temp\hudson7455494972728076452.bat
>
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests>copy "C:\Documents
> and Settings\hudson\Application Data\Macromedia\Flash
> Player\Logs\flashlog.txt" .
> The system cannot find the path specified.
>
> f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests>exit 1
> POST BUILD TASK : FAILURE
> END OF POST BUILD TASK : 0
> Finished: ABORTED
>
>
>
>> On 12/11/12 10:24 PM, "Justin Mclean" <ju...@classsoftware.com> 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 the release process.
>>>
>>> It would be great if we could get the checkin tests working on Jenkins,
>> it
>>> should be possible and the flash debug player has been installed on the
>>> windows build box and the Jenkins job is configured with the correct
>> path to
>>> it. Currently the tests hang if you try and run them - no further
>> information
>>> is given so it's a little hard to debug. Any one have any experience with
>>> running anything similar on Jenkins?
>>>
>>> Justin
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: Release target and Jenekins
Posted by Om <bi...@gmail.com>.
On Tue, Dec 11, 2012 at 11:50 PM, Alex Harui <ah...@adobe.com> 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-slave\workspace\Flex_SDK_checkin_tests
Location 'https://svn.apache.org/repos/asf/incubator/flex/trunk' does not
exist
Updating https://svn.apache.org/repos/asf/incubator/flex/trunk
ERROR: Failed to update
https://svn.apache.org/repos/asf/incubator/flex/trunk
org.tmatesoft.svn.core.SVNException: svn: Target path
'/incubator/flex/trunk' does not exist
svn: REPORT of /repos/asf/!svn/vcc/default: 500 Internal Server Error (
https://svn.apache.org)
at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1284)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:830)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:564)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:401)
at
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136)
at
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:788)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:769)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Unknown Source)
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: Target path
'/incubator/flex/trunk' does not exist
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:146)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:89)
at
org.tmatesoft.svn.core.internal.io.dav.handlers.DAVErrorHandler.endElement(DAVErrorHandler.java:72)
at
org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(BasicDAVHandler.java:99)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown
Source)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
Source)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:776)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:741)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readError(HTTPConnection.java:222)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.readError(HTTPRequest.java:290)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:213)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:379)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:292)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:283)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1282)
... 19 more
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: REPORT of
/repos/asf/!svn/vcc/default: 500 Internal Server Error (
https://svn.apache.org)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:181)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:133)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.createDefaultErrorMessage(HTTPRequest.java:444)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.readError(HTTPRequest.java:288)
... 26 more
no change for https://svn.apache.org/repos/asf/incubator/flex/trunk since
the previous build
[Flex_SDK_checkin_tests] $ cmd.exe /C
'"f:\hudson\tools\ant\apache-ant-1.7.0\bin\ant.bat -file jenkins.xml main
&& exit %%ERRORLEVEL%%"'
Buildfile: jenkins.xml
airsdk-check:
airsdk-download:
playerglobal-check:
playerglobal-settarget:
playerglobal10.3-download:
playerglobal11.0-download:
playerglobal11.1-download:
playerglobal11.2-download:
playerglobal11.3-download:
playerglobal-download:
thirdparty-downloads:
main:
BUILD SUCCESSFUL
Total time: 0 seconds
[Flex_SDK_checkin_tests] $ cmd.exe /C
'"f:\hudson\tools\ant\apache-ant-1.7.0\bin\ant.bat -file build.xml
-Dfont.donot.ask="" -Dbuild.number=1373096 -Dblazeds.donot.ask=""
checkintests && exit %%ERRORLEVEL%%"'
Buildfile: build.xml
check-air-home:
[echo] AIR_HOME is
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests/air/AIR Integration
Kit
check-runtime-env:
runtime-setup:
mustella-setup:
[echo] exclude file will be:
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella/tests/ExcludeListWin.txt
[loadfile]
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\local.properties
doesn't exist
cleanmustellaswc:
[delete] Deleting:
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\mustella.swc
[echo] exclude file will be:
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella/tests/ExcludeListWin.txt
[loadfile]
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\local.properties
doesn't exist
get_date:
get_os:
setup_mac:
setup_windows:
[echo] doing windows setup
[echo] homepath: C:\Users\hudson
[echo] trace output file: ${TraceOutputFileEnable}
[echo] apollo_exe: adl.exe
[echo] player is C:/Program Files
(x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
setup_linux:
db_time:
[echo] db_time=2012/12/12 07:31:44
get_mobile_data:
device_fail:
handle_mobile_config:
echo-browser:
echo-apollo:
setup:
[echo] player is C:/Program Files
(x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
[echo] fileset:
makemustellaswc:
[echo] exclude file will be:
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella/tests/ExcludeListWin.txt
[loadfile]
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\local.properties
doesn't exist
compilemustellaswc:
[exec] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config.xml
[exec]
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\mustella\mustella.swc
(80482 bytes)
load-task:
basictests:
[mxmlc] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config.xml
[mxmlc] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basicTests\BasicTests-config.xml
[mxmlc]
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basicTests\BasicTests.swf
(3634262 bytes)
[mxmlc] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config.xml
[mxmlc]
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basicTests\basicLoader.swf
(990 bytes)
[mxmlc] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config.xml
[mxmlc]
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basicTests\spark\views\StyleManagerModuleTest.swf
(498330 bytes)
[mxmlc] Loading configuration file
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\flex-config.xml
[mxmlc] Required RSLs:
[mxmlc] framework_1347387.swf
[mxmlc] textLayout_1347387.swf
[mxmlc] spark_1347387.swf
[mxmlc] osmf_1347387.swf
[mxmlc]
F:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests\frameworks\tests\basicTests\spark\views\HelloWorld.swf
(49319 bytes)
[echo] launching player and swf
Build timed out (after 5 minutes). Marking the build as aborted.
Build was aborted
Performing Post build task...
Match found for :Build timed out : True
Logical operation result is TRUE
Running script : copy "C:\Documents and Settings\hudson\Application
Data\Macromedia\Flash Player\Logs\flashlog.txt" .
[Flex_SDK_checkin_tests] $ cmd /c call
C:\Users\hudson\AppData\Local\Temp\hudson7455494972728076452.bat
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests>copy "C:\Documents
and Settings\hudson\Application Data\Macromedia\Flash
Player\Logs\flashlog.txt" .
The system cannot find the path specified.
f:\hudson\hudson-slave\workspace\Flex_SDK_checkin_tests>exit 1
POST BUILD TASK : FAILURE
END OF POST BUILD TASK : 0
Finished: ABORTED
> On 12/11/12 10:24 PM, "Justin Mclean" <ju...@classsoftware.com> 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 the release process.
> >
> > It would be great if we could get the checkin tests working on Jenkins,
> it
> > should be possible and the flash debug player has been installed on the
> > windows build box and the Jenkins job is configured with the correct
> path to
> > it. Currently the tests hang if you try and run them - no further
> information
> > is given so it's a little hard to debug. Any one have any experience with
> > running anything similar on Jenkins?
> >
> > Justin
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
Re: Release target and Jenekins
Posted by Alex Harui <ah...@adobe.com>.
Can we get the ant output in the console and the flashlog.txt?
On 12/11/12 10:24 PM, "Justin Mclean" <ju...@classsoftware.com> 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 the release process.
>
> It would be great if we could get the checkin tests working on Jenkins, it
> should be possible and the flash debug player has been installed on the
> windows build box and the Jenkins job is configured with the correct path to
> it. Currently the tests hang if you try and run them - no further information
> is given so it's a little hard to debug. Any one have any experience with
> running anything similar on Jenkins?
>
> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui