Jenkins build is back to normal : royale-typedefs #553

[apacheroyaleci]

See 

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

On Sun, Apr 19, 2020 at 11:37 PM Alex Harui 
wrote:

> Royale-compiler has to be built first.  This is an example of shared
> resources that I mentioned upthread.  Royale-typedefs is going to look for
> a sibling workspace folder called royale-compiler with a built of
> royale-compiler in it.  If royale-compiler fails to create all of its
> binaries or is in the process of building them, royale-typedefs will report
> an error.
>

Got it.  I was just looking at the logic here:
https://github.com/apache/royale-typedefs/blob/85c74dde104294a0127ce46a8795d7534216e7eb/js/build.xml#L53

Weird.  The royale-compiler build says it was successful, but I cant find
the lib directory under C:\jenkins\workspace\royale-compiler\compiler-jx




>
> What should probably happen is that royale-typedefs pulls down the
> lastsuccessfulartifacts from royale-compiler, but I've never found enough
> time and energy to try to make changes like that since most of us do have
> all of the folders as siblings.
>
> HTH,
> -Alex
>
> On 4/19/20, 11:31 PM, "OmPrakash Muppirala"  wrote:
>
> I am now getting this error on royale-typedefs build:
>
> BUILD FAILEDc:\jenkins\workspace\royale-typedefs\build.xml:58: The
> following error occurred while executing this line:
> c:\jenkins\workspace\royale-typedefs\js\build.xml:91: src
>
> 'c:\jenkins\workspace\royale-typedefs\js\${ROYALE_TRANSPILER_HOME}\lib\google\closure-compiler\compiler.jar'
> doesn't exist.
>
>
> Where does the ROYALE_TRANSPILER_HOME var come from?
>
> Here is the full console output:
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fview%2FAgent%25202%2520&data=02%7C01%7Caharui%40adobe.com%7Ca55fd899b7b247fcf6f308d7e4f468a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229610695411638&sdata=vvN91svHM9UrGH%2FpsQoFdpyHgyVMwatr5NJ9s9%2FUfzc%3D&reserved=0(Om's%20VM)/job/royale-typedefs/552/console
>
> On Sun, Apr 19, 2020 at 11:24 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> wrote:
>
> > On Sun, Apr 19, 2020 at 11:08 PM Alex Harui  >
> > wrote:
> >
> >> Congratulations!  But does that mean that JAVA_HOME is pointing at
> a JRE
> >> instead of a JDK?  If you have other issues that might be a factor.
> >>
> >
> > Yeah, I messed up initially by getting the JRE instead of JDK.  I
> have
> > since corrected it.  But for some reason Ant still thinks that
> JAVA_HOME is
> > the jre directory.
> > I don't know how to fix this, hence the hack :-|
> >
> >
> >
> >
> >>
> >> HTH,
> >> -Alex
> >>
> >> On 4/19/20, 10:50 PM, "OmPrakash Muppirala" 
> >> wrote:
> >>
> >> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to
> have
> >> fixed
> >> the issue.
> >> We now have a successful build of the royale-compiler on the
> new Agent
> >> machine!!
> >>
> >> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
> >> bigosma...@gmail.com>
> >> wrote:
> >>
> >> > Restart dint help.  Although Serkan's reply made me look at
> how Ant
> >> was
> >> > getting invoked.
> >> >
> >> > I see this warning that tools.jar is missing:
> >> >
> >> > [royale-compiler] $ cmd.exe /C
> >> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
> >> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
> >> %%ERRORLEVEL%%"
> >> >
> >> > Unable to locate tools.jar. Expected to find it in C:\Program
> >> Files\Java\jre1.8.0_251\lib\tools.jar
> >> >
> >> >
> >> > I am pretty sure this is related to this issue.
> >> >
> >> >
> >> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
> >> bigosma...@gmail.com>
> >> > wrote:
> >> >
> >> >>
> >> >>
> >> >> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui
> >> 
> >> >> wrote:
> >> >>
> >> >>> Did you reboot your VM?  Also, have you checked what user is
> >> running
> >> >>> Jenkins on your VM?  I think that can sometimes be a
> problem.  I
> >> might be
> >> >>> running Jenkins as the user.
> >> >>>
> >> >>>
> >> >> Agents don't require Jenkins to be running.  I will give the
> >> rebooting of
> >> >> the VM a shot .
> >> >>
> >> >> Thanks,
> >> >> Om
> >> >>
> >> >>
> >> >>> -Alex
> >> >>>
> >> >>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" <
> bigosma...@gmail.com
> >> >
> >> >>> wrote:
> >> >>>
> >> >>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui
> >> 
> >> >>> wrote:
> >> >>>
> >> >>> > Should be here:
> >> >>> >
> >> >>> >
> >> >>>
> >>
> https://nam04.safelinks.protecti

Re: Prioritize Release Jobs on CI

[Alex Harui]

Royale-compiler has to be built first.  This is an example of shared resources 
that I mentioned upthread.  Royale-typedefs is going to look for a sibling 
workspace folder called royale-compiler with a built of royale-compiler in it.  
If royale-compiler fails to create all of its binaries or is in the process of 
building them, royale-typedefs will report an error.

What should probably happen is that royale-typedefs pulls down the 
lastsuccessfulartifacts from royale-compiler, but I've never found enough time 
and energy to try to make changes like that since most of us do have all of the 
folders as siblings.

HTH,
-Alex

On 4/19/20, 11:31 PM, "OmPrakash Muppirala"  wrote:

I am now getting this error on royale-typedefs build:

BUILD FAILEDc:\jenkins\workspace\royale-typedefs\build.xml:58: The
following error occurred while executing this line:
c:\jenkins\workspace\royale-typedefs\js\build.xml:91: src

'c:\jenkins\workspace\royale-typedefs\js\${ROYALE_TRANSPILER_HOME}\lib\google\closure-compiler\compiler.jar'
doesn't exist.


Where does the ROYALE_TRANSPILER_HOME var come from?

Here is the full console output:

https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fview%2FAgent%25202%2520&data=02%7C01%7Caharui%40adobe.com%7Ca55fd899b7b247fcf6f308d7e4f468a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229610695411638&sdata=vvN91svHM9UrGH%2FpsQoFdpyHgyVMwatr5NJ9s9%2FUfzc%3D&reserved=0(Om's%20VM)/job/royale-typedefs/552/console

On Sun, Apr 19, 2020 at 11:24 PM OmPrakash Muppirala 
wrote:

> On Sun, Apr 19, 2020 at 11:08 PM Alex Harui 
> wrote:
>
>> Congratulations!  But does that mean that JAVA_HOME is pointing at a JRE
>> instead of a JDK?  If you have other issues that might be a factor.
>>
>
> Yeah, I messed up initially by getting the JRE instead of JDK.  I have
> since corrected it.  But for some reason Ant still thinks that JAVA_HOME 
is
> the jre directory.
> I don't know how to fix this, hence the hack :-|
>
>
>
>
>>
>> HTH,
>> -Alex
>>
>> On 4/19/20, 10:50 PM, "OmPrakash Muppirala" 
>> wrote:
>>
>> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have
>> fixed
>> the issue.
>> We now have a successful build of the royale-compiler on the new 
Agent
>> machine!!
>>
>> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> wrote:
>>
>> > Restart dint help.  Although Serkan's reply made me look at how Ant
>> was
>> > getting invoked.
>> >
>> > I see this warning that tools.jar is missing:
>> >
>> > [royale-compiler] $ cmd.exe /C
>> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
>> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
>> %%ERRORLEVEL%%"
>> >
>> > Unable to locate tools.jar. Expected to find it in C:\Program
>> Files\Java\jre1.8.0_251\lib\tools.jar
>> >
>> >
>> > I am pretty sure this is related to this issue.
>> >
>> >
>> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> > wrote:
>> >
>> >>
>> >>
>> >> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui
>> 
>> >> wrote:
>> >>
>> >>> Did you reboot your VM?  Also, have you checked what user is
>> running
>> >>> Jenkins on your VM?  I think that can sometimes be a problem.  I
>> might be
>> >>> running Jenkins as the user.
>> >>>
>> >>>
>> >> Agents don't require Jenkins to be running.  I will give the
>> rebooting of
>> >> the VM a shot .
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >>
>> >>> -Alex
>> >>>
>> >>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" > >
>> >>> wrote:
>> >>>
>> >>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui
>> 
>> >>> wrote:
>> >>>
>> >>> > Should be here:
>> >>> >
>> >>> >
>> >>>
>> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2F&data=02%7C01%7Caharui%40adobe.com%7Ca55fd899b7b247fcf6f308d7e4f468a0%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229610695411638&sdata=L6YhauHRF8IcSIlLJVFGn%2BPY5Ut%2BC9i2OBaNUF2yX20%3D&reserved=0
>> >>>
>> >>>
>> >>> My git is located in the same exact location as master.
>> >>> Moreover, the git call from the commandline executes fine.
>> The git
>> >>> call
>> >>> from ant exec is what is failing.
>> >>>
>> >>>
>> >>>
>> 

Re: Prioritize Release Jobs on CI

[Alex Harui]

On 4/19/20, 11:25 PM, "OmPrakash Muppirala"  wrote:

On Sun, Apr 19, 2020 at 11:08 PM Alex Harui 
wrote:

> Congratulations!  But does that mean that JAVA_HOME is pointing at a JRE
> instead of a JDK?  If you have other issues that might be a factor.
>

Yeah, I messed up initially by getting the JRE instead of JDK.  I have
since corrected it.  But for some reason Ant still thinks that JAVA_HOME is
the jre directory.
I don't know how to fix this, hence the hack :-|

If you want to dig deeper, one idea is to run a Jenkins Job with a batch file 
that dumps out PATH and JAVA_HOME.  This post seems to imply that Ant may store 
info in .antrc and/or ant.conf files.

HTH,
-Alex



>
> HTH,
> -Alex
>
> On 4/19/20, 10:50 PM, "OmPrakash Muppirala"  wrote:
>
> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have
> fixed
> the issue.
> We now have a successful build of the royale-compiler on the new Agent
> machine!!
>
> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> wrote:
>
> > Restart dint help.  Although Serkan's reply made me look at how Ant
> was
> > getting invoked.
> >
> > I see this warning that tools.jar is missing:
> >
> > [royale-compiler] $ cmd.exe /C
> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
> %%ERRORLEVEL%%"
> >
> > Unable to locate tools.jar. Expected to find it in C:\Program
> Files\Java\jre1.8.0_251\lib\tools.jar
> >
> >
> > I am pretty sure this is related to this issue.
> >
> >
> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> > wrote:
> >
> >>
> >>
> >> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui
> 
> >> wrote:
> >>
> >>> Did you reboot your VM?  Also, have you checked what user is
> running
> >>> Jenkins on your VM?  I think that can sometimes be a problem.  I
> might be
> >>> running Jenkins as the user.
> >>>
> >>>
> >> Agents don't require Jenkins to be running.  I will give the
> rebooting of
> >> the VM a shot .
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>> -Alex
> >>>
> >>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" 
> >>> wrote:
> >>>
> >>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui
> 
> >>> wrote:
> >>>
> >>> > Should be here:
> >>> >
> >>> >
> >>>
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2F&data=02%7C01%7Caharui%40adobe.com%7C064142121e184b7a721f08d7e4f39a91%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229607239796954&sdata=VBfhdjYkWvKLxPRasbxtkfkxJRGfGsyMf0w7EmaMQGY%3D&reserved=0
> >>>
> >>>
> >>> My git is located in the same exact location as master.
> >>> Moreover, the git call from the commandline executes fine.
> The git
> >>> call
> >>> from ant exec is what is failing.
> >>>
> >>>
> >>>
> >>> >
> >>> >
> >>> > HTH,
> >>> > -Alex
> >>> >
> >>> > From: OmPrakash Muppirala 
> >>> > Reply-To: "dev@royale.apache.org" 
> >>> > Date: Sunday, April 19, 2020 at 9:37 PM
> >>> > To: Apache Royale Development 
> >>> > Subject: Re: Prioritize Release Jobs on CI
> >>> >
> >>> > I'm a bit stumped here.  The royale-compiler is failing with
> this
> >>> error:
> >>> >
> >>> >
> >>> > BUILD FAILED
> >>> >
> >>> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute
> >>> failed:
> >>> > java.io.IOException: Cannot run program "git" (in directory
> >>> > "c:\jenkins\workspace\royale-compiler"): CreateProcess
> error=2,
> >>> The system
> >>> > cannot find the file specified
> >>> >
> >>> >   at java.lang.ProcessBuilder.start(Unknown Source)
> >>> >
> >>> >
> >>> > It is from this part of the jenkins.xml:
> >>> >
> >>> >
> >>> > 
> >>> > 
> >>> > 
> >>> > 
> >>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7C064142121e184b7a721f08d7e4f39a91%

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

I am now getting this error on royale-typedefs build:

BUILD FAILEDc:\jenkins\workspace\royale-typedefs\build.xml:58: The
following error occurred while executing this line:
c:\jenkins\workspace\royale-typedefs\js\build.xml:91: src
'c:\jenkins\workspace\royale-typedefs\js\${ROYALE_TRANSPILER_HOME}\lib\google\closure-compiler\compiler.jar'
doesn't exist.


Where does the ROYALE_TRANSPILER_HOME var come from?

Here is the full console output:
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/view/Agent%202%20(Om's%20VM)/job/royale-typedefs/552/console

On Sun, Apr 19, 2020 at 11:24 PM OmPrakash Muppirala 
wrote:

> On Sun, Apr 19, 2020 at 11:08 PM Alex Harui 
> wrote:
>
>> Congratulations!  But does that mean that JAVA_HOME is pointing at a JRE
>> instead of a JDK?  If you have other issues that might be a factor.
>>
>
> Yeah, I messed up initially by getting the JRE instead of JDK.  I have
> since corrected it.  But for some reason Ant still thinks that JAVA_HOME is
> the jre directory.
> I don't know how to fix this, hence the hack :-|
>
>
>
>
>>
>> HTH,
>> -Alex
>>
>> On 4/19/20, 10:50 PM, "OmPrakash Muppirala" 
>> wrote:
>>
>> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have
>> fixed
>> the issue.
>> We now have a successful build of the royale-compiler on the new Agent
>> machine!!
>>
>> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> wrote:
>>
>> > Restart dint help.  Although Serkan's reply made me look at how Ant
>> was
>> > getting invoked.
>> >
>> > I see this warning that tools.jar is missing:
>> >
>> > [royale-compiler] $ cmd.exe /C
>> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
>> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
>> %%ERRORLEVEL%%"
>> >
>> > Unable to locate tools.jar. Expected to find it in C:\Program
>> Files\Java\jre1.8.0_251\lib\tools.jar
>> >
>> >
>> > I am pretty sure this is related to this issue.
>> >
>> >
>> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
>> bigosma...@gmail.com>
>> > wrote:
>> >
>> >>
>> >>
>> >> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui
>> 
>> >> wrote:
>> >>
>> >>> Did you reboot your VM?  Also, have you checked what user is
>> running
>> >>> Jenkins on your VM?  I think that can sometimes be a problem.  I
>> might be
>> >>> running Jenkins as the user.
>> >>>
>> >>>
>> >> Agents don't require Jenkins to be running.  I will give the
>> rebooting of
>> >> the VM a shot .
>> >>
>> >> Thanks,
>> >> Om
>> >>
>> >>
>> >>> -Alex
>> >>>
>> >>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" > >
>> >>> wrote:
>> >>>
>> >>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui
>> 
>> >>> wrote:
>> >>>
>> >>> > Should be here:
>> >>> >
>> >>> >
>> >>>
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2F&data=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200405113&sdata=RhBraBN5pQDVrqAbMoXKejWBTwyqtSwd7DURGcQSwUg%3D&reserved=0
>> >>>
>> >>>
>> >>> My git is located in the same exact location as master.
>> >>> Moreover, the git call from the commandline executes fine.
>> The git
>> >>> call
>> >>> from ant exec is what is failing.
>> >>>
>> >>>
>> >>>
>> >>> >
>> >>> >
>> >>> > HTH,
>> >>> > -Alex
>> >>> >
>> >>> > From: OmPrakash Muppirala 
>> >>> > Reply-To: "dev@royale.apache.org" 
>> >>> > Date: Sunday, April 19, 2020 at 9:37 PM
>> >>> > To: Apache Royale Development 
>> >>> > Subject: Re: Prioritize Release Jobs on CI
>> >>> >
>> >>> > I'm a bit stumped here.  The royale-compiler is failing
>> with this
>> >>> error:
>> >>> >
>> >>> >
>> >>> > BUILD FAILED
>> >>> >
>> >>> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute
>> >>> failed:
>> >>> > java.io.IOException: Cannot run program "git" (in directory
>> >>> > "c:\jenkins\workspace\royale-compiler"): CreateProcess
>> error=2,
>> >>> The system
>> >>> > cannot find the file specified
>> >>> >
>> >>> >   at java.lang.ProcessBuilder.start(Unknown Source)
>> >>> >
>> >>> >
>> >>> > It is from this part of the jenkins.xml:
>> >>> >
>> >>> >
>> >>> > 
>> >>> > 
>> >>> > 
>> >>> > 
>> >>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

On Sun, Apr 19, 2020 at 11:08 PM Alex Harui 
wrote:

> Congratulations!  But does that mean that JAVA_HOME is pointing at a JRE
> instead of a JDK?  If you have other issues that might be a factor.
>

Yeah, I messed up initially by getting the JRE instead of JDK.  I have
since corrected it.  But for some reason Ant still thinks that JAVA_HOME is
the jre directory.
I don't know how to fix this, hence the hack :-|




>
> HTH,
> -Alex
>
> On 4/19/20, 10:50 PM, "OmPrakash Muppirala"  wrote:
>
> I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have
> fixed
> the issue.
> We now have a successful build of the royale-compiler on the new Agent
> machine!!
>
> On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> wrote:
>
> > Restart dint help.  Although Serkan's reply made me look at how Ant
> was
> > getting invoked.
> >
> > I see this warning that tools.jar is missing:
> >
> > [royale-compiler] $ cmd.exe /C
> "C:\apache\apache-ant-1.9.9\bin\ant.bat -file jenkins.xml
> -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit
> %%ERRORLEVEL%%"
> >
> > Unable to locate tools.jar. Expected to find it in C:\Program
> Files\Java\jre1.8.0_251\lib\tools.jar
> >
> >
> > I am pretty sure this is related to this issue.
> >
> >
> > On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala <
> bigosma...@gmail.com>
> > wrote:
> >
> >>
> >>
> >> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui
> 
> >> wrote:
> >>
> >>> Did you reboot your VM?  Also, have you checked what user is
> running
> >>> Jenkins on your VM?  I think that can sometimes be a problem.  I
> might be
> >>> running Jenkins as the user.
> >>>
> >>>
> >> Agents don't require Jenkins to be running.  I will give the
> rebooting of
> >> the VM a shot .
> >>
> >> Thanks,
> >> Om
> >>
> >>
> >>> -Alex
> >>>
> >>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" 
> >>> wrote:
> >>>
> >>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui
> 
> >>> wrote:
> >>>
> >>> > Should be here:
> >>> >
> >>> >
> >>>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2F&data=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200405113&sdata=RhBraBN5pQDVrqAbMoXKejWBTwyqtSwd7DURGcQSwUg%3D&reserved=0
> >>>
> >>>
> >>> My git is located in the same exact location as master.
> >>> Moreover, the git call from the commandline executes fine.
> The git
> >>> call
> >>> from ant exec is what is failing.
> >>>
> >>>
> >>>
> >>> >
> >>> >
> >>> > HTH,
> >>> > -Alex
> >>> >
> >>> > From: OmPrakash Muppirala 
> >>> > Reply-To: "dev@royale.apache.org" 
> >>> > Date: Sunday, April 19, 2020 at 9:37 PM
> >>> > To: Apache Royale Development 
> >>> > Subject: Re: Prioritize Release Jobs on CI
> >>> >
> >>> > I'm a bit stumped here.  The royale-compiler is failing with
> this
> >>> error:
> >>> >
> >>> >
> >>> > BUILD FAILED
> >>> >
> >>> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute
> >>> failed:
> >>> > java.io.IOException: Cannot run program "git" (in directory
> >>> > "c:\jenkins\workspace\royale-compiler"): CreateProcess
> error=2,
> >>> The system
> >>> > cannot find the file specified
> >>> >
> >>> >   at java.lang.ProcessBuilder.start(Unknown Source)
> >>> >
> >>> >
> >>> > It is from this part of the jenkins.xml:
> >>> >
> >>> >
> >>> > 
> >>> > 
> >>> > 
> >>> > 
> >>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200405113&sdata=AJO8lF1H7VG%2Fy9T1I9p0%2Fsqjh8cQ8U8exbInYHyuch0%3D&reserved=0
> >>> <
> >>> >
> >>>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200415104&sdata=2%2BG3WpItozbraXCp2Q4XACBXizsHNZQYMAgiSaaPXwo%3D&reserved=0
> >>> >"
> >>> > />
> >>> > 
> >>> > 
> >>> > Cloned fresh copy of Google Closure
> Library
> >>> > 
> >>> >
> >>> > I am not sure how this executable call works without the
> full path.
> >>> >
> >>> > I checked the env va

Re: Prioritize Release Jobs on CI

[Alex Harui]

Congratulations!  But does that mean that JAVA_HOME is pointing at a JRE 
instead of a JDK?  If you have other issues that might be a factor.

HTH,
-Alex

On 4/19/20, 10:50 PM, "OmPrakash Muppirala"  wrote:

I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have fixed
the issue.
We now have a successful build of the royale-compiler on the new Agent
machine!!

On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala 
wrote:

> Restart dint help.  Although Serkan's reply made me look at how Ant was
> getting invoked.
>
> I see this warning that tools.jar is missing:
>
> [royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-file jenkins.xml -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit 
%%ERRORLEVEL%%"
>
> Unable to locate tools.jar. Expected to find it in C:\Program 
Files\Java\jre1.8.0_251\lib\tools.jar
>
>
> I am pretty sure this is related to this issue.
>
>
> On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala 

> wrote:
>
>>
>>
>> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui 
>> wrote:
>>
>>> Did you reboot your VM?  Also, have you checked what user is running
>>> Jenkins on your VM?  I think that can sometimes be a problem.  I might 
be
>>> running Jenkins as the user.
>>>
>>>
>> Agents don't require Jenkins to be running.  I will give the rebooting of
>> the VM a shot .
>>
>> Thanks,
>> Om
>>
>>
>>> -Alex
>>>
>>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" 
>>> wrote:
>>>
>>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui 

>>> wrote:
>>>
>>> > Should be here:
>>> >
>>> >
>>> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2F&data=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200405113&sdata=RhBraBN5pQDVrqAbMoXKejWBTwyqtSwd7DURGcQSwUg%3D&reserved=0
>>>
>>>
>>> My git is located in the same exact location as master.
>>> Moreover, the git call from the commandline executes fine.  The git
>>> call
>>> from ant exec is what is failing.
>>>
>>>
>>>
>>> >
>>> >
>>> > HTH,
>>> > -Alex
>>> >
>>> > From: OmPrakash Muppirala 
>>> > Reply-To: "dev@royale.apache.org" 
>>> > Date: Sunday, April 19, 2020 at 9:37 PM
>>> > To: Apache Royale Development 
>>> > Subject: Re: Prioritize Release Jobs on CI
>>> >
>>> > I'm a bit stumped here.  The royale-compiler is failing with this
>>> error:
>>> >
>>> >
>>> > BUILD FAILED
>>> >
>>> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute
>>> failed:
>>> > java.io.IOException: Cannot run program "git" (in directory
>>> > "c:\jenkins\workspace\royale-compiler"): CreateProcess error=2,
>>> The system
>>> > cannot find the file specified
>>> >
>>> >   at java.lang.ProcessBuilder.start(Unknown Source)
>>> >
>>> >
>>> > It is from this part of the jenkins.xml:
>>> >
>>> >
>>> > 
>>> > 
>>> > 
>>> > 
>>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200405113&sdata=AJO8lF1H7VG%2Fy9T1I9p0%2Fsqjh8cQ8U8exbInYHyuch0%3D&reserved=0
>>> <
>>> >
>>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Cae66be53fa804cc3c74108d7e4eeb2a3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229586200415104&sdata=2%2BG3WpItozbraXCp2Q4XACBXizsHNZQYMAgiSaaPXwo%3D&reserved=0
>>> >"
>>> > />
>>> > 
>>> > 
>>> > Cloned fresh copy of Google Closure Library
>>> > 
>>> >
>>> > I am not sure how this executable call works without the full 
path.
>>> >
>>> > I checked the env variables, I do have both the git/bin and 
git/cmd
>>> > directory in the PATH:
>>> >
>>> > [cid:ii_k97zkk9o0]
>>> >
>>> > What am I missing?
>>> >
>>> > Thanks,
>>> > Om
>>> >
>>> > On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala <
>>> bigosma...@gmail.com
>>> > > wrote:
>>> > Update - I have successfully attached my VM as a slave agent of 
our
>>> > Jenkins instance.
>>> > I am going to pull the job - /royale-asjs_jsonl

Build failed in Jenkins: royale-typedefs #552

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/apache/royale-typedefs
 > C:\Program Files\Git\cmd\git.exe init 
 > 
 >  # timeout=10
Fetching upstream changes from https://github.com/apache/royale-typedefs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-typedefs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-typedefs # timeout=10
 > C:\Program Files\Git\cmd\git.exe config --add remote.origin.fetch 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-typedefs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-typedefs
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-typedefs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 85c74dde104294a0127ce46a8795d7534216e7eb 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 85c74dde104294a0127ce46a8795d7534216e7eb
Commit message: "Use royale-extras ie_dom file"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 85c74dde104294a0127ce46a8795d7534216e7eb # timeout=10
[royale-typedefs] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-Dbuild.number=552 main && exit %%ERRORLEVEL%%"
Buildfile: 


main:
 [echo] swc-date is 04/20/20 05:53 +

download:
 [echo] 

[mkdir] Created dir: 


BUILD FAILED
:58:
 The following error occurred while executing this line:
:91:
 src 
'
 doesn't exist.

Total time: 0 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1024m
Build step 'Invoke Ant' marked build as failure

Build failed in Jenkins: royale-asjs_jsonly #1330

[apacheroyaleci]

See 


Changes:


--
[...truncated 137.28 KB...]
check-for-tests:

clean-tests:

package-clean:

clean-temp:
   [delete] Deleting directory 


checkintests-clean:

mxtests-clean:

clean:
   [delete] Deleting: 

   [delete] Deleting directory 

 [echo] ROYALE_HOME = 

 [echo] royalelib = 

 [echo] doc_output = 

 [echo] compiler.source-path = 


clean:

super-clean:
   [delete] Deleting directory 


create-description:
 [echo] build.number is 20200420

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

tweak-for-jsonly:
 [copy] Warning: Could not find file 

 to copy.
 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:
[mkdir] Created dir: 


stage-source:

clean-temp:
[mkdir] Created dir: 

 [copy] Copying 6570 files to 

 [copy] Copied 2372 empty directories to 1 empty directory under 

 [echo] Updating config file air-config.xml with version 0.9.7.20200420
 [echo] Updating config file royale-config.xml with version 0.9.7.20200420
 [echo] Updating config file js-config.xml with version 0.9.7.20200420
 [echo] Updating config file jquery-config.xml with version 0.9.7.20200420
 [echo] Updating config file ace-config.xml with version 0.9.7.20200420
 [echo] Updating config file createjs-config.xml with version 0.9.7.20200420
 [echo] Updating config file node-config.xml with version 0.9.7.20200420

stage-compiler:

wipe-all:

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-build-tools\target\classes

wipe:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-build-tools\target

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-jburg-types\target\classes

wipe:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-compiler\compiler-jburg-types\target

clean:
   [delete] Deleting directory 
C:\jenkins\workspace\royale-

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

I copied tools.jar from  jdk/lib to the jre/lib.  That seems to have fixed
the issue.
We now have a successful build of the royale-compiler on the new Agent
machine!!

On Sun, Apr 19, 2020 at 10:44 PM OmPrakash Muppirala 
wrote:

> Restart dint help.  Although Serkan's reply made me look at how Ant was
> getting invoked.
>
> I see this warning that tools.jar is missing:
>
> [royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat -file 
> jenkins.xml -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit 
> %%ERRORLEVEL%%"
>
> Unable to locate tools.jar. Expected to find it in C:\Program 
> Files\Java\jre1.8.0_251\lib\tools.jar
>
>
> I am pretty sure this is related to this issue.
>
>
> On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala 
> wrote:
>
>>
>>
>> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui 
>> wrote:
>>
>>> Did you reboot your VM?  Also, have you checked what user is running
>>> Jenkins on your VM?  I think that can sometimes be a problem.  I might be
>>> running Jenkins as the user.
>>>
>>>
>> Agents don't require Jenkins to be running.  I will give the rebooting of
>> the VM a shot .
>>
>> Thanks,
>> Om
>>
>>
>>> -Alex
>>>
>>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" 
>>> wrote:
>>>
>>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui 
>>> wrote:
>>>
>>> > Should be here:
>>> >
>>> >
>>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2F&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=YJq3Ac1xpVWwyQDyFRgYmlcrGXs10W04hhON5QE0%2B90%3D&reserved=0
>>>
>>>
>>> My git is located in the same exact location as master.
>>> Moreover, the git call from the commandline executes fine.  The git
>>> call
>>> from ant exec is what is failing.
>>>
>>>
>>>
>>> >
>>> >
>>> > HTH,
>>> > -Alex
>>> >
>>> > From: OmPrakash Muppirala 
>>> > Reply-To: "dev@royale.apache.org" 
>>> > Date: Sunday, April 19, 2020 at 9:37 PM
>>> > To: Apache Royale Development 
>>> > Subject: Re: Prioritize Release Jobs on CI
>>> >
>>> > I'm a bit stumped here.  The royale-compiler is failing with this
>>> error:
>>> >
>>> >
>>> > BUILD FAILED
>>> >
>>> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute
>>> failed:
>>> > java.io.IOException: Cannot run program "git" (in directory
>>> > "c:\jenkins\workspace\royale-compiler"): CreateProcess error=2,
>>> The system
>>> > cannot find the file specified
>>> >
>>> >   at java.lang.ProcessBuilder.start(Unknown Source)
>>> >
>>> >
>>> > It is from this part of the jenkins.xml:
>>> >
>>> >
>>> > 
>>> > 
>>> > 
>>> > 
>>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=9fgEZdqrtoj75jvA8i0Yi%2FZj6X2rjgIkuShBpIv4Z1I%3D&reserved=0
>>> <
>>> >
>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=9fgEZdqrtoj75jvA8i0Yi%2FZj6X2rjgIkuShBpIv4Z1I%3D&reserved=0
>>> >"
>>> > />
>>> > 
>>> > 
>>> > Cloned fresh copy of Google Closure Library
>>> > 
>>> >
>>> > I am not sure how this executable call works without the full path.
>>> >
>>> > I checked the env variables, I do have both the git/bin and git/cmd
>>> > directory in the PATH:
>>> >
>>> > [cid:ii_k97zkk9o0]
>>> >
>>> > What am I missing?
>>> >
>>> > Thanks,
>>> > Om
>>> >
>>> > On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala <
>>> bigosma...@gmail.com
>>> > > wrote:
>>> > Update - I have successfully attached my VM as a slave agent of our
>>> > Jenkins instance.
>>> > I am going to pull the job - /royale-asjs_jsonly and tie it to my
>>> agent so
>>> > I can test it.
>>> >
>>> > It will fail for a sometime while I go set up my VM with all the
>>> > dependencies.
>>> >
>>> > Once we have the job successfully building on my VM, we can figure
>>> out how
>>> > to divide the load between the master and agent.
>>> >
>>> > Thanks,
>>> > Om
>>> >
>>> > On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala <
>>> bigosma...@gmail.com
>>> > > wrote:
>>> > We could achieve the same by creating a new agent (separate vm) and
>>> > attaching it as a slave to the current Jenkins server.
>>> >
>>> > Then we can use labels/tags to tie 

Jenkins build is back to normal : royale-compiler #364

[apacheroyaleci]

See 

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

Restart dint help.  Although Serkan's reply made me look at how Ant was
getting invoked.

I see this warning that tools.jar is missing:

[royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat
-file jenkins.xml -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs
main && exit %%ERRORLEVEL%%"

Unable to locate tools.jar. Expected to find it in C:\Program
Files\Java\jre1.8.0_251\lib\tools.jar


I am pretty sure this is related to this issue.


On Sun, Apr 19, 2020 at 10:29 PM OmPrakash Muppirala 
wrote:

>
>
> On Sun, Apr 19, 2020 at 10:15 PM Alex Harui 
> wrote:
>
>> Did you reboot your VM?  Also, have you checked what user is running
>> Jenkins on your VM?  I think that can sometimes be a problem.  I might be
>> running Jenkins as the user.
>>
>>
> Agents don't require Jenkins to be running.  I will give the rebooting of
> the VM a shot .
>
> Thanks,
> Om
>
>
>> -Alex
>>
>> On 4/19/20, 10:01 PM, "OmPrakash Muppirala" 
>> wrote:
>>
>> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui 
>> wrote:
>>
>> > Should be here:
>> >
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2F&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=YJq3Ac1xpVWwyQDyFRgYmlcrGXs10W04hhON5QE0%2B90%3D&reserved=0
>>
>>
>> My git is located in the same exact location as master.
>> Moreover, the git call from the commandline executes fine.  The git
>> call
>> from ant exec is what is failing.
>>
>>
>>
>> >
>> >
>> > HTH,
>> > -Alex
>> >
>> > From: OmPrakash Muppirala 
>> > Reply-To: "dev@royale.apache.org" 
>> > Date: Sunday, April 19, 2020 at 9:37 PM
>> > To: Apache Royale Development 
>> > Subject: Re: Prioritize Release Jobs on CI
>> >
>> > I'm a bit stumped here.  The royale-compiler is failing with this
>> error:
>> >
>> >
>> > BUILD FAILED
>> >
>> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute failed:
>> > java.io.IOException: Cannot run program "git" (in directory
>> > "c:\jenkins\workspace\royale-compiler"): CreateProcess error=2, The
>> system
>> > cannot find the file specified
>> >
>> >   at java.lang.ProcessBuilder.start(Unknown Source)
>> >
>> >
>> > It is from this part of the jenkins.xml:
>> >
>> >
>> > 
>> > 
>> > 
>> > 
>> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=9fgEZdqrtoj75jvA8i0Yi%2FZj6X2rjgIkuShBpIv4Z1I%3D&reserved=0
>> <
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=9fgEZdqrtoj75jvA8i0Yi%2FZj6X2rjgIkuShBpIv4Z1I%3D&reserved=0
>> >"
>> > />
>> > 
>> > 
>> > Cloned fresh copy of Google Closure Library
>> > 
>> >
>> > I am not sure how this executable call works without the full path.
>> >
>> > I checked the env variables, I do have both the git/bin and git/cmd
>> > directory in the PATH:
>> >
>> > [cid:ii_k97zkk9o0]
>> >
>> > What am I missing?
>> >
>> > Thanks,
>> > Om
>> >
>> > On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala <
>> bigosma...@gmail.com
>> > > wrote:
>> > Update - I have successfully attached my VM as a slave agent of our
>> > Jenkins instance.
>> > I am going to pull the job - /royale-asjs_jsonly and tie it to my
>> agent so
>> > I can test it.
>> >
>> > It will fail for a sometime while I go set up my VM with all the
>> > dependencies.
>> >
>> > Once we have the job successfully building on my VM, we can figure
>> out how
>> > to divide the load between the master and agent.
>> >
>> > Thanks,
>> > Om
>> >
>> > On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala <
>> bigosma...@gmail.com
>> > > wrote:
>> > We could achieve the same by creating a new agent (separate vm) and
>> > attaching it as a slave to the current Jenkins server.
>> >
>> > Then we can use labels/tags to tie release jobs to one agent and non
>> > release jobs to another agent.
>> >
>> > That way we can maintain everything in one UI, one login while
>> achieving
>> > the concurrent building capabilities we want.
>> >
>> > Jenkins is built for this kind of stuff and I think it would be
>> best we
>> > followed this practice.
>> >
>> > Thanks,
>> > Om

Build failed in Jenkins: royale-compiler #363

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-compiler # timeout=10
Fetching upstream changes from https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-compiler +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 86bbb1e4d69569dc538a3e25041305a9c673a1e8 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 86bbb1e4d69569dc538a3e25041305a9c673a1e8
Commit message: "release-notes: added improvements to Maven by chris dutz and 
enhancements to create maven distribution that now is working"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 86bbb1e4d69569dc538a3e25041305a9c673a1e8 # timeout=10
[royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat -file 
jenkins.xml -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit 
%%ERRORLEVEL%%"
Unable to locate tools.jar. Expected to find it in C:\Program 
Files\Java\jre1.8.0_251\lib\tools.jar
Buildfile: 


clean:
   [delete] Deleting directory 

   [delete] Deleting directory 

   [delete] Deleting directory C:\Google\Closure\Library

init:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: C:\Google\Closure\Library

jflex-download:
 [echo] Be patient. This takes a few minutes...
  [get] Getting: https://jflex.de/jflex-1.4.3.zip
  [get] To: 

[unzip] Expanding: 

 into 


closure-lib-download:
 [echo] Be patient. This takes a few minutes...
 [exec] Cloning into 'C:\Google\Closure\Library'...
 [echo] Cloned fresh copy of Google Closure Library

check-env:

env-properties:

main:

BUILD SUCCESSFUL
Total time: 16 seconds
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1024m
[royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-Dbuild.number=363 -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs clean main 
&& exit %%ERRORLEVEL%%"
Unable to locate tools.jar. Expected to find it in C:\Program 
Files\Java\jre1.8.0_251\lib\tools.jar
Buildfile: 


clean:

clean:

clean:

clean:
 [echo] RELEASE_VERSION IS: 0.9.7

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:

clean:
 [echo] basedir is 

 [echo] ROYALE_COMPILER_HOME is ${ROYALE_COMPILER_HOME}
 [echo] ROYALE_COMPILER_HOME is c:\compiler-jx

clean:

clean:
 [echo] Cleaning out dist dir: 


clean:
 [echo] Cleaning out generated dir: target/generated-sources/jburg/
 [echo] Cleaning out output dir: 


sdk:

annotate.class:
[mkdir] Created dir: 


BUILD FAILED
:63:
 The following error occurred while executing this line:

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

On Sun, Apr 19, 2020 at 10:05 PM serkan  wrote:

> It should be related with the shell which ant is executed in.
>
> It seems like you should set PATH for that shell.
>

Thanks for the reply!
I'm not sure how I would do that?


>
>
> 20.04.2020 07:36 tarihinde OmPrakash Muppirala yazdı:
>
> I'm a bit stumped here.  The royale-compiler is failing with this error:
>
>
> BUILD FAILEDc:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute 
> failed: java.io.IOException: Cannot run program "git" (in directory 
> "c:\jenkins\workspace\royale-compiler"): CreateProcess error=2, The system 
> cannot find the file specified
>   at java.lang.ProcessBuilder.start(Unknown Source)
>
> It is from this part of the jenkins.xml:
>
>
> 
> 
> 
> 
> https://github.com/google/closure-library"; />
> 
> 
> Cloned fresh copy of Google Closure Library
> 
>
> I am not sure how this executable call works without the full path.
>
> I checked the env variables, I do have both the git/bin and git/cmd
> directory in the PATH:
>
> [image: image.png]
>
> What am I missing?
>
> Thanks,
> Om
>
> On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala 
> wrote:
>
>> Update - I have successfully attached my VM as a slave agent of our
>> Jenkins instance.
>> I am going to pull the job - /royale-asjs_jsonly and tie it to my agent
>> so I can test it.
>>
>> It will fail for a sometime while I go set up my VM with all the
>> dependencies.
>>
>> Once we have the job successfully building on my VM, we can figure out
>> how to divide the load between the master and agent.
>>
>> Thanks,
>> Om
>>
>> On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala 
>> wrote:
>>
>>> We could achieve the same by creating a new agent (separate vm) and
>>> attaching it as a slave to the current Jenkins server.
>>>
>>> Then we can use labels/tags to tie release jobs to one agent and non
>>> release jobs to another agent.
>>>
>>> That way we can maintain everything in one UI, one login while achieving
>>> the concurrent building capabilities we want.
>>>
>>> Jenkins is built for this kind of stuff and I think it would be best we
>>> followed this practice.
>>>
>>> Thanks,
>>> Om
>>>
>>> On Sat, Apr 18, 2020, 8:18 AM Alex Harui 
>>>  wrote:
>>>
 Om, I thought you were going to get the image from my VM and run it on
 another VM.  Then we'd remove all non-release jobs from your VM and all of
 the release jobs from my VM.  That won't solve the problem of how long it
 takes for a commit to be built and tested, but will allow the RM to get a
 release out without getting stuck behind the commit jobs.  Is that
 currently the plan?

 -Alex

 On 4/18/20, 12:43 AM, "OmPrakash Muppirala" 
 wrote:

 Makes sense to me.  I will set parallel executors back to 1.

 And start working on a new Jenkins instance.

 Thanks,
 Om


 On Sat, Apr 18, 2020, 12:28 AM Alex Harui
   wrote:

 > Are you saying that Java, Ant and Maven do not know how to
 distribute work
 > to different cores?
 >
 > To repeat my main concern:  our Jenkins jobs often use shared
 resources.
 > If you want to take the time to fix that, feel free, but I do not
 know how
 > you are going to keep two jobs from both trying to launch Flash
 Player
 > Debugger at the same time and open the same socket to communicate
 with it,
 > or try to parse the flashlog.txt that they have both written to.
 >
 > The royale-asjs job will use the royale-compiler workspace to get
 the
 > compiler.  If the compiler is building, the jars are not there
 and the
 > royale-asjs build fails.
 >
 > There is also only so much memory and some of our jobs use all of
 it and
 > I'm not sure if jobs slowed down due to paging memory and
 writing/reading
 > from disk, even if it is an SSD.
 >
 > I'm done for tonight, but that's what I was seeing last time I
 tried to
 > have both master and an agent running jobs in parallel.
 >
 > Thanks,
 > -Alex
 >
 > On 4/17/20, 11:52 PM, "OmPrakash Muppirala" 
 wrote:
 >
 > A typical setup would be to have 0 executors on master and at
 least n
 > number of executors on each agent, where n = number of cpu
 cores.
 > I see that the current VM has 2 cores.  So, I started with
 setting the
 > num
 > executors on the current agent to 2.
 >
 > This should improve things quite a bit.  If this doesn't
 work, I will
 > create a new VM and make it the slave agent of the current
 Jenkins
 > master.
 >
 >
 > Thanks,
 > Om
 >
 > On 

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

On Sun, Apr 19, 2020 at 10:15 PM Alex Harui 
wrote:

> Did you reboot your VM?  Also, have you checked what user is running
> Jenkins on your VM?  I think that can sometimes be a problem.  I might be
> running Jenkins as the user.
>
>
Agents don't require Jenkins to be running.  I will give the rebooting of
the VM a shot .

Thanks,
Om


> -Alex
>
> On 4/19/20, 10:01 PM, "OmPrakash Muppirala"  wrote:
>
> On Sun, Apr 19, 2020 at 9:55 PM Alex Harui 
> wrote:
>
> > Should be here:
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2F&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=YJq3Ac1xpVWwyQDyFRgYmlcrGXs10W04hhON5QE0%2B90%3D&reserved=0
>
>
> My git is located in the same exact location as master.
> Moreover, the git call from the commandline executes fine.  The git
> call
> from ant exec is what is failing.
>
>
>
> >
> >
> > HTH,
> > -Alex
> >
> > From: OmPrakash Muppirala 
> > Reply-To: "dev@royale.apache.org" 
> > Date: Sunday, April 19, 2020 at 9:37 PM
> > To: Apache Royale Development 
> > Subject: Re: Prioritize Release Jobs on CI
> >
> > I'm a bit stumped here.  The royale-compiler is failing with this
> error:
> >
> >
> > BUILD FAILED
> >
> > c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute failed:
> > java.io.IOException: Cannot run program "git" (in directory
> > "c:\jenkins\workspace\royale-compiler"): CreateProcess error=2, The
> system
> > cannot find the file specified
> >
> >   at java.lang.ProcessBuilder.start(Unknown Source)
> >
> >
> > It is from this part of the jenkins.xml:
> >
> >
> > 
> > 
> > 
> > 
> > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=9fgEZdqrtoj75jvA8i0Yi%2FZj6X2rjgIkuShBpIv4Z1I%3D&reserved=0
> <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=9fgEZdqrtoj75jvA8i0Yi%2FZj6X2rjgIkuShBpIv4Z1I%3D&reserved=0
> >"
> > />
> > 
> > 
> > Cloned fresh copy of Google Closure Library
> > 
> >
> > I am not sure how this executable call works without the full path.
> >
> > I checked the env variables, I do have both the git/bin and git/cmd
> > directory in the PATH:
> >
> > [cid:ii_k97zkk9o0]
> >
> > What am I missing?
> >
> > Thanks,
> > Om
> >
> > On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala <
> bigosma...@gmail.com
> > > wrote:
> > Update - I have successfully attached my VM as a slave agent of our
> > Jenkins instance.
> > I am going to pull the job - /royale-asjs_jsonly and tie it to my
> agent so
> > I can test it.
> >
> > It will fail for a sometime while I go set up my VM with all the
> > dependencies.
> >
> > Once we have the job successfully building on my VM, we can figure
> out how
> > to divide the load between the master and agent.
> >
> > Thanks,
> > Om
> >
> > On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala <
> bigosma...@gmail.com
> > > wrote:
> > We could achieve the same by creating a new agent (separate vm) and
> > attaching it as a slave to the current Jenkins server.
> >
> > Then we can use labels/tags to tie release jobs to one agent and non
> > release jobs to another agent.
> >
> > That way we can maintain everything in one UI, one login while
> achieving
> > the concurrent building capabilities we want.
> >
> > Jenkins is built for this kind of stuff and I think it would be best
> we
> > followed this practice.
> >
> > Thanks,
> > Om
> > On Sat, Apr 18, 2020, 8:18 AM Alex Harui 
> wrote:
> > Om, I thought you were going to get the image from my VM and run it
> on
> > another VM.  Then we'd remove all non-release jobs from your VM and
> all of
> > the release jobs from my VM.  That won't solve the problem of how
> long it
> > takes for a commit to be built and tested, but will allow the RM to
> get a
> > release out without getting stuck behind the commit jobs.  Is that
> > currently the plan?
> >
> > -Alex
> >
> > On 4/18/20, 12:43 AM, "OmPrakash Muppirala"   > bigosma...@gmail.com>> wrote:
> >
> > Makes sense to me.  I wil

Re: Prioritize Release Jobs on CI

[Alex Harui]

Did you reboot your VM?  Also, have you checked what user is running Jenkins on 
your VM?  I think that can sometimes be a problem.  I might be running Jenkins 
as the user.

-Alex

On 4/19/20, 10:01 PM, "OmPrakash Muppirala"  wrote:

On Sun, Apr 19, 2020 at 9:55 PM Alex Harui  wrote:

> Should be here:
>
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2FconfigureTools%2F&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=YJq3Ac1xpVWwyQDyFRgYmlcrGXs10W04hhON5QE0%2B90%3D&reserved=0


My git is located in the same exact location as master.
Moreover, the git call from the commandline executes fine.  The git call
from ant exec is what is failing.



>
>
> HTH,
> -Alex
>
> From: OmPrakash Muppirala 
> Reply-To: "dev@royale.apache.org" 
> Date: Sunday, April 19, 2020 at 9:37 PM
> To: Apache Royale Development 
> Subject: Re: Prioritize Release Jobs on CI
>
> I'm a bit stumped here.  The royale-compiler is failing with this error:
>
>
> BUILD FAILED
>
> c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute failed:
> java.io.IOException: Cannot run program "git" (in directory
> "c:\jenkins\workspace\royale-compiler"): CreateProcess error=2, The system
> cannot find the file specified
>
>   at java.lang.ProcessBuilder.start(Unknown Source)
>
>
> It is from this part of the jenkins.xml:
>
>
> 
> 
> 
> 
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=9fgEZdqrtoj75jvA8i0Yi%2FZj6X2rjgIkuShBpIv4Z1I%3D&reserved=0<
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7Ce57b89ef99cd486fd83508d7e4e7e84d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229557003118752&sdata=9fgEZdqrtoj75jvA8i0Yi%2FZj6X2rjgIkuShBpIv4Z1I%3D&reserved=0>"
> />
> 
> 
> Cloned fresh copy of Google Closure Library
> 
>
> I am not sure how this executable call works without the full path.
>
> I checked the env variables, I do have both the git/bin and git/cmd
> directory in the PATH:
>
> [cid:ii_k97zkk9o0]
>
> What am I missing?
>
> Thanks,
> Om
>
> On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala  > wrote:
> Update - I have successfully attached my VM as a slave agent of our
> Jenkins instance.
> I am going to pull the job - /royale-asjs_jsonly and tie it to my agent so
> I can test it.
>
> It will fail for a sometime while I go set up my VM with all the
> dependencies.
>
> Once we have the job successfully building on my VM, we can figure out how
> to divide the load between the master and agent.
>
> Thanks,
> Om
>
> On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala  > wrote:
> We could achieve the same by creating a new agent (separate vm) and
> attaching it as a slave to the current Jenkins server.
>
> Then we can use labels/tags to tie release jobs to one agent and non
> release jobs to another agent.
>
> That way we can maintain everything in one UI, one login while achieving
> the concurrent building capabilities we want.
>
> Jenkins is built for this kind of stuff and I think it would be best we
> followed this practice.
>
> Thanks,
> Om
> On Sat, Apr 18, 2020, 8:18 AM Alex Harui  wrote:
> Om, I thought you were going to get the image from my VM and run it on
> another VM.  Then we'd remove all non-release jobs from your VM and all of
> the release jobs from my VM.  That won't solve the problem of how long it
> takes for a commit to be built and tested, but will allow the RM to get a
> release out without getting stuck behind the commit jobs.  Is that
> currently the plan?
>
> -Alex
>
> On 4/18/20, 12:43 AM, "OmPrakash Muppirala"  bigosma...@gmail.com>> wrote:
>
> Makes sense to me.  I will set parallel executors back to 1.
>
> And start working on a new Jenkins instance.
>
> Thanks,
> Om
>
>
> On Sat, Apr 18, 2020, 12:28 AM Alex Harui 
> wrote:
>
> > Are you saying that Java, Ant and Maven do not know how to
> distribute work
> > to different cores?
> >
> > To repeat my main concern:  our Jenkins jobs often use shared
> resources.
> > I

Re: Prioritize Release Jobs on CI

[serkan]

It should be related with the shell which ant is executed in.

It seems like you should set PATH for that shell.

20.04.2020 07:36 tarihinde OmPrakash Muppirala yazdı:

I'm a bit stumped here.  The royale-compiler is failing with this error:

BUILD FAILED c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute failed: 
java.io.IOException: Cannot run program "git" (in directory 
"c:\jenkins\workspace\royale-compiler"): CreateProcess error=2, The system cannot find 
the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
It is from this part of the jenkins.xml:


    

        
        
            
            https://github.com/google/closure-library"; />
            
        
        Cloned fresh copy of Google Closure Library
    

I am not sure how this executable call works without the full path.

I checked the env variables, I do have both the git/bin and git/cmd 
directory in the PATH:


image.png

What am I missing?

Thanks,
Om

On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala 
mailto:bigosma...@gmail.com>> wrote:


Update - I have successfully attached my VM as a slave agent of
our Jenkins instance.
I am going to pull the job - /royale-asjs_jsonly and tie it to my
agent so I can test it.

It will fail for a sometime while I go set up my VM with all the
dependencies.

Once we have the job successfully building on my VM, we can figure
out how to divide the load between the master and agent.

Thanks,
Om

On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala
mailto:bigosma...@gmail.com>> wrote:

We could achieve the same by creating a new agent (separate
vm) and attaching it as a slave to the current Jenkins server.

Then we can use labels/tags to tie release jobs to one agent
and non release jobs to another agent.

That way we can maintain everything in one UI, one login while
achieving the concurrent building capabilities we want.

Jenkins is built for this kind of stuff and I think it would
be best we followed this practice.

Thanks,
Om

On Sat, Apr 18, 2020, 8:18 AM Alex Harui
 wrote:

Om, I thought you were going to get the image from my VM
and run it on another VM.  Then we'd remove all
non-release jobs from your VM and all of the release jobs
from my VM.  That won't solve the problem of how long it
takes for a commit to be built and tested, but will allow
the RM to get a release out without getting stuck behind
the commit jobs.  Is that currently the plan?

-Alex

On 4/18/20, 12:43 AM, "OmPrakash Muppirala"
mailto:bigosma...@gmail.com>> wrote:

    Makes sense to me.  I will set parallel executors back
to 1.

    And start working on a new Jenkins instance.

    Thanks,
    Om


    On Sat, Apr 18, 2020, 12:28 AM Alex Harui
 wrote:

    > Are you saying that Java, Ant and Maven do not know
how to distribute work
    > to different cores?
    >
    > To repeat my main concern:  our Jenkins jobs often
use shared resources.
    > If you want to take the time to fix that, feel free,
but I do not know how
    > you are going to keep two jobs from both trying to
launch Flash Player
    > Debugger at the same time and open the same socket
to communicate with it,
    > or try to parse the flashlog.txt that they have both
written to.
    >
    > The royale-asjs job will use the royale-compiler
workspace to get the
    > compiler.  If the compiler is building, the jars are
not there and the
    > royale-asjs build fails.
    >
    > There is also only so much memory and some of our
jobs use all of it and
    > I'm not sure if jobs slowed down due to paging
memory and writing/reading
    > from disk, even if it is an SSD.
    >
    > I'm done for tonight, but that's what I was seeing
last time I tried to
    > have both master and an agent running jobs in parallel.
    >
    > Thanks,
    > -Alex
    >
    > On 4/17/20, 11:52 PM, "OmPrakash Muppirala"
mailto:bigosma...@gmail.com>> wrote:
    >
    >     A typical setup would be to have 0 executors on
master and at least n
    >     number of executors on each agent, where n =
number of cpu cores.
    >     I see that the current VM has 2 cores.  So, I
started with setting the
  

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

On Sun, Apr 19, 2020 at 9:55 PM Alex Harui  wrote:

> Should be here:
>
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/configureTools/


My git is located in the same exact location as master.
Moreover, the git call from the commandline executes fine.  The git call
from ant exec is what is failing.



>
>
> HTH,
> -Alex
>
> From: OmPrakash Muppirala 
> Reply-To: "dev@royale.apache.org" 
> Date: Sunday, April 19, 2020 at 9:37 PM
> To: Apache Royale Development 
> Subject: Re: Prioritize Release Jobs on CI
>
> I'm a bit stumped here.  The royale-compiler is failing with this error:
>
>
> BUILD FAILED
>
> c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute failed:
> java.io.IOException: Cannot run program "git" (in directory
> "c:\jenkins\workspace\royale-compiler"): CreateProcess error=2, The system
> cannot find the file specified
>
>   at java.lang.ProcessBuilder.start(Unknown Source)
>
>
> It is from this part of the jenkins.xml:
>
>
> 
> 
> 
> 
> https://github.com/google/closure-library<
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgoogle%2Fclosure-library&data=02%7C01%7Caharui%40adobe.com%7C0dd5709b5c23458c5f0508d7e4e47f47%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229542364320116&sdata=yH8RnSomTWYMU5qKf%2FnQhztdjHhVRIb%2BdtmaU6cIUzQ%3D&reserved=0>"
> />
> 
> 
> Cloned fresh copy of Google Closure Library
> 
>
> I am not sure how this executable call works without the full path.
>
> I checked the env variables, I do have both the git/bin and git/cmd
> directory in the PATH:
>
> [cid:ii_k97zkk9o0]
>
> What am I missing?
>
> Thanks,
> Om
>
> On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala  > wrote:
> Update - I have successfully attached my VM as a slave agent of our
> Jenkins instance.
> I am going to pull the job - /royale-asjs_jsonly and tie it to my agent so
> I can test it.
>
> It will fail for a sometime while I go set up my VM with all the
> dependencies.
>
> Once we have the job successfully building on my VM, we can figure out how
> to divide the load between the master and agent.
>
> Thanks,
> Om
>
> On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala  > wrote:
> We could achieve the same by creating a new agent (separate vm) and
> attaching it as a slave to the current Jenkins server.
>
> Then we can use labels/tags to tie release jobs to one agent and non
> release jobs to another agent.
>
> That way we can maintain everything in one UI, one login while achieving
> the concurrent building capabilities we want.
>
> Jenkins is built for this kind of stuff and I think it would be best we
> followed this practice.
>
> Thanks,
> Om
> On Sat, Apr 18, 2020, 8:18 AM Alex Harui  wrote:
> Om, I thought you were going to get the image from my VM and run it on
> another VM.  Then we'd remove all non-release jobs from your VM and all of
> the release jobs from my VM.  That won't solve the problem of how long it
> takes for a commit to be built and tested, but will allow the RM to get a
> release out without getting stuck behind the commit jobs.  Is that
> currently the plan?
>
> -Alex
>
> On 4/18/20, 12:43 AM, "OmPrakash Muppirala"  bigosma...@gmail.com>> wrote:
>
> Makes sense to me.  I will set parallel executors back to 1.
>
> And start working on a new Jenkins instance.
>
> Thanks,
> Om
>
>
> On Sat, Apr 18, 2020, 12:28 AM Alex Harui 
> wrote:
>
> > Are you saying that Java, Ant and Maven do not know how to
> distribute work
> > to different cores?
> >
> > To repeat my main concern:  our Jenkins jobs often use shared
> resources.
> > If you want to take the time to fix that, feel free, but I do not
> know how
> > you are going to keep two jobs from both trying to launch Flash
> Player
> > Debugger at the same time and open the same socket to communicate
> with it,
> > or try to parse the flashlog.txt that they have both written to.
> >
> > The royale-asjs job will use the royale-compiler workspace to get the
> > compiler.  If the compiler is building, the jars are not there and
> the
> > royale-asjs build fails.
> >
> > There is also only so much memory and some of our jobs use all of it
> and
> > I'm not sure if jobs slowed down due to paging memory and
> writing/reading
> > from disk, even if it is an SSD.
> >
> > I'm done for tonight, but that's what I was seeing last time I tried
> to
> > have both master and an agent running jobs in parallel.
> >
> > Thanks,
> > -Alex
> >
> > On 4/17/20, 11:52 PM, "OmPrakash Muppirala"  > wrote:
> >
> > A typical setup would be to have 0 executors on master and at
> least n
> > number of executors on each agent, where n = number of cpu cores.
> > I see that the current VM has 2 cores.  So, I starte

Re: Prioritize Release Jobs on CI

[Alex Harui]

Should be here:

http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/configureTools/

HTH,
-Alex

From: OmPrakash Muppirala 
Reply-To: "dev@royale.apache.org" 
Date: Sunday, April 19, 2020 at 9:37 PM
To: Apache Royale Development 
Subject: Re: Prioritize Release Jobs on CI

I'm a bit stumped here.  The royale-compiler is failing with this error:


BUILD FAILED

c:\jenkins\workspace\royale-compiler\jenkins.xml:55: Execute failed: 
java.io.IOException: Cannot run program "git" (in directory 
"c:\jenkins\workspace\royale-compiler"): CreateProcess error=2, The system 
cannot find the file specified

  at java.lang.ProcessBuilder.start(Unknown Source)


It is from this part of the jenkins.xml:






https://github.com/google/closure-library"
 />


Cloned fresh copy of Google Closure Library


I am not sure how this executable call works without the full path.

I checked the env variables, I do have both the git/bin and git/cmd directory 
in the PATH:

[cid:ii_k97zkk9o0]

What am I missing?

Thanks,
Om

On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala 
mailto:bigosma...@gmail.com>> wrote:
Update - I have successfully attached my VM as a slave agent of our Jenkins 
instance.
I am going to pull the job - /royale-asjs_jsonly and tie it to my agent so I 
can test it.

It will fail for a sometime while I go set up my VM with all the dependencies.

Once we have the job successfully building on my VM, we can figure out how to 
divide the load between the master and agent.

Thanks,
Om

On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala 
mailto:bigosma...@gmail.com>> wrote:
We could achieve the same by creating a new agent (separate vm) and attaching 
it as a slave to the current Jenkins server.

Then we can use labels/tags to tie release jobs to one agent and non release 
jobs to another agent.

That way we can maintain everything in one UI, one login while achieving the 
concurrent building capabilities we want.

Jenkins is built for this kind of stuff and I think it would be best we 
followed this practice.

Thanks,
Om
On Sat, Apr 18, 2020, 8:18 AM Alex Harui  wrote:
Om, I thought you were going to get the image from my VM and run it on another 
VM.  Then we'd remove all non-release jobs from your VM and all of the release 
jobs from my VM.  That won't solve the problem of how long it takes for a 
commit to be built and tested, but will allow the RM to get a release out 
without getting stuck behind the commit jobs.  Is that currently the plan?

-Alex

On 4/18/20, 12:43 AM, "OmPrakash Muppirala" 
mailto:bigosma...@gmail.com>> wrote:

Makes sense to me.  I will set parallel executors back to 1.

And start working on a new Jenkins instance.

Thanks,
Om


On Sat, Apr 18, 2020, 12:28 AM Alex Harui  wrote:

> Are you saying that Java, Ant and Maven do not know how to distribute work
> to different cores?
>
> To repeat my main concern:  our Jenkins jobs often use shared resources.
> If you want to take the time to fix that, feel free, but I do not know how
> you are going to keep two jobs from both trying to launch Flash Player
> Debugger at the same time and open the same socket to communicate with it,
> or try to parse the flashlog.txt that they have both written to.
>
> The royale-asjs job will use the royale-compiler workspace to get the
> compiler.  If the compiler is building, the jars are not there and the
> royale-asjs build fails.
>
> There is also only so much memory and some of our jobs use all of it and
> I'm not sure if jobs slowed down due to paging memory and writing/reading
> from disk, even if it is an SSD.
>
> I'm done for tonight, but that's what I was seeing last time I tried to
> have both master and an agent running jobs in parallel.
>
> Thanks,
> -Alex
>
> On 4/17/20, 11:52 PM, "OmPrakash Muppirala" 
mailto:bigosma...@gmail.com>> wrote:
>
> A typical setup would be to have 0 executors on master and at least n
> number of executors on each agent, where n = number of cpu cores.
> I see that the current VM has 2 cores.  So, I started with setting the
> num
> executors on the current agent to 2.
>
> This should improve things quite a bit.  If this doesn't work, I will
> create a new VM and make it the slave agent of the current Jenkins
> master.
>
>
> Thanks,
> Om
>
> On Fri, Apr 17, 2020 at 11:31 PM Alex Harui 
> wrote:
>
> > On your VM or mine?  I don't think mine can handle it.  I used to

Re: Build failed in Jenkins: royale-asjs #1097

[Alex Harui]

Hmm.  We enabled SSH.  I wonder if that changed security on sockets somehow.  
Is RoyaleUnit using a known socket port number?

Or maybe it is time to reboot the server.

-Alex

On 4/19/20, 12:03 AM, "Greg Dove"  wrote:

Did RoyaleUnits use of sockets change  How were tests running in the past
months?

AFAIK nothing changed in terms of how the tests are run by RoyaleUnit -
they launch the browser (chrome) and use websocket connection back to
royaleunit for js - same as they have been doing for many months now since
Josh set it up. I did make a change not so long ago to launch release
builds instead of debug builds, but I don't understand why that would
suddenly cause anything to stop working after it had been working without
issue for 2 weeks. Everything seemed to be working ok until CI build #1090,
and they also worked as normal for me locally this morning with up to date
code for a full build as well. Maybe something else changed on the server?



On Sun, Apr 19, 2020 at 5:13 PM Alex Harui  wrote:

> Did RoyaleUnits use of sockets change  How were tests running in the past
> months?
>
> -Alex
>
> On 4/18/20, 1:57 PM, "Greg Dove"  wrote:
>
> I am not sure what the actual issue on the server here is. It is 
saying
> there is a socket timeout issue from the browser launch.
> But this does provide an opportunity for a quick example of the
> information
> I shared recently about the changes to tests for JS, and it might be
> helpful for you to see that with a 'live' example.
>
> For the part of the output:
>
> [royaleunit] Executing 'C:\Program Files
> (x86)\Google\Chrome\Application\chrome.exe' with arguments:
> [royaleunit] '<
>
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2Fws%2Fframeworks%2Fjs%2Fprojects%2FBasicJS%2Fsrc%2Ftest%2Froyale%2Ftarget%2Fbin%2Fjs-release%2Findex.html&data=02%7C01%7Caharui%40adobe.com%7C8321911e6d794c46cbeb08d7e42fb50b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637228765870436810&sdata=L8Bad6RMwPW1SOB8eAw0JvOjYGjvjTAr0B%2BqQOIcPpQ%3D&reserved=0
> '>
>
> If you simply launch that link in a browser you will see the normal
> launch
> of the royaleunit BasicJS tests (it is a blank white page - not
> particularly interesting in itself). If you look in the dev tools
> console for that page, you can see that it also did not find a socket
> server to connect to to report back the test results (which is
> definitely
> expected when you launch it like this, because there is of course none
> available).
> But you also will also see this in the console:
> For javascript you can run this locally with console output for
> debugging
> purposes, using "?local" appended to the url.
> It may not work for all browsers with file:// protocol (works with
> Chrome),
> in which case you need a local http server
>
> So if you append
> ?local
> to the url by simply typing that at the end of the original url in the
> browser and reload, you will see the following in the console:
>
> [JS] flexUnitTests::DataGridColumnTest.testLabelProperty .
> [JS] Time: 0.038
> [JS] OK (1 test)
>
> ...which means the tests themselves are not the problem here. There
> was no
> suggestion that they were...this was just to illustrate how you can
> toggle
> between CI style tests and console output of test results.
> The build error may indicate some issue with the chrome launch itself
> I am
> guessing (not sure).
> Aside: The css is not being served as the correct MIME type, so you
> may see
> console errors for that as well, but I think that has always been the
> case
> on the CI server (not sure).
>
>
>
> On Sun, Apr 19, 2020 at 8:19 AM  wrote:
>
> > See <
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2F1097%2Fdisplay%2Fredirect%3Fpage%3Dchanges&data=02%7C01%7Caharui%40adobe.com%7C8321911e6d794c46cbeb08d7e42fb50b%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637228765870436810&sdata=k3G5W%2BLxSp%2Fp%2BHJtExsKhOM9dLu3xfSBffOXt6CZ4kU%3D&reserved=0
> > >
> >
> > Changes:
> >
> > [carlosrovira] markdown-example: highlight as3 and mxml
> >
> >
> > --
> > [...truncated 1.34 MB...]
> > [mxmlc] Loading configuration: <
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2

Re: Routing (was Re: Spectrum Components)

[Alex Harui]

I think there are apps that only use the hash, some that use only parameters, 
and some that will use both, so PAYG would not require the hash-only people to 
carry code for parameters and vice versa.

-Alex

On 4/19/20, 5:34 AM, "Piotr Zarzycki"  wrote:

Hi Alex,

Could you elaborate what do you mean exactly in that case saying PAYG?
Parameter parsing should be done in different version of Router ?

Thanks,
Piotr

pt., 17 kwi 2020 o 17:54 Alex Harui  napisał(a):

> Ideally, supporting the route information in parameters vs hash would be
> done in a PAYG way.
>
> AIUI, hash has to be used as the delimiter if you plan to change the route
> information within the application, otherwise the application will reload.
> IOW, if the user is going to navigate in the appiication and the route
> information is going to change as they navigate, hash should be used.  If,
> on the other hand, there are a bunch of links on a website to click and 
you
> end up on a "page", then URL parameters is probably ok.
>
> I don't understand the concern about the dev branch version.  The release
> branch for 0.9.7 has been cut.  Any changes that go in develop are going 
in
> the next release.  That's how the git branching model works.  You can make
> any change you want in the dev branch right now.  It just won't be in the
> 0.9.7 release unless the RM decides to cherry-pick it, which they should
> not unless it is really important.  What am I missing?
>
> -Alex
>
> On 4/17/20, 3:09 AM, "Harbs"  wrote:
>
> Whatever you think is fine by me.
>
> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get rid of that conditional.
>
> It could be you can get rid of that and handle hashRecieved in a bead.
> If the hashReceived event has no hash you can then check the URL.You do
> need to make sure that you always get a stateChange event and don’t
> dispatch it twice.
>
> Feel free to play around with the code… ;-)
>
> Harbs
>
> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com> wrote:
> >
> > I think it would be better to have it here in Router.
> >
> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >
> >> Alternatively, you can subclass Router to support setting the
> parameters
> >> in the onInit method.
> >>
> >> Not sure which of these is best.
> >>
> >>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >>>
> >>> Actually, it’s not going to work because the
> >> router.routeState.parameters will not be set.
> >>>
> >>> You will likely need to add code to set the
> router.routeState.parameters
> >> using the part of the location after the question mark.
> >>>
> >>> The easiest way to do that would be to either:
> >>> 1. Modify RouteToParameters.stateChanged to first check that there
> is a
> >> parameters value and then set it if not.
> >>> 2. Subclass RouteToParameters and override stateChanged to make
> that
> >> check first.
> >>>
>  On Apr 17, 2020, at 10:29 AM, Harbs   >> harbs.li...@gmail.com>> wrote:
> 
>  I’m pretty sure it’ll work without the hash as well.
> 
>  Give it a try.
> 
> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com >
> wrote:
> >
> > Hi Harbs,
> >
> > Thanks for pointing me out, but this is still that Routing
> expects me
> >> to
> > use in url hashes - The question is - What if I can't use
> hashes, but
> >> url
> > looks like I have presented in previous email ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 09:20 Harbs  >> harbs.li...@gmail.com>> napisał(a):
> >
> >> This app uses both path based and query based routing:
> >>
> >>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddark&data=02%7C01%7Caharui%40adobe.com%7C8b503852fe2b407798eb08d7e45df281%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637228964470465928&sdata=vVYdOwC6mmZw%2FpSH6jGXfyS%2BhLbLCovT9laawtoQpU8%3D&reserved=0
> <
> >>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddark&data=02%7C01%7Caharui%40adobe.com%7C8b503852fe2b407798eb08d7e45df281%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637228964470465928&sdata=vVYdOwC6mmZw%2FpSH6jGX

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

I'm a bit stumped here.  The royale-compiler is failing with this error:


BUILD FAILEDc:\jenkins\workspace\royale-compiler\jenkins.xml:55:
Execute failed: java.io.IOException: Cannot run program "git" (in
directory "c:\jenkins\workspace\royale-compiler"): CreateProcess
error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)


It is from this part of the jenkins.xml:






https://github.com/google/closure-library"; />


Cloned fresh copy of Google Closure Library


I am not sure how this executable call works without the full path.

I checked the env variables, I do have both the git/bin and git/cmd
directory in the PATH:

[image: image.png]

What am I missing?

Thanks,
Om

On Sat, Apr 18, 2020 at 11:54 PM OmPrakash Muppirala 
wrote:

> Update - I have successfully attached my VM as a slave agent of our
> Jenkins instance.
> I am going to pull the job - /royale-asjs_jsonly and tie it to my agent so
> I can test it.
>
> It will fail for a sometime while I go set up my VM with all the
> dependencies.
>
> Once we have the job successfully building on my VM, we can figure out how
> to divide the load between the master and agent.
>
> Thanks,
> Om
>
> On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala 
> wrote:
>
>> We could achieve the same by creating a new agent (separate vm) and
>> attaching it as a slave to the current Jenkins server.
>>
>> Then we can use labels/tags to tie release jobs to one agent and non
>> release jobs to another agent.
>>
>> That way we can maintain everything in one UI, one login while achieving
>> the concurrent building capabilities we want.
>>
>> Jenkins is built for this kind of stuff and I think it would be best we
>> followed this practice.
>>
>> Thanks,
>> Om
>>
>> On Sat, Apr 18, 2020, 8:18 AM Alex Harui 
>> wrote:
>>
>>> Om, I thought you were going to get the image from my VM and run it on
>>> another VM.  Then we'd remove all non-release jobs from your VM and all of
>>> the release jobs from my VM.  That won't solve the problem of how long it
>>> takes for a commit to be built and tested, but will allow the RM to get a
>>> release out without getting stuck behind the commit jobs.  Is that
>>> currently the plan?
>>>
>>> -Alex
>>>
>>> On 4/18/20, 12:43 AM, "OmPrakash Muppirala" 
>>> wrote:
>>>
>>> Makes sense to me.  I will set parallel executors back to 1.
>>>
>>> And start working on a new Jenkins instance.
>>>
>>> Thanks,
>>> Om
>>>
>>>
>>> On Sat, Apr 18, 2020, 12:28 AM Alex Harui 
>>> wrote:
>>>
>>> > Are you saying that Java, Ant and Maven do not know how to
>>> distribute work
>>> > to different cores?
>>> >
>>> > To repeat my main concern:  our Jenkins jobs often use shared
>>> resources.
>>> > If you want to take the time to fix that, feel free, but I do not
>>> know how
>>> > you are going to keep two jobs from both trying to launch Flash
>>> Player
>>> > Debugger at the same time and open the same socket to communicate
>>> with it,
>>> > or try to parse the flashlog.txt that they have both written to.
>>> >
>>> > The royale-asjs job will use the royale-compiler workspace to get
>>> the
>>> > compiler.  If the compiler is building, the jars are not there and
>>> the
>>> > royale-asjs build fails.
>>> >
>>> > There is also only so much memory and some of our jobs use all of
>>> it and
>>> > I'm not sure if jobs slowed down due to paging memory and
>>> writing/reading
>>> > from disk, even if it is an SSD.
>>> >
>>> > I'm done for tonight, but that's what I was seeing last time I
>>> tried to
>>> > have both master and an agent running jobs in parallel.
>>> >
>>> > Thanks,
>>> > -Alex
>>> >
>>> > On 4/17/20, 11:52 PM, "OmPrakash Muppirala" 
>>> wrote:
>>> >
>>> > A typical setup would be to have 0 executors on master and at
>>> least n
>>> > number of executors on each agent, where n = number of cpu
>>> cores.
>>> > I see that the current VM has 2 cores.  So, I started with
>>> setting the
>>> > num
>>> > executors on the current agent to 2.
>>> >
>>> > This should improve things quite a bit.  If this doesn't work,
>>> I will
>>> > create a new VM and make it the slave agent of the current
>>> Jenkins
>>> > master.
>>> >
>>> >
>>> > Thanks,
>>> > Om
>>> >
>>> > On Fri, Apr 17, 2020 at 11:31 PM Alex Harui
>>> 
>>> > wrote:
>>> >
>>> > > On your VM or mine?  I don't think mine can handle it.  I
>>> used to
>>> > run jobs
>>> > > of master and agent and we got lots of failures and jobs took
>>> > forever.  If
>>> > > two jobs are trying to run tests with the shared Flash Player
>>> > Debugger, for
>>> > > example, you won't get consistent results.
>>> > >
>>> 

Build failed in Jenkins: royale-asjs_jsonly #1329

[apacheroyaleci]

See 


Changes:


--
[...truncated 133.32 KB...]

check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 04:05 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 04:05 +
   [delete] Deleting: 


check-for-tests:

clean-tests:

package-clean:

clean-temp:
   [delete] Deleting directory 


checkintests-clean:

mxtests-clean:

clean:
   [delete] Deleting: 

   [delete] Deleting directory 

 [echo] ROYALE_HOME = 

 [echo] royalelib = 

 [echo] doc_output = 

 [echo] compiler.source-path = 


clean:

super-clean:
   [delete] Deleting directory 


create-description:
 [echo] build.number is 20200420

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

tweak-for-jsonly:
 [copy] Warning: Could not find file 

 to copy.
 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:
[mkdir] Created dir: 


stage-source:

clean-temp:
[mkdir] Created dir: 

 [copy] Copying 6570 files to 

 [copy] Copied 2372 empty directories to 1 empty directory under 

 [echo] Updating config file air-config.xml with version 0.9.7.20200420
 [echo] Updating config file royale-config.xml with version 0.9.7.20200420
 

Build failed in Jenkins: royale-asjs_jsonly #1328

[apacheroyaleci]

See 


Changes:


--
[...truncated 132.69 KB...]

check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 02:40 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 02:40 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 02:40 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 02:40 +
   [delete] Deleting: 


check-for-tests:

clean-tests:

package-clean:

clean-temp:
   [delete] Deleting directory 


checkintests-clean:

mxtests-clean:

clean:
   [delete] Deleting: 

   [delete] Deleting directory 

 [echo] ROYALE_HOME = 

 [echo] royalelib = 

 [echo] doc_output = 

 [echo] compiler.source-path = 


clean:

super-clean:
   [delete] Deleting directory 


create-description:
 [echo] build.number is 20200420

js-output-royale-description:

swf-js-output-royale-description:

create-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

tweak-for-jsonly:
 [copy] Warning: Could not find file 

 to copy.
 [copy] Copying 1 file to 


check-royale-config:

fixup-royale-config:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:

playerglobal-setswfversion:

create-config:
 [copy] Copying 1 file to 


tweak-for-jsonly:
[mkdir] Created dir: 


stage-source:

clean-temp:
[mkdir] Created dir: 

 [copy] Copying 6570 files to 

 [copy] Copied 2372 empty directories to 1 empty directory under 

 [echo] Updating config file air-config.xml with version 0.9.7.20200420
 [echo] Updating config file royale-config.xml with version 0.9.7.20200420
 

Build failed in Jenkins: royale-compiler #359

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd rev-parse --is-inside-work-tree # timeout=10
ERROR: Workspace has a .git repository, but it appears to be corrupt.
hudson.plugins.git.GitException: Error performing command: C:\Program 
Files\Git\cmd rev-parse --is-inside-work-tree
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2181)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2142)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2138)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1743)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1755)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.hasGitRepo(CliGitAPIImpl.java:331)
at hudson.plugins.git.GitAPI.hasGitRepo(GitAPI.java:232)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
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.lambda$newThread$0(Engine.java:93)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Cannot run program "C:\Program Files\Git\cmd" 
(in directory 
":
 CreateProcess error=5, Access is denied
at java.lang.ProcessBuilder.start(Unknown Source)
at hudson.Proc$LocalProc.(Proc.java:250)
at hudson.Proc$LocalProc.(Proc.java:219)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:937)
at hudson.Launcher$ProcStarter.start(Launcher.java:455)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2170)
... 22 more
Caused by: java.io.IOException: CreateProcess error=5, Access is denied
at java.lang.ProcessImpl.create(Native Method)
at java.lang.ProcessImpl.(Unknown Source)
at java.lang.ProcessImpl.start(Unknown Source)
... 28 more
Cloning the remote Git repository
Cloning repository https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd init 
 > 
 >  # timeout=10
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:918)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:710)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
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.lambda$newThread$0(Engine.java:93)
at java.lang.Thread.run(Unknown Source)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
JNLP4-connect connection from 52.251.60.60/52.251.60.60:55744

Build failed in Jenkins: royale-compiler #360

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd init 
 > 
 >  # timeout=10
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:918)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:710)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
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.lambda$newThread$0(Engine.java:93)
at java.lang.Thread.run(Unknown Source)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
JNLP4-connect connection from 52.251.60.60/52.251.60.60:55744
at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
at hudson.remoting.Channel.call(Channel.java:957)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown 
Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
at com.sun.proxy.$Proxy65.execute(Unknown Source)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1152)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
at hudson.scm.SCM.checkout(SCM.java:504)
at 
hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at 
jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1815)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at 
hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Caused by: hudson.plugins.git.GitException: Error performing command: 
C:\Program Files\Git\cmd init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2181)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2142)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2138)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1743)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:916)
... 12 more
Caused by: java.io.IOException: Cannot run program "C:\Program Files\Git\cmd" 
(in directory 
":
 CreateProcess error=5, Access is denied
at java.lang.ProcessBuilder.start(Unknown Source)
at hudson.Proc$LocalProc.(Proc.java:250)
at hudson.Proc$LocalProc.(Proc.java:219)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:937)
at hudson.Launcher$ProcStarter.start(Launcher.java:455)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2170)
... 16 more
Caused by: java.io.

Build failed in Jenkins: royale-compiler #362

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-compiler # timeout=10
Fetching upstream changes from https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-compiler +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 86bbb1e4d69569dc538a3e25041305a9c673a1e8 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 86bbb1e4d69569dc538a3e25041305a9c673a1e8
Commit message: "release-notes: added improvements to Maven by chris dutz and 
enhancements to create maven distribution that now is working"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 86bbb1e4d69569dc538a3e25041305a9c673a1e8 # timeout=10
[royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat -file 
jenkins.xml -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit 
%%ERRORLEVEL%%"
Unable to locate tools.jar. Expected to find it in C:\Program Files 
(x86)\Java\jre1.8.0_251\lib\tools.jar
Buildfile: 


clean:
   [delete] Deleting directory 

   [delete] Deleting directory 

   [delete] Deleting directory C:\Google\Closure\Library

init:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: C:\Google\Closure\Library

jflex-download:
 [echo] Be patient. This takes a few minutes...
  [get] Getting: https://jflex.de/jflex-1.4.3.zip
  [get] To: 

[unzip] Expanding: 

 into 


closure-lib-download:
 [echo] Be patient. This takes a few minutes...

BUILD FAILED
:55:
 Execute failed: java.io.IOException: Cannot run program "git" (in directory 
":
 CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at 
org.apache.tools.ant.taskdefs.launcher.Java13CommandLauncher.exec(Java13CommandLauncher.java:58)
at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:426)
at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:440)
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:629)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:670)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:496)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
at org.apache.tools.ant.Project.executeTarget(Project.java:1376)
at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Projec

Build failed in Jenkins: royale-compiler #361

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd\git.exe init 
 > 
 >  # timeout=10
Fetching upstream changes from https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-compiler +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-compiler # timeout=10
 > C:\Program Files\Git\cmd\git.exe config --add remote.origin.fetch 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-compiler # timeout=10
Fetching upstream changes from https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-compiler +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 86bbb1e4d69569dc538a3e25041305a9c673a1e8 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 86bbb1e4d69569dc538a3e25041305a9c673a1e8
Commit message: "release-notes: added improvements to Maven by chris dutz and 
enhancements to create maven distribution that now is working"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 86bbb1e4d69569dc538a3e25041305a9c673a1e8 # timeout=10
[royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat -file 
jenkins.xml -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit 
%%ERRORLEVEL%%"
Unable to locate tools.jar. Expected to find it in C:\Program Files 
(x86)\Java\jre1.8.0_251\lib\tools.jar
Buildfile: 


clean:
   [delete] Deleting directory C:\Google\Closure\Library

init:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: C:\Google\Closure\Library

jflex-download:
 [echo] Be patient. This takes a few minutes...
  [get] Getting: https://jflex.de/jflex-1.4.3.zip
  [get] To: 

[unzip] Expanding: 

 into 


closure-lib-download:
 [echo] Be patient. This takes a few minutes...

BUILD FAILED
:55:
 Execute failed: java.io.IOException: Cannot run program "git" (in directory 
":
 CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at 
org.apache.tools.ant.taskdefs.launcher.Java13CommandLauncher.exec(Java13CommandLauncher.java:58)
at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:426)
at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:440)
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:629)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:670)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:496)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.per

Build failed in Jenkins: royale-compiler #358

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-compiler # timeout=10
Fetching upstream changes from https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-compiler +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 86bbb1e4d69569dc538a3e25041305a9c673a1e8 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 86bbb1e4d69569dc538a3e25041305a9c673a1e8
Commit message: "release-notes: added improvements to Maven by chris dutz and 
enhancements to create maven distribution that now is working"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 86bbb1e4d69569dc538a3e25041305a9c673a1e8 # timeout=10
[royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat -file 
jenkins.xml -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit 
%%ERRORLEVEL%%"
Unable to locate tools.jar. Expected to find it in C:\Program Files 
(x86)\Java\jre1.8.0_251\lib\tools.jar
Buildfile: 


clean:
   [delete] Deleting directory 

   [delete] Deleting directory 

   [delete] Deleting directory C:\Google\Closure\Library

init:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: C:\Google\Closure\Library

jflex-download:
 [echo] Be patient. This takes a few minutes...
  [get] Getting: https://jflex.de/jflex-1.4.3.zip
  [get] To: 

[unzip] Expanding: 

 into 


closure-lib-download:
 [echo] Be patient. This takes a few minutes...

BUILD FAILED
:55:
 Execute failed: java.io.IOException: Cannot run program "git" (in directory 
":
 CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at 
org.apache.tools.ant.taskdefs.launcher.Java13CommandLauncher.exec(Java13CommandLauncher.java:58)
at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:426)
at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:440)
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:629)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:670)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:496)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405)
at org.apache.tools.ant.Project.executeTarget(Project.java:1376)
at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Projec

Build failed in Jenkins: royale-asjs #1100

[apacheroyaleci]

See 


Changes:

[carlosrovira] markdown-example: make links have target and rel attributes. Add 
some

[carlosrovira] markdown-example: fix highlightAuto


--
[...truncated 1.34 MB...]
[mxmlc] Loading configuration: 

[mxmlc] 
[mxmlc] 94130 bytes written to 

 in 7.166 seconds
[mxmlc] 9.133873 seconds
[mxmlc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g

test:
[mkdir] Created dir: 

[royaleunit] Validating task attributes ...
[royaleunit] Generating default values ...
[royaleunit] Using the following settings for the test run:
[royaleunit]ROYALE_HOME: 
[
[royaleunit]haltonfailure: [true]
[royaleunit]headless: [false]
[royaleunit]display: [99]
[royaleunit]localTrusted: [true]
[royaleunit]player: [flash]
[royaleunit]port: [1024]
[royaleunit]swf: 
[
[royaleunit]timeout: [9ms]
[royaleunit]toDir: 
[
[royaleunit] Setting up server process ...
[royaleunit] Entry 
[
 already available in local trust file at 
[C:\Users\ApacheRoyaleCI\AppData\Roaming\Macromedia\Flash 
Player\#Security\FlashPlayerTrust\royaleUnit.cfg].
[royaleunit] Executing 'rundll32' with arguments:
[royaleunit] 'url.dll,FileProtocolHandler'
[royaleunit] 
'
[royaleunit] 
[royaleunit] The ' characters around the executable and arguments are
[royaleunit] not part of the command.
[royaleunit] 
[royaleunit] Starting server ...
[royaleunit] Opening server socket on port [1024].
[royaleunit] Waiting for client connection ...
[royaleunit] Client connected.
[royaleunit] Setting inbound buffer size to [262144] bytes.
[royaleunit] Receiving data ...
[royaleunit] Sending acknowledgement to player to start sending test data ...
[royaleunit] 
[royaleunit] 
[royaleunit] Stopping server ...
[royaleunit] End of test data reached, sending acknowledgement to player ...
[royaleunit] Closing client connection ...
[royaleunit] Closing server on port [1024] ...
[royaleunit] Analyzing reports ...
[royaleunit] 
[royaleunit] Suite: flexUnitTests.DataGridColumnTest
[royaleunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.123 sec
[royaleunit] 
[royaleunit] Results :
[royaleunit] 
[royaleunit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.123 sec
[royaleunit] 
[junitreport] Processing 

 to C:\Users\ApacheRoyaleCI\AppData\Local\Temp\null1263496928
[junitreport] Loading stylesheet 
jar:file:/C:/apache/apache-ant-1.9.9/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames.xsl
[junitreport] Transform time: 1169ms
[junitreport] Deleting: 
C:\Users\ApacheRoyaleCI\AppData\Local\Temp\null1263496928

main:
 [echo] swc-date is 04/20/20 01:58 +

test-js:
 [echo] swc-date is 04/20/20 01:59 +
   [delete] Deleting: 


check-for-tests:

check-compiler-home:

check-transpiler-home:

check-compiler:

test:

clean:

compile:
 [echo] Cross-compiling tests
 [echo] ROYALE_HOME: 

 [echo] ROYALE_SWF_COMPILER_HOME: 

 [echo] playerglobal.version: 11.7
Trying to override old definition of task compc
Trying to override old definition of task mxmlc
[mxmlc] MXMLJSC
[mxmlc] -compiler.targets=JSRoyale
[mxmlc] -js-output=target
[mxmlc] +playerglobal.version=11.7
[mxmlc] +env.PLAYERGLOBAL_HOME=C:\adobe\flash
[mxmlc] 
+royalelib=
   

Build failed in Jenkins: royale-compiler #357

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd\git.exe init 
 > 
 >  # timeout=10
Fetching upstream changes from https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-compiler +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-compiler # timeout=10
 > C:\Program Files\Git\cmd\git.exe config --add remote.origin.fetch 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-compiler # timeout=10
Fetching upstream changes from https://github.com/apache/royale-compiler
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-compiler +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 86bbb1e4d69569dc538a3e25041305a9c673a1e8 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 86bbb1e4d69569dc538a3e25041305a9c673a1e8
Commit message: "release-notes: added improvements to Maven by chris dutz and 
enhancements to create maven distribution that now is working"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 86bbb1e4d69569dc538a3e25041305a9c673a1e8 # timeout=10
[royale-compiler] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat -file 
jenkins.xml -Denv.ASJS_HOME=C:\jenkins\workspace\royale-asjs main && exit 
%%ERRORLEVEL%%"
Unable to locate tools.jar. Expected to find it in C:\Program Files 
(x86)\Java\jre1.8.0_251\lib\tools.jar
Buildfile: 


clean:

init:
[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: 

[mkdir] Created dir: C:\Google\Closure\Library

jflex-download:
 [echo] Be patient. This takes a few minutes...
  [get] Getting: https://jflex.de/jflex-1.4.3.zip
  [get] To: 

[unzip] Expanding: 

 into 


closure-lib-download:
 [echo] Be patient. This takes a few minutes...

BUILD FAILED
:55:
 Execute failed: java.io.IOException: Cannot run program "git" (in directory 
":
 CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at 
org.apache.tools.ant.taskdefs.launcher.Java13CommandLauncher.exec(Java13CommandLauncher.java:58)
at org.apache.tools.ant.taskdefs.Execute.launch(Execute.java:426)
at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:440)
at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:629)
at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:670)
at org.apache.tools.ant.taskdefs.ExecTask.execute(ExecTask.java:496)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Targe

Build failed in Jenkins: royale-asjs_jsonly #1327

[apacheroyaleci]

See 


Changes:


--
[...truncated 120.09 KB...]
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


check-for-tests:

clean-tests:

clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


check-for-tests:

clean-tests:

clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


check-for-tests:

clean-tests:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


clean:
 [echo] swc-date is 04/20/20 01:38 +
   [delete] Deleting: 


check-for-tests:

clean-tests:

package-clean:

clean-temp:

checkintests-clean:

mxtests-clean:

clean:

Build failed in Jenkins: royale-asjs_jsonly #1326

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1325

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
FATAL: java.nio.channels.ClosedChannelException
java.nio.channels.ClosedChannelException
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
JNLP4-connect connection from 52.251.60.60/52.251.60.60:55667
at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
at hudson.remoting.Request.call(Request.java:202)
at hudson.remoting.Channel.call(Channel.java:956)
at hudson.FilePath.act(FilePath.java:1162)
at 
org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvVarsForNode(EnvironmentVariablesNodeLoader.java:61)
at 
org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:78)
at 
org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:42)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462)
at hudson.model.Run.execute(Run.java:1815)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at 
hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Caused: hudson.remoting.RequestAbortedException
at hudson.remoting.Request.abort(Request.java:340)
at hudson.remoting.Channel.terminate(Channel.java:1040)
at 
org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:209)
at 
org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222)
at 
org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816)
at 
org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)
at 
org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172)
at 
org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816)
at 
org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at 
org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)
at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at 
jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
ERROR: Step ‘Archive the artifacts’ failed: no workspace for royale-asjs_jsonly 
#1325
ERROR: agent2 is offline; cannot locate Java 8 (201)

Build failed in Jenkins: royale-asjs_jsonly #1324

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1321

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1323

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1322

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1320

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1319

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1318

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1317

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1316

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1312

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
'ant.bat' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1315

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\apache\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1314

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "C:\opt\apache-ant-1.9.9\bin\ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
Error occurred during initialization of VM
Could not reserve enough space for 2097152KB object heap
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx2g
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1313

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
'ant.bat' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Repository for tutorials

[Andrew Wetmore]

Hi:

Hi: I see that flink.apache.org has requested a separate git repository for
the self-directed learning modules they hope to deploy. As we move closer
to Royale 1.0 it will become more important to have a suite of tutorials to
extends the excellent how-tos @carlos has been posting on the blog..

I have committed to creating Royale in a Week, which will have lots of
stuff to store: scripts, videos, code samples, transcripts, and so on. Can
we fit that all into the existing documentation repository? Or should we
request a separate one?

A

-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Build failed in Jenkins: royale-asjs_jsonly #1311

[apacheroyaleci]

See 


Changes:

[carlosrovira] markdown-example: fix highlightAuto


--
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > f6f09ace9b98a3a86b5f2865fe6fd80586b4b72e
Commit message: "markdown-example: fix highlightAuto"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 93992d9a7158e0bc33a917526863a659f743eeb6 # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
'ant.bat' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1310

[apacheroyaleci]

See 


Changes:

[carlosrovira] markdown-example: make links have target and rel attributes. Add 
some


--
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 93992d9a7158e0bc33a917526863a659f743eeb6 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 93992d9a7158e0bc33a917526863a659f743eeb6
Commit message: "markdown-example: make links have target and rel attributes. 
Add some buttons that loads different files"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
'ant.bat' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Yishay Weiss]

Turns out my public key needed to be distributed to a keyserver.

gpg --keyserver http://keyserver.ubuntu.com --send-keys 

did the trick. You should see it now.




From: Yishay Weiss 
Sent: Sunday, April 19, 2020 5:22:56 PM
To: dev@royale.apache.org 
Subject: RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

Thanks for spotting that. It looks like it failed signature validation on 
releasing the folder, even though it had passed it when closing the folder. 
I’ll see if I can figure this out…

From: Carlos Rovira
Sent: Sunday, April 19, 2020 5:12 PM
To: Apache Royale Development
Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

I think 1.2.0 must be pushed to maven central

https://search.maven.org/artifact/org.apache.royale.compiler/compiler-build-tools

El dom., 19 abr. 2020 a las 16:10, Carlos Rovira ()
escribió:

> Ok Yishay,
>
> and is this version used in current 0.9.7 ongoing release process?
>
> thanks
>
>
>
> El dom., 19 abr. 2020 a las 15:37, Yishay Weiss ()
> escribió:
>
>> Hi Carlos,
>>
>> It’s already been released, just haven’t announced it yet.
>>
>> From: Carlos Rovira
>> Sent: Sunday, April 19, 2020 4:12 PM
>> To: Apache Royale Development
>> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
>>
>> Hi
>>
>> can we consider this vote finished?
>>
>> also, I think current main release is not using this 1.2.0 right? so the
>> fixes will be not applied
>>
>> Maybe I'm wrong
>>
>> Thanks
>>
>>
>>
>> El mié., 15 abr. 2020 a las 23:05, Harbs ()
>> escribió:
>>
>> > I’m not going to have the time to look at this before the 72 hours are
>> > over, so here’s my official +0 vote… ;-)
>> >
>> > Harbs
>> >
>> > > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
>> > >
>> > > Hi,
>> > > This is the vote for the 1.2.0 release of Apache Royale Compiler Build
>> > Tools.  The release candidate can be found here;
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/
>> > >
>> > > Before voting please review the section,'What are the ASF requirements
>> > on approving a release?', at:
>> > > http://www.apache.org/dev/release.html#approving-a-release
>> > >
>> > > At a minimum you would be expected to check that:
>> > > - SHA and signed packages are correct
>> > > - NOTICE and LICENSE files are all fine
>> > > - That "mvn clean install" in the root of the source package completes
>> > successfully
>> > > - That you can modify other compiler poms to use that version of
>> > compiler-build-tools and build the compiler.
>> > >
>> > > The KEYS file is at
>> > https://dist.apache.org/repos/dist/release/royale/KEYS
>> > >
>> > > Maven artifacts are staged here:
>> > >
>> https://repository.apache.org/content/repositories/orgapacheroyale-1064
>> > >
>> > > Please vote to approve this release:
>> > > +1 Approve the release
>> > > -1 Disapprove the release (please provide specific comments to why)
>> > >
>> > > This vote will be open for 72 hours or until a result can be called.
>> > >
>> > > The vote passes if there is:
>> > > - At least 3 +1 votes from the PMC
>> > > - More positive votes than negative votes
>> > >
>> > > Remember that this is a 'beta-quality' release so expect there will be
>> > many bugs found. IMO the goal is not to try to find and fix bugs in the
>> RC,
>> > but to make sure we have the packaging right, and enough functionality
>> that
>> > folks will have some success trying to use it.  People who are not in
>> PMC
>> > are also encouraged to test out the release and vote, although their
>> votes
>> > will not be binding, they can influence how the PMC votes.
>> > >
>> > > When voting please indicate what OS, IDE, Flash Player version and AIR
>> > version you tested with.
>> > >
>> > > For your convenience, there is an ant script that automates the common
>> > steps to validate a release.  Instead of individually downloading the
>> > package and signature files, unzipping, etc, you can instead:
>> > > 1) create an empty folder,
>> > > 2) download into that folder this file:
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/ApproveBuildTools.xml
>> > > 3) run the script:
>> > >   ant -e -f ApproveBuildTools.xml -Drelease.version=1.2.0 -Drc=3
>> > >
>> > > You are not required to use this script, and more testing of the
>> > packages and build results are always encouraged.
>> > >
>> > > Please put all discussion about this release in the DISCUSSION thread
>> > not this VOTE thread.
>> > >
>> > > Thanks,
>> > > Yishay Weiss
>> >
>> >
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

--
Carlos Rovira
http://about.me/carlosrovira
From: Yishay Weiss
Sent: Sunday, April 19, 2020 5:23 PM
To: dev@royale.apache.org

Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Alex Harui]

Once the build tools is successfully deployed to Maven Central, then in the 
royale-compiler release/0.9.7 branch, the main pom.xml needs to be modified to 
use 1.2.0 version of build-tools.

On 4/19/20, 7:50 AM, "Yishay Weiss"  wrote:

I’m not sure I understand the question. As I understand it, the compiler 
will be built using the latest sources under compiler-build-tools. There are no 
recent code changes there as far as I can tell. I may be missing something.

From: Carlos Rovira
Sent: Sunday, April 19, 2020 5:10 PM
To: Apache Royale Development
Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

Ok Yishay,

and is this version used in current 0.9.7 ongoing release process?

thanks



El dom., 19 abr. 2020 a las 15:37, Yishay Weiss ()
escribió:

> Hi Carlos,
>
> It’s already been released, just haven’t announced it yet.
>
> From: Carlos Rovira
> Sent: Sunday, April 19, 2020 4:12 PM
> To: Apache Royale Development
> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
>
> Hi
>
> can we consider this vote finished?
>
> also, I think current main release is not using this 1.2.0 right? so the
> fixes will be not applied
>
> Maybe I'm wrong
>
> Thanks
>
>
>
> El mié., 15 abr. 2020 a las 23:05, Harbs ()
> escribió:
>
> > I’m not going to have the time to look at this before the 72 hours are
> > over, so here’s my official +0 vote… ;-)
> >
> > Harbs
> >
> > > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
> > >
> > > Hi,
> > > This is the vote for the 1.2.0 release of Apache Royale Compiler Build
> > Tools.  The release candidate can be found here;
> > >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Froyale%2Fcompiler-build-tools%2F1.2.0%2Frc3%2F&data=02%7C01%7Caharui%40adobe.com%7C503d4ea9322f40ea93e608d7e470f763%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229046151047604&sdata=w8lhK2Pjthl0iXa%2FuQUXkfz95PM9BIs2t7wP4sDahcg%3D&reserved=0
> > >
> > > Before voting please review the section,'What are the ASF requirements
> > on approving a release?', at:
> > > 
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apache.org%2Fdev%2Frelease.html%23approving-a-release&data=02%7C01%7Caharui%40adobe.com%7C503d4ea9322f40ea93e608d7e470f763%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229046151057597&sdata=Uew%2BUT1HvaXMFXCYcJL9H2jbIAAIraG0ydVbZ2TE92Q%3D&reserved=0
> > >
> > > At a minimum you would be expected to check that:
> > > - SHA and signed packages are correct
> > > - NOTICE and LICENSE files are all fine
> > > - That "mvn clean install" in the root of the source package completes
> > successfully
> > > - That you can modify other compiler poms to use that version of
> > compiler-build-tools and build the compiler.
> > >
> > > The KEYS file is at
> > 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Frelease%2Froyale%2FKEYS&data=02%7C01%7Caharui%40adobe.com%7C503d4ea9322f40ea93e608d7e470f763%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229046151057597&sdata=wabwAgbmweHTbpfsYefeS0Pi38JScqsbL1oZF5gop4I%3D&reserved=0
> > >
> > > Maven artifacts are staged here:
> > >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapacheroyale-1064&data=02%7C01%7Caharui%40adobe.com%7C503d4ea9322f40ea93e608d7e470f763%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637229046151057597&sdata=LJMIfPqQb53rR3LdPbDLcUmz5yVViqVihzpaJ7SivCM%3D&reserved=0
> > >
> > > Please vote to approve this release:
> > > +1 Approve the release
> > > -1 Disapprove the release (please provide specific comments to why)
> > >
> > > This vote will be open for 72 hours or until a result can be called.
> > >
> > > The vote passes if there is:
> > > - At least 3 +1 votes from the PMC
> > > - More positive votes than negative votes
> > >
> > > Remember that this is a 'beta-quality' release so expect there will be
> > many bugs found. IMO the goal is not to try to find and fix bugs in the
> RC,
> > but to make sure we have the packaging right, and enough functionality
> that
> > folks will have some success trying to use it.  People who are not in 
PMC
> > are also encouraged to test out the release and vote, although their
> votes
> > will not be binding, they can influence how the PMC votes.
> > >
> > > When voting please indicate what OS, IDE, Flash Player version and AIR
> > version you tested wi

RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Yishay Weiss]

I’m not sure I understand the question. As I understand it, the compiler will 
be built using the latest sources under compiler-build-tools. There are no 
recent code changes there as far as I can tell. I may be missing something.

From: Carlos Rovira
Sent: Sunday, April 19, 2020 5:10 PM
To: Apache Royale Development
Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

Ok Yishay,

and is this version used in current 0.9.7 ongoing release process?

thanks



El dom., 19 abr. 2020 a las 15:37, Yishay Weiss ()
escribió:

> Hi Carlos,
>
> It’s already been released, just haven’t announced it yet.
>
> From: Carlos Rovira
> Sent: Sunday, April 19, 2020 4:12 PM
> To: Apache Royale Development
> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
>
> Hi
>
> can we consider this vote finished?
>
> also, I think current main release is not using this 1.2.0 right? so the
> fixes will be not applied
>
> Maybe I'm wrong
>
> Thanks
>
>
>
> El mié., 15 abr. 2020 a las 23:05, Harbs ()
> escribió:
>
> > I’m not going to have the time to look at this before the 72 hours are
> > over, so here’s my official +0 vote… ;-)
> >
> > Harbs
> >
> > > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
> > >
> > > Hi,
> > > This is the vote for the 1.2.0 release of Apache Royale Compiler Build
> > Tools.  The release candidate can be found here;
> > >
> >
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/
> > >
> > > Before voting please review the section,'What are the ASF requirements
> > on approving a release?', at:
> > > http://www.apache.org/dev/release.html#approving-a-release
> > >
> > > At a minimum you would be expected to check that:
> > > - SHA and signed packages are correct
> > > - NOTICE and LICENSE files are all fine
> > > - That "mvn clean install" in the root of the source package completes
> > successfully
> > > - That you can modify other compiler poms to use that version of
> > compiler-build-tools and build the compiler.
> > >
> > > The KEYS file is at
> > https://dist.apache.org/repos/dist/release/royale/KEYS
> > >
> > > Maven artifacts are staged here:
> > >
> https://repository.apache.org/content/repositories/orgapacheroyale-1064
> > >
> > > Please vote to approve this release:
> > > +1 Approve the release
> > > -1 Disapprove the release (please provide specific comments to why)
> > >
> > > This vote will be open for 72 hours or until a result can be called.
> > >
> > > The vote passes if there is:
> > > - At least 3 +1 votes from the PMC
> > > - More positive votes than negative votes
> > >
> > > Remember that this is a 'beta-quality' release so expect there will be
> > many bugs found. IMO the goal is not to try to find and fix bugs in the
> RC,
> > but to make sure we have the packaging right, and enough functionality
> that
> > folks will have some success trying to use it.  People who are not in PMC
> > are also encouraged to test out the release and vote, although their
> votes
> > will not be binding, they can influence how the PMC votes.
> > >
> > > When voting please indicate what OS, IDE, Flash Player version and AIR
> > version you tested with.
> > >
> > > For your convenience, there is an ant script that automates the common
> > steps to validate a release.  Instead of individually downloading the
> > package and signature files, unzipping, etc, you can instead:
> > > 1) create an empty folder,
> > > 2) download into that folder this file:
> > >
> >
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/ApproveBuildTools.xml
> > > 3) run the script:
> > >   ant -e -f ApproveBuildTools.xml -Drelease.version=1.2.0 -Drc=3
> > >
> > > You are not required to use this script, and more testing of the
> > packages and build results are always encouraged.
> > >
> > > Please put all discussion about this release in the DISCUSSION thread
> > not this VOTE thread.
> > >
> > > Thanks,
> > > Yishay Weiss
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

--
Carlos Rovira
http://about.me/carlosrovira

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Harbs,

Agreed with that. We can rename them, but even in case of HashRouter - does
exclude it ability to have parameters ? Does those parameters not exists in
HasRouter as well. Is it not a common stuff no matter what kind of url it
is ?

niedz., 19 kwi 2020 o 15:52 Harbs  napisał(a):

> After thinking about this some more, I’m thinking that Router should be
> named and we should add another type of router for standard path routing.
>
> React calls them HashRouter and BrowserRouter. Maybe we should use the
> same names…
>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter <
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter>
>
> > On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki 
> wrote:
> >
> > Hi Harbs,
> >
> > It sounds like you are asking me to check in onInit whether
> > if(location.hash) exists then do something, but if doesn't exists check
> url
> > params. - I may understand it in a wrong way, but I think location.hash
> may
> > exists and location.search - where parameters are stored could exists
> > equally.
> >
> > if(location.hash)
> > {
> >  hashChangeHandler();
> > }
> >
> > if (location.search)
> > {
> >   parseParameters();
> > }
> >
> > Am I missing something ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> >
> >> Whatever you think is fine by me.
> >>
> >> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get
> >> rid of that conditional.
> >>
> >> It could be you can get rid of that and handle hashRecieved in a bead.
> If
> >> the hashReceived event has no hash you can then check the URL.You do
> need
> >> to make sure that you always get a stateChange event and don’t dispatch
> it
> >> twice.
> >>
> >> Feel free to play around with the code… ;-)
> >>
> >> Harbs
> >>
> >>> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >>>
> >>> I think it would be better to have it here in Router.
> >>>
> >>> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >>>
>  Alternatively, you can subclass Router to support setting the
> parameters
>  in the onInit method.
> 
>  Not sure which of these is best.
> 
> > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >
> > Actually, it’s not going to work because the
>  router.routeState.parameters will not be set.
> >
> > You will likely need to add code to set the
> >> router.routeState.parameters
>  using the part of the location after the question mark.
> >
> > The easiest way to do that would be to either:
> > 1. Modify RouteToParameters.stateChanged to first check that there
> is a
>  parameters value and then set it if not.
> > 2. Subclass RouteToParameters and override stateChanged to make that
>  check first.
> >
> >> On Apr 17, 2020, at 10:29 AM, Harbs   harbs.li...@gmail.com>> wrote:
> >>
> >> I’m pretty sure it’ll work without the hash as well.
> >>
> >> Give it a try.
> >>
> >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>  piotrzarzyck...@gmail.com > wrote:
> >>>
> >>> Hi Harbs,
> >>>
> >>> Thanks for pointing me out, but this is still that Routing expects
> me
>  to
> >>> use in url hashes - The question is - What if I can't use hashes,
> but
>  url
> >>> looks like I have presented in previous email ?
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> pt., 17 kwi 2020 o 09:20 Harbs   harbs.li...@gmail.com>> napisał(a):
> >>>
>  This app uses both path based and query based routing:
> 
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> 
>  You can see how it’s done here:
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>  <
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
>  <
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>  <
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
> >
> 
> > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
>  piotrzarzyck...@gmail.com >
>  wrote:
> >
> > I'm still looking into the code and it looks like Routing
>  implemented now
> > is not doing what I would expected. Everything is based on "hash"
>  property
> > in "location". Instead I need something which is in "search" of

RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Yishay Weiss]

Thanks for spotting that. It looks like it failed signature validation on 
releasing the folder, even though it had passed it when closing the folder. 
I’ll see if I can figure this out…

From: Carlos Rovira
Sent: Sunday, April 19, 2020 5:12 PM
To: Apache Royale Development
Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

I think 1.2.0 must be pushed to maven central

https://search.maven.org/artifact/org.apache.royale.compiler/compiler-build-tools

El dom., 19 abr. 2020 a las 16:10, Carlos Rovira ()
escribió:

> Ok Yishay,
>
> and is this version used in current 0.9.7 ongoing release process?
>
> thanks
>
>
>
> El dom., 19 abr. 2020 a las 15:37, Yishay Weiss ()
> escribió:
>
>> Hi Carlos,
>>
>> It’s already been released, just haven’t announced it yet.
>>
>> From: Carlos Rovira
>> Sent: Sunday, April 19, 2020 4:12 PM
>> To: Apache Royale Development
>> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
>>
>> Hi
>>
>> can we consider this vote finished?
>>
>> also, I think current main release is not using this 1.2.0 right? so the
>> fixes will be not applied
>>
>> Maybe I'm wrong
>>
>> Thanks
>>
>>
>>
>> El mié., 15 abr. 2020 a las 23:05, Harbs ()
>> escribió:
>>
>> > I’m not going to have the time to look at this before the 72 hours are
>> > over, so here’s my official +0 vote… ;-)
>> >
>> > Harbs
>> >
>> > > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
>> > >
>> > > Hi,
>> > > This is the vote for the 1.2.0 release of Apache Royale Compiler Build
>> > Tools.  The release candidate can be found here;
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/
>> > >
>> > > Before voting please review the section,'What are the ASF requirements
>> > on approving a release?', at:
>> > > http://www.apache.org/dev/release.html#approving-a-release
>> > >
>> > > At a minimum you would be expected to check that:
>> > > - SHA and signed packages are correct
>> > > - NOTICE and LICENSE files are all fine
>> > > - That "mvn clean install" in the root of the source package completes
>> > successfully
>> > > - That you can modify other compiler poms to use that version of
>> > compiler-build-tools and build the compiler.
>> > >
>> > > The KEYS file is at
>> > https://dist.apache.org/repos/dist/release/royale/KEYS
>> > >
>> > > Maven artifacts are staged here:
>> > >
>> https://repository.apache.org/content/repositories/orgapacheroyale-1064
>> > >
>> > > Please vote to approve this release:
>> > > +1 Approve the release
>> > > -1 Disapprove the release (please provide specific comments to why)
>> > >
>> > > This vote will be open for 72 hours or until a result can be called.
>> > >
>> > > The vote passes if there is:
>> > > - At least 3 +1 votes from the PMC
>> > > - More positive votes than negative votes
>> > >
>> > > Remember that this is a 'beta-quality' release so expect there will be
>> > many bugs found. IMO the goal is not to try to find and fix bugs in the
>> RC,
>> > but to make sure we have the packaging right, and enough functionality
>> that
>> > folks will have some success trying to use it.  People who are not in
>> PMC
>> > are also encouraged to test out the release and vote, although their
>> votes
>> > will not be binding, they can influence how the PMC votes.
>> > >
>> > > When voting please indicate what OS, IDE, Flash Player version and AIR
>> > version you tested with.
>> > >
>> > > For your convenience, there is an ant script that automates the common
>> > steps to validate a release.  Instead of individually downloading the
>> > package and signature files, unzipping, etc, you can instead:
>> > > 1) create an empty folder,
>> > > 2) download into that folder this file:
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/ApproveBuildTools.xml
>> > > 3) run the script:
>> > >   ant -e -f ApproveBuildTools.xml -Drelease.version=1.2.0 -Drc=3
>> > >
>> > > You are not required to use this script, and more testing of the
>> > packages and build results are always encouraged.
>> > >
>> > > Please put all discussion about this release in the DISCUSSION thread
>> > not this VOTE thread.
>> > >
>> > > Thanks,
>> > > Yishay Weiss
>> >
>> >
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

--
Carlos Rovira
http://about.me/carlosrovira

Re: Routing (was Re: Spectrum Components)

[Harbs]

It’s also interesting to see how Vue handles routing:
https://github.com/vuejs/vue-router/tree/dev/examples 


> On Apr 19, 2020, at 4:27 PM, Harbs  wrote:
> 
> After thinking about this some more, I’m thinking that Router should be named 
> and we should add another type of router for standard path routing.
> 
> React calls them HashRouter and BrowserRouter. Maybe we should use the same 
> names…
> 
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter 
> 
> 
>> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki > > wrote:
>> 
>> Hi Harbs,
>> 
>> It sounds like you are asking me to check in onInit whether
>> if(location.hash) exists then do something, but if doesn't exists check url
>> params. - I may understand it in a wrong way, but I think location.hash may
>> exists and location.search - where parameters are stored could exists
>> equally.
>> 
>> if(location.hash)
>> {
>>  hashChangeHandler();
>> }
>> 
>> if (location.search)
>> {
>>   parseParameters();
>> }
>> 
>> Am I missing something ?
>> 
>> Thanks,
>> Piotr
>> 
>> pt., 17 kwi 2020 o 12:09 Harbs > > napisał(a):
>> 
>>> Whatever you think is fine by me.
>>> 
>>> I don’t remember why I have "if(location.hash)”. It’s possible you can get
>>> rid of that conditional.
>>> 
>>> It could be you can get rid of that and handle hashRecieved in a bead. If
>>> the hashReceived event has no hash you can then check the URL.You do need
>>> to make sure that you always get a stateChange event and don’t dispatch it
>>> twice.
>>> 
>>> Feel free to play around with the code… ;-)
>>> 
>>> Harbs
>>> 
 On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki >>> >
>>> wrote:
 
 I think it would be better to have it here in Router.
 
 pt., 17 kwi 2020 o 09:37 Harbs >>> > napisał(a):
 
> Alternatively, you can subclass Router to support setting the parameters
> in the onInit method.
> 
> Not sure which of these is best.
> 
>> On Apr 17, 2020, at 10:35 AM, Harbs > > wrote:
>> 
>> Actually, it’s not going to work because the
> router.routeState.parameters will not be set.
>> 
>> You will likely need to add code to set the
>>> router.routeState.parameters
> using the part of the location after the question mark.
>> 
>> The easiest way to do that would be to either:
>> 1. Modify RouteToParameters.stateChanged to first check that there is a
> parameters value and then set it if not.
>> 2. Subclass RouteToParameters and override stateChanged to make that
> check first.
>> 
>>> On Apr 17, 2020, at 10:29 AM, Harbs >>   harbs.li...@gmail.com >> wrote:
>>> 
>>> I’m pretty sure it’ll work without the hash as well.
>>> 
>>> Give it a try.
>>> 
 On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com  
> >> 
> wrote:
 
 Hi Harbs,
 
 Thanks for pointing me out, but this is still that Routing expects me
> to
 use in url hashes - The question is - What if I can't use hashes, but
> url
 looks like I have presented in previous email ?
 
 Thanks,
 Piotr
 
 pt., 17 kwi 2020 o 09:20 Harbs >>>   harbs.li...@gmail.com >> napisał(a):
 
> This app uses both path based and query based routing:
> 
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
>  <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
> > <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
>  <
> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark 
> >>
> 
> You can see how it’s done here:
> 
> 
>>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>>>  
>>> 
> <
> 
>>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>> 
> <
> 
> 
>>> https://github.com/unhurdle/spectrum-royale/blob/master/Spe

Build failed in Jenkins: royale-asjs_jsonly #1309

[apacheroyaleci]

See 


Changes:


--
Started by upstream project "royale-typedefs" build number 549
originally caused by:
 Started by upstream project "royale-compiler" build number 356
 originally caused by:
  Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 48597d9f2cb779a8014932583c8b8aff1233d87f 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f
Commit message: "markdown-example: highlight as3 and mxml"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
'ant.bat' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Carlos Rovira]

I think 1.2.0 must be pushed to maven central

https://search.maven.org/artifact/org.apache.royale.compiler/compiler-build-tools

El dom., 19 abr. 2020 a las 16:10, Carlos Rovira ()
escribió:

> Ok Yishay,
>
> and is this version used in current 0.9.7 ongoing release process?
>
> thanks
>
>
>
> El dom., 19 abr. 2020 a las 15:37, Yishay Weiss ()
> escribió:
>
>> Hi Carlos,
>>
>> It’s already been released, just haven’t announced it yet.
>>
>> From: Carlos Rovira
>> Sent: Sunday, April 19, 2020 4:12 PM
>> To: Apache Royale Development
>> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
>>
>> Hi
>>
>> can we consider this vote finished?
>>
>> also, I think current main release is not using this 1.2.0 right? so the
>> fixes will be not applied
>>
>> Maybe I'm wrong
>>
>> Thanks
>>
>>
>>
>> El mié., 15 abr. 2020 a las 23:05, Harbs ()
>> escribió:
>>
>> > I’m not going to have the time to look at this before the 72 hours are
>> > over, so here’s my official +0 vote… ;-)
>> >
>> > Harbs
>> >
>> > > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
>> > >
>> > > Hi,
>> > > This is the vote for the 1.2.0 release of Apache Royale Compiler Build
>> > Tools.  The release candidate can be found here;
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/
>> > >
>> > > Before voting please review the section,'What are the ASF requirements
>> > on approving a release?', at:
>> > > http://www.apache.org/dev/release.html#approving-a-release
>> > >
>> > > At a minimum you would be expected to check that:
>> > > - SHA and signed packages are correct
>> > > - NOTICE and LICENSE files are all fine
>> > > - That "mvn clean install" in the root of the source package completes
>> > successfully
>> > > - That you can modify other compiler poms to use that version of
>> > compiler-build-tools and build the compiler.
>> > >
>> > > The KEYS file is at
>> > https://dist.apache.org/repos/dist/release/royale/KEYS
>> > >
>> > > Maven artifacts are staged here:
>> > >
>> https://repository.apache.org/content/repositories/orgapacheroyale-1064
>> > >
>> > > Please vote to approve this release:
>> > > +1 Approve the release
>> > > -1 Disapprove the release (please provide specific comments to why)
>> > >
>> > > This vote will be open for 72 hours or until a result can be called.
>> > >
>> > > The vote passes if there is:
>> > > - At least 3 +1 votes from the PMC
>> > > - More positive votes than negative votes
>> > >
>> > > Remember that this is a 'beta-quality' release so expect there will be
>> > many bugs found. IMO the goal is not to try to find and fix bugs in the
>> RC,
>> > but to make sure we have the packaging right, and enough functionality
>> that
>> > folks will have some success trying to use it.  People who are not in
>> PMC
>> > are also encouraged to test out the release and vote, although their
>> votes
>> > will not be binding, they can influence how the PMC votes.
>> > >
>> > > When voting please indicate what OS, IDE, Flash Player version and AIR
>> > version you tested with.
>> > >
>> > > For your convenience, there is an ant script that automates the common
>> > steps to validate a release.  Instead of individually downloading the
>> > package and signature files, unzipping, etc, you can instead:
>> > > 1) create an empty folder,
>> > > 2) download into that folder this file:
>> > >
>> >
>> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/ApproveBuildTools.xml
>> > > 3) run the script:
>> > >   ant -e -f ApproveBuildTools.xml -Drelease.version=1.2.0 -Drc=3
>> > >
>> > > You are not required to use this script, and more testing of the
>> > packages and build results are always encouraged.
>> > >
>> > > Please put all discussion about this release in the DISCUSSION thread
>> > not this VOTE thread.
>> > >
>> > > Thanks,
>> > > Yishay Weiss
>> >
>> >
>>
>> --
>> Carlos Rovira
>> http://about.me/carlosrovira
>>
>>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Carlos Rovira]

Ok Yishay,

and is this version used in current 0.9.7 ongoing release process?

thanks



El dom., 19 abr. 2020 a las 15:37, Yishay Weiss ()
escribió:

> Hi Carlos,
>
> It’s already been released, just haven’t announced it yet.
>
> From: Carlos Rovira
> Sent: Sunday, April 19, 2020 4:12 PM
> To: Apache Royale Development
> Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0
>
> Hi
>
> can we consider this vote finished?
>
> also, I think current main release is not using this 1.2.0 right? so the
> fixes will be not applied
>
> Maybe I'm wrong
>
> Thanks
>
>
>
> El mié., 15 abr. 2020 a las 23:05, Harbs ()
> escribió:
>
> > I’m not going to have the time to look at this before the 72 hours are
> > over, so here’s my official +0 vote… ;-)
> >
> > Harbs
> >
> > > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
> > >
> > > Hi,
> > > This is the vote for the 1.2.0 release of Apache Royale Compiler Build
> > Tools.  The release candidate can be found here;
> > >
> >
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/
> > >
> > > Before voting please review the section,'What are the ASF requirements
> > on approving a release?', at:
> > > http://www.apache.org/dev/release.html#approving-a-release
> > >
> > > At a minimum you would be expected to check that:
> > > - SHA and signed packages are correct
> > > - NOTICE and LICENSE files are all fine
> > > - That "mvn clean install" in the root of the source package completes
> > successfully
> > > - That you can modify other compiler poms to use that version of
> > compiler-build-tools and build the compiler.
> > >
> > > The KEYS file is at
> > https://dist.apache.org/repos/dist/release/royale/KEYS
> > >
> > > Maven artifacts are staged here:
> > >
> https://repository.apache.org/content/repositories/orgapacheroyale-1064
> > >
> > > Please vote to approve this release:
> > > +1 Approve the release
> > > -1 Disapprove the release (please provide specific comments to why)
> > >
> > > This vote will be open for 72 hours or until a result can be called.
> > >
> > > The vote passes if there is:
> > > - At least 3 +1 votes from the PMC
> > > - More positive votes than negative votes
> > >
> > > Remember that this is a 'beta-quality' release so expect there will be
> > many bugs found. IMO the goal is not to try to find and fix bugs in the
> RC,
> > but to make sure we have the packaging right, and enough functionality
> that
> > folks will have some success trying to use it.  People who are not in PMC
> > are also encouraged to test out the release and vote, although their
> votes
> > will not be binding, they can influence how the PMC votes.
> > >
> > > When voting please indicate what OS, IDE, Flash Player version and AIR
> > version you tested with.
> > >
> > > For your convenience, there is an ant script that automates the common
> > steps to validate a release.  Instead of individually downloading the
> > package and signature files, unzipping, etc, you can instead:
> > > 1) create an empty folder,
> > > 2) download into that folder this file:
> > >
> >
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/ApproveBuildTools.xml
> > > 3) run the script:
> > >   ant -e -f ApproveBuildTools.xml -Drelease.version=1.2.0 -Drc=3
> > >
> > > You are not required to use this script, and more testing of the
> > packages and build results are always encouraged.
> > >
> > > Please put all discussion about this release in the DISCUSSION thread
> > not this VOTE thread.
> > >
> > > Thanks,
> > > Yishay Weiss
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Routing (was Re: Spectrum Components)

[Carlos Rovira]

Hi Harbs

+1

that has more sense. Maybe actual Router should be renamed to HashRouter
and  create a new BrowserRouter.
Since you created the first Router and Piotr is interested in applying to
his work, would be possible for both to work on that?
As I said, I'm fighting with other MD things but would want to use that as
well for in a future royale website

Thanks



El dom., 19 abr. 2020 a las 15:52, Harbs () escribió:

> After thinking about this some more, I’m thinking that Router should be
> named and we should add another type of router for standard path routing.
>
> React calls them HashRouter and BrowserRouter. Maybe we should use the
> same names…
>
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter <
> https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter>
>
> > On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki 
> wrote:
> >
> > Hi Harbs,
> >
> > It sounds like you are asking me to check in onInit whether
> > if(location.hash) exists then do something, but if doesn't exists check
> url
> > params. - I may understand it in a wrong way, but I think location.hash
> may
> > exists and location.search - where parameters are stored could exists
> > equally.
> >
> > if(location.hash)
> > {
> >  hashChangeHandler();
> > }
> >
> > if (location.search)
> > {
> >   parseParameters();
> > }
> >
> > Am I missing something ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> >
> >> Whatever you think is fine by me.
> >>
> >> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get
> >> rid of that conditional.
> >>
> >> It could be you can get rid of that and handle hashRecieved in a bead.
> If
> >> the hashReceived event has no hash you can then check the URL.You do
> need
> >> to make sure that you always get a stateChange event and don’t dispatch
> it
> >> twice.
> >>
> >> Feel free to play around with the code… ;-)
> >>
> >> Harbs
> >>
> >>> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> >> wrote:
> >>>
> >>> I think it would be better to have it here in Router.
> >>>
> >>> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >>>
>  Alternatively, you can subclass Router to support setting the
> parameters
>  in the onInit method.
> 
>  Not sure which of these is best.
> 
> > On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >
> > Actually, it’s not going to work because the
>  router.routeState.parameters will not be set.
> >
> > You will likely need to add code to set the
> >> router.routeState.parameters
>  using the part of the location after the question mark.
> >
> > The easiest way to do that would be to either:
> > 1. Modify RouteToParameters.stateChanged to first check that there
> is a
>  parameters value and then set it if not.
> > 2. Subclass RouteToParameters and override stateChanged to make that
>  check first.
> >
> >> On Apr 17, 2020, at 10:29 AM, Harbs   harbs.li...@gmail.com>> wrote:
> >>
> >> I’m pretty sure it’ll work without the hash as well.
> >>
> >> Give it a try.
> >>
> >>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>  piotrzarzyck...@gmail.com > wrote:
> >>>
> >>> Hi Harbs,
> >>>
> >>> Thanks for pointing me out, but this is still that Routing expects
> me
>  to
> >>> use in url hashes - The question is - What if I can't use hashes,
> but
>  url
> >>> looks like I have presented in previous email ?
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> pt., 17 kwi 2020 o 09:20 Harbs   harbs.li...@gmail.com>> napisał(a):
> >>>
>  This app uses both path based and query based routing:
> 
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark
> <
>  https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> 
>  You can see how it’s done here:
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>  <
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
>  <
> 
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
>  <
> 
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >
> >
> 
> > On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
>  piotrzarzyck...@gmail.com >
>  wrote:
> >
> > I'm still looking into the code and it looks like Routing
>  implemented now
> > is not doing what I would

Re: Routing (was Re: Spectrum Components)

[Harbs]

After thinking about this some more, I’m thinking that Router should be named 
and we should add another type of router for standard path routing.

React calls them HashRouter and BrowserRouter. Maybe we should use the same 
names…

https://stackoverflow.com/questions/51974369/hashrouter-vs-browserrouter 


> On Apr 19, 2020, at 3:32 PM, Piotr Zarzycki  wrote:
> 
> Hi Harbs,
> 
> It sounds like you are asking me to check in onInit whether
> if(location.hash) exists then do something, but if doesn't exists check url
> params. - I may understand it in a wrong way, but I think location.hash may
> exists and location.search - where parameters are stored could exists
> equally.
> 
> if(location.hash)
> {
>  hashChangeHandler();
> }
> 
> if (location.search)
> {
>   parseParameters();
> }
> 
> Am I missing something ?
> 
> Thanks,
> Piotr
> 
> pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):
> 
>> Whatever you think is fine by me.
>> 
>> I don’t remember why I have "if(location.hash)”. It’s possible you can get
>> rid of that conditional.
>> 
>> It could be you can get rid of that and handle hashRecieved in a bead. If
>> the hashReceived event has no hash you can then check the URL.You do need
>> to make sure that you always get a stateChange event and don’t dispatch it
>> twice.
>> 
>> Feel free to play around with the code… ;-)
>> 
>> Harbs
>> 
>>> On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki 
>> wrote:
>>> 
>>> I think it would be better to have it here in Router.
>>> 
>>> pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
>>> 
 Alternatively, you can subclass Router to support setting the parameters
 in the onInit method.
 
 Not sure which of these is best.
 
> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> 
> Actually, it’s not going to work because the
 router.routeState.parameters will not be set.
> 
> You will likely need to add code to set the
>> router.routeState.parameters
 using the part of the location after the question mark.
> 
> The easiest way to do that would be to either:
> 1. Modify RouteToParameters.stateChanged to first check that there is a
 parameters value and then set it if not.
> 2. Subclass RouteToParameters and override stateChanged to make that
 check first.
> 
>> On Apr 17, 2020, at 10:29 AM, Harbs >>> harbs.li...@gmail.com>> wrote:
>> 
>> I’m pretty sure it’ll work without the hash as well.
>> 
>> Give it a try.
>> 
>>> On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
 piotrzarzyck...@gmail.com > wrote:
>>> 
>>> Hi Harbs,
>>> 
>>> Thanks for pointing me out, but this is still that Routing expects me
 to
>>> use in url hashes - The question is - What if I can't use hashes, but
 url
>>> looks like I have presented in previous email ?
>>> 
>>> Thanks,
>>> Piotr
>>> 
>>> pt., 17 kwi 2020 o 09:20 Harbs >>> harbs.li...@gmail.com>> napisał(a):
>>> 
 This app uses both path based and query based routing:
 
 https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
 https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
 https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
 https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
 
 You can see how it’s done here:
 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
 <
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> 
 <
 
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
 <
 
>> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> 
> 
 
> On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
 piotrzarzyck...@gmail.com >
 wrote:
> 
> I'm still looking into the code and it looks like Routing
 implemented now
> is not doing what I would expected. Everything is based on "hash"
 property
> in "location". Instead I need something which is in "search" of
 location. I
> will wait for your thoughts before I do try to handle stuff on my
 end.
> 
> pt., 17 kwi 2020 o 08:30 Piotr Zarzycki >>> >
> napisał(a):
> 
>> Hi Guys,
>> 
>> I really thought that I will be able to use Router [1] based on
>> documentation and maybe eventually some look to the code [2] - to
 figure
>> out how things should be implemented. However it looks like non of
 the
>> existing stuff helps me to use in in re

RE: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Yishay Weiss]

Hi Carlos,

It’s already been released, just haven’t announced it yet.

From: Carlos Rovira
Sent: Sunday, April 19, 2020 4:12 PM
To: Apache Royale Development
Subject: Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

Hi

can we consider this vote finished?

also, I think current main release is not using this 1.2.0 right? so the
fixes will be not applied

Maybe I'm wrong

Thanks



El mié., 15 abr. 2020 a las 23:05, Harbs () escribió:

> I’m not going to have the time to look at this before the 72 hours are
> over, so here’s my official +0 vote… ;-)
>
> Harbs
>
> > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
> >
> > Hi,
> > This is the vote for the 1.2.0 release of Apache Royale Compiler Build
> Tools.  The release candidate can be found here;
> >
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/
> >
> > Before voting please review the section,'What are the ASF requirements
> on approving a release?', at:
> > http://www.apache.org/dev/release.html#approving-a-release
> >
> > At a minimum you would be expected to check that:
> > - SHA and signed packages are correct
> > - NOTICE and LICENSE files are all fine
> > - That "mvn clean install" in the root of the source package completes
> successfully
> > - That you can modify other compiler poms to use that version of
> compiler-build-tools and build the compiler.
> >
> > The KEYS file is at
> https://dist.apache.org/repos/dist/release/royale/KEYS
> >
> > Maven artifacts are staged here:
> > https://repository.apache.org/content/repositories/orgapacheroyale-1064
> >
> > Please vote to approve this release:
> > +1 Approve the release
> > -1 Disapprove the release (please provide specific comments to why)
> >
> > This vote will be open for 72 hours or until a result can be called.
> >
> > The vote passes if there is:
> > - At least 3 +1 votes from the PMC
> > - More positive votes than negative votes
> >
> > Remember that this is a 'beta-quality' release so expect there will be
> many bugs found. IMO the goal is not to try to find and fix bugs in the RC,
> but to make sure we have the packaging right, and enough functionality that
> folks will have some success trying to use it.  People who are not in PMC
> are also encouraged to test out the release and vote, although their votes
> will not be binding, they can influence how the PMC votes.
> >
> > When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
> >
> > For your convenience, there is an ant script that automates the common
> steps to validate a release.  Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> > 1) create an empty folder,
> > 2) download into that folder this file:
> >
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/ApproveBuildTools.xml
> > 3) run the script:
> >   ant -e -f ApproveBuildTools.xml -Drelease.version=1.2.0 -Drc=3
> >
> > You are not required to use this script, and more testing of the
> packages and build results are always encouraged.
> >
> > Please put all discussion about this release in the DISCUSSION thread
> not this VOTE thread.
> >
> > Thanks,
> > Yishay Weiss
>
>

--
Carlos Rovira
http://about.me/carlosrovira

Re: 0.9.7 release notes updates - quick check

[Carlos Rovira]

Hi Greg

for compiler: just added improvements to maven by Chris Dutz and Maven
Distribution (that's now working) to create SDK with Maven
I think in compiler Josh should add many of his improvements

Going to check framework

thanks

Carlos



El dom., 19 abr. 2020 a las 2:02, Greg Dove ()
escribió:

> I pushed some changes to both compiler and asjs release notes in branch
> release/0.9.7
>
> I'd like to suggest that others review this and add more as needed (as
> opposed to waiting until late in the process to do it).
>
>
> On Sat, Apr 18, 2020 at 11:25 AM Greg Dove  wrote:
>
> > Ok, thanks for clarifying Alex. I will do that later today.
> >
> >
> > On Sat, Apr 18, 2020 at 11:03 AM Alex Harui 
> > wrote:
> >
> >> IMO, there is no perfect solution.  There will be times where the
> release
> >> branch is so broken that it will be tossed and re-cut from develop.  But
> >> this time around we are trying to keep the release branches around, so
> make
> >> changes to the release branch and make sure the RM knows so they RM
> knows
> >> to merge changes back in case we get to the toss-and-re-cut point.
> >>
> >> Thanks,
> >> -Alex
> >>
> >> On 4/17/20, 3:20 PM, "Greg Dove"  wrote:
> >>
> >> I am not sure whether the current work on 0.9.7 release is a dry run
> >> or a
> >> full effort (I have not been reading all details recently, sorry). I
> >> assume
> >> it is a full release effort.
> >>
> >> For 0.9.6 release we had a collective rush to add things to RELEASE
> >> NOTES
> >> before release.
> >>
> >> I have a few things I want to add to RELEASE NOTES. But I would also
> >> like
> >> to make sure I apply our collective learning from last time.
> >>
> >> The issue last time (iirc) was that we pushed updates into develop
> >> branch
> >> which I think then were being cherry picked into release branch.
> This
> >> I
> >> believe contributed to some merge conflicts at some point.
> >> Can I get a definitive answer for where I should add updates to
> >> RELEASE
> >> NOTES at this point if it is not too late? I think it is probably
> >> supposed
> >> to be directly into release branch which then gets merged later back
> >> into
> >> develop, but I'd like a confirmation of that if it is correct (and
> >> not too
> >> late), please.
> >>
> >>
> >>
>


-- 
Carlos Rovira
http://about.me/carlosrovira

Re: [VOTE] Release Apache Royale Compiler Build Tools 1.2.0

[Carlos Rovira]

Hi

can we consider this vote finished?

also, I think current main release is not using this 1.2.0 right? so the
fixes will be not applied

Maybe I'm wrong

Thanks



El mié., 15 abr. 2020 a las 23:05, Harbs () escribió:

> I’m not going to have the time to look at this before the 72 hours are
> over, so here’s my official +0 vote… ;-)
>
> Harbs
>
> > On Apr 13, 2020, at 11:25 PM, apacheroyal...@gmail.com wrote:
> >
> > Hi,
> > This is the vote for the 1.2.0 release of Apache Royale Compiler Build
> Tools.  The release candidate can be found here;
> >
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/
> >
> > Before voting please review the section,'What are the ASF requirements
> on approving a release?', at:
> > http://www.apache.org/dev/release.html#approving-a-release
> >
> > At a minimum you would be expected to check that:
> > - SHA and signed packages are correct
> > - NOTICE and LICENSE files are all fine
> > - That "mvn clean install" in the root of the source package completes
> successfully
> > - That you can modify other compiler poms to use that version of
> compiler-build-tools and build the compiler.
> >
> > The KEYS file is at
> https://dist.apache.org/repos/dist/release/royale/KEYS
> >
> > Maven artifacts are staged here:
> > https://repository.apache.org/content/repositories/orgapacheroyale-1064
> >
> > Please vote to approve this release:
> > +1 Approve the release
> > -1 Disapprove the release (please provide specific comments to why)
> >
> > This vote will be open for 72 hours or until a result can be called.
> >
> > The vote passes if there is:
> > - At least 3 +1 votes from the PMC
> > - More positive votes than negative votes
> >
> > Remember that this is a 'beta-quality' release so expect there will be
> many bugs found. IMO the goal is not to try to find and fix bugs in the RC,
> but to make sure we have the packaging right, and enough functionality that
> folks will have some success trying to use it.  People who are not in PMC
> are also encouraged to test out the release and vote, although their votes
> will not be binding, they can influence how the PMC votes.
> >
> > When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
> >
> > For your convenience, there is an ant script that automates the common
> steps to validate a release.  Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> > 1) create an empty folder,
> > 2) download into that folder this file:
> >
> https://dist.apache.org/repos/dist/dev/royale/compiler-build-tools/1.2.0/rc3/ApproveBuildTools.xml
> > 3) run the script:
> >   ant -e -f ApproveBuildTools.xml -Drelease.version=1.2.0 -Drc=3
> >
> > You are not required to use this script, and more testing of the
> packages and build results are always encouraged.
> >
> > Please put all discussion about this release in the DISCUSSION thread
> not this VOTE thread.
> >
> > Thanks,
> > Yishay Weiss
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Josh and Greg pointed into exactly the case which I have in our
application. Urls are controlled by server sight and I cannot change it, so
I rather need adjust how my application react towards different type of
urls which could be used, rather create specific for some views.

niedz., 19 kwi 2020 o 14:33 Piotr Zarzycki 
napisał(a):

> Hi Alex,
>
> Could you elaborate what do you mean exactly in that case saying PAYG?
> Parameter parsing should be done in different version of Router ?
>
> Thanks,
> Piotr
>
> pt., 17 kwi 2020 o 17:54 Alex Harui  napisał(a):
>
>> Ideally, supporting the route information in parameters vs hash would be
>> done in a PAYG way.
>>
>> AIUI, hash has to be used as the delimiter if you plan to change the
>> route information within the application, otherwise the application will
>> reload.  IOW, if the user is going to navigate in the appiication and the
>> route information is going to change as they navigate, hash should be
>> used.  If, on the other hand, there are a bunch of links on a website to
>> click and you end up on a "page", then URL parameters is probably ok.
>>
>> I don't understand the concern about the dev branch version.  The release
>> branch for 0.9.7 has been cut.  Any changes that go in develop are going in
>> the next release.  That's how the git branching model works.  You can make
>> any change you want in the dev branch right now.  It just won't be in the
>> 0.9.7 release unless the RM decides to cherry-pick it, which they should
>> not unless it is really important.  What am I missing?
>>
>> -Alex
>>
>> On 4/17/20, 3:09 AM, "Harbs"  wrote:
>>
>> Whatever you think is fine by me.
>>
>> I don’t remember why I have "if(location.hash)”. It’s possible you
>> can get rid of that conditional.
>>
>> It could be you can get rid of that and handle hashRecieved in a
>> bead. If the hashReceived event has no hash you can then check the URL.You
>> do need to make sure that you always get a stateChange event and don’t
>> dispatch it twice.
>>
>> Feel free to play around with the code… ;-)
>>
>> Harbs
>>
>> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
>> piotrzarzyck...@gmail.com> wrote:
>> >
>> > I think it would be better to have it here in Router.
>> >
>> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
>> >
>> >> Alternatively, you can subclass Router to support setting the
>> parameters
>> >> in the onInit method.
>> >>
>> >> Not sure which of these is best.
>> >>
>> >>> On Apr 17, 2020, at 10:35 AM, Harbs 
>> wrote:
>> >>>
>> >>> Actually, it’s not going to work because the
>> >> router.routeState.parameters will not be set.
>> >>>
>> >>> You will likely need to add code to set the
>> router.routeState.parameters
>> >> using the part of the location after the question mark.
>> >>>
>> >>> The easiest way to do that would be to either:
>> >>> 1. Modify RouteToParameters.stateChanged to first check that
>> there is a
>> >> parameters value and then set it if not.
>> >>> 2. Subclass RouteToParameters and override stateChanged to make
>> that
>> >> check first.
>> >>>
>>  On Apr 17, 2020, at 10:29 AM, Harbs > > >> harbs.li...@gmail.com>> wrote:
>> 
>>  I’m pretty sure it’ll work without the hash as well.
>> 
>>  Give it a try.
>> 
>> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
>> >> piotrzarzyck...@gmail.com >
>> wrote:
>> >
>> > Hi Harbs,
>> >
>> > Thanks for pointing me out, but this is still that Routing
>> expects me
>> >> to
>> > use in url hashes - The question is - What if I can't use
>> hashes, but
>> >> url
>> > looks like I have presented in previous email ?
>> >
>> > Thanks,
>> > Piotr
>> >
>> > pt., 17 kwi 2020 o 09:20 Harbs > >> harbs.li...@gmail.com>> napisał(a):
>> >
>> >> This app uses both path based and query based routing:
>> >>
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddark&data=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717&sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3D&reserved=0
>> <
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddark&data=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717&sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3D&reserved=0>
>> <
>> >>
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddark&data=02%7C01%7Caharui%40adobe.com%7C

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Hi Alex,

Could you elaborate what do you mean exactly in that case saying PAYG?
Parameter parsing should be done in different version of Router ?

Thanks,
Piotr

pt., 17 kwi 2020 o 17:54 Alex Harui  napisał(a):

> Ideally, supporting the route information in parameters vs hash would be
> done in a PAYG way.
>
> AIUI, hash has to be used as the delimiter if you plan to change the route
> information within the application, otherwise the application will reload.
> IOW, if the user is going to navigate in the appiication and the route
> information is going to change as they navigate, hash should be used.  If,
> on the other hand, there are a bunch of links on a website to click and you
> end up on a "page", then URL parameters is probably ok.
>
> I don't understand the concern about the dev branch version.  The release
> branch for 0.9.7 has been cut.  Any changes that go in develop are going in
> the next release.  That's how the git branching model works.  You can make
> any change you want in the dev branch right now.  It just won't be in the
> 0.9.7 release unless the RM decides to cherry-pick it, which they should
> not unless it is really important.  What am I missing?
>
> -Alex
>
> On 4/17/20, 3:09 AM, "Harbs"  wrote:
>
> Whatever you think is fine by me.
>
> I don’t remember why I have "if(location.hash)”. It’s possible you can
> get rid of that conditional.
>
> It could be you can get rid of that and handle hashRecieved in a bead.
> If the hashReceived event has no hash you can then check the URL.You do
> need to make sure that you always get a stateChange event and don’t
> dispatch it twice.
>
> Feel free to play around with the code… ;-)
>
> Harbs
>
> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com> wrote:
> >
> > I think it would be better to have it here in Router.
> >
> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >
> >> Alternatively, you can subclass Router to support setting the
> parameters
> >> in the onInit method.
> >>
> >> Not sure which of these is best.
> >>
> >>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >>>
> >>> Actually, it’s not going to work because the
> >> router.routeState.parameters will not be set.
> >>>
> >>> You will likely need to add code to set the
> router.routeState.parameters
> >> using the part of the location after the question mark.
> >>>
> >>> The easiest way to do that would be to either:
> >>> 1. Modify RouteToParameters.stateChanged to first check that there
> is a
> >> parameters value and then set it if not.
> >>> 2. Subclass RouteToParameters and override stateChanged to make
> that
> >> check first.
> >>>
>  On Apr 17, 2020, at 10:29 AM, Harbs   >> harbs.li...@gmail.com>> wrote:
> 
>  I’m pretty sure it’ll work without the hash as well.
> 
>  Give it a try.
> 
> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com >
> wrote:
> >
> > Hi Harbs,
> >
> > Thanks for pointing me out, but this is still that Routing
> expects me
> >> to
> > use in url hashes - The question is - What if I can't use
> hashes, but
> >> url
> > looks like I have presented in previous email ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 09:20 Harbs  >> harbs.li...@gmail.com>> napisał(a):
> >
> >> This app uses both path based and query based routing:
> >>
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddark&data=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717&sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3D&reserved=0
> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddark&data=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717&sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3D&reserved=0>
> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddark&data=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717&sdata=kGEULHJDYvZ1XHxq1GRF0FNx5%2BBwoXjDTZHw%2BppF6ks%3D&reserved=0
> <
> >>
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Funhurdle.github.io%2Fspectrum-royale%2F%23!asset%3Fcolorstop%3Ddark&data=02%7C01%7Caharui%40adobe.com%7C3f371b8193974ec8a47d08d7e2b77733%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637227149925562717&sdata=kGEUL

Re: Routing (was Re: Spectrum Components)

[Piotr Zarzycki]

Hi Harbs,

It sounds like you are asking me to check in onInit whether
if(location.hash) exists then do something, but if doesn't exists check url
params. - I may understand it in a wrong way, but I think location.hash may
exists and location.search - where parameters are stored could exists
equally.

if(location.hash)
{
  hashChangeHandler();
}

if (location.search)
{
   parseParameters();
}

Am I missing something ?

Thanks,
Piotr

pt., 17 kwi 2020 o 12:09 Harbs  napisał(a):

> Whatever you think is fine by me.
>
> I don’t remember why I have "if(location.hash)”. It’s possible you can get
> rid of that conditional.
>
> It could be you can get rid of that and handle hashRecieved in a bead. If
> the hashReceived event has no hash you can then check the URL.You do need
> to make sure that you always get a stateChange event and don’t dispatch it
> twice.
>
> Feel free to play around with the code… ;-)
>
> Harbs
>
> > On Apr 17, 2020, at 11:37 AM, Piotr Zarzycki 
> wrote:
> >
> > I think it would be better to have it here in Router.
> >
> > pt., 17 kwi 2020 o 09:37 Harbs  napisał(a):
> >
> >> Alternatively, you can subclass Router to support setting the parameters
> >> in the onInit method.
> >>
> >> Not sure which of these is best.
> >>
> >>> On Apr 17, 2020, at 10:35 AM, Harbs  wrote:
> >>>
> >>> Actually, it’s not going to work because the
> >> router.routeState.parameters will not be set.
> >>>
> >>> You will likely need to add code to set the
> router.routeState.parameters
> >> using the part of the location after the question mark.
> >>>
> >>> The easiest way to do that would be to either:
> >>> 1. Modify RouteToParameters.stateChanged to first check that there is a
> >> parameters value and then set it if not.
> >>> 2. Subclass RouteToParameters and override stateChanged to make that
> >> check first.
> >>>
>  On Apr 17, 2020, at 10:29 AM, Harbs  >> harbs.li...@gmail.com>> wrote:
> 
>  I’m pretty sure it’ll work without the hash as well.
> 
>  Give it a try.
> 
> > On Apr 17, 2020, at 10:23 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com > wrote:
> >
> > Hi Harbs,
> >
> > Thanks for pointing me out, but this is still that Routing expects me
> >> to
> > use in url hashes - The question is - What if I can't use hashes, but
> >> url
> > looks like I have presented in previous email ?
> >
> > Thanks,
> > Piotr
> >
> > pt., 17 kwi 2020 o 09:20 Harbs  >> harbs.li...@gmail.com>> napisał(a):
> >
> >> This app uses both path based and query based routing:
> >>
> >> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> >> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark> <
> >> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark <
> >> https://unhurdle.github.io/spectrum-royale/#!asset?colorstop=dark>>
> >>
> >> You can see how it’s done here:
> >>
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >> <
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >>>
> >> <
> >>
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >> <
> >>
> https://github.com/unhurdle/spectrum-royale/blob/master/SpectrumBrowser/src/view/BrowserRouter.mxml
> >>>
> >>>
> >>
> >>> On Apr 17, 2020, at 10:13 AM, Piotr Zarzycki <
> >> piotrzarzyck...@gmail.com >
> >> wrote:
> >>>
> >>> I'm still looking into the code and it looks like Routing
> >> implemented now
> >>> is not doing what I would expected. Everything is based on "hash"
> >> property
> >>> in "location". Instead I need something which is in "search" of
> >> location. I
> >>> will wait for your thoughts before I do try to handle stuff on my
> >> end.
> >>>
> >>> pt., 17 kwi 2020 o 08:30 Piotr Zarzycki  >> >
> >>> napisał(a):
> >>>
>  Hi Guys,
> 
>  I really thought that I will be able to use Router [1] based on
>  documentation and maybe eventually some look to the code [2] - to
> >> figure
>  out how things should be implemented. However it looks like non of
> >> the
>  existing stuff helps me to use in in real world application at
> all.
> >> I
> >> would
>  like to throw a simple question.
> 
>  I would like to "answer" in my application to following url, catch
> >> params
>  and do some actions:
> 
> 
> >> https://mydomain.com/somefolder/index.html?target=somevalue&account= <
> >> https://mydomain.com/somefolder/index.html?target=somevalue&account=>
>  <
> >>
> >>
> https://localdev.prominic.net/prominic/bin/js-debug/index.html?target=UpdateCreditCard&account=A55XXX
> >> <
>

Build failed in Jenkins: royale-asjs_jsonly #1308

[apacheroyaleci]

See 


Changes:


--
Started by upstream project "royale-typedefs" build number 548
originally caused by:
 Started by upstream project "royale-compiler" build number 355
 originally caused by:
  Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 48597d9f2cb779a8014932583c8b8aff1233d87f 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f
Commit message: "markdown-example: highlight as3 and mxml"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
'ant.bat' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1307

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 48597d9f2cb779a8014932583c8b8aff1233d87f 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f
Commit message: "markdown-example: highlight as3 and mxml"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
'ant.bat' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1304

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 48597d9f2cb779a8014932583c8b8aff1233d87f 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f
Commit message: "markdown-example: highlight as3 and mxml"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f # timeout=10
ERROR: Cannot find executable from the chosen Ant installation "Ant 1.9.9"
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1306

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 48597d9f2cb779a8014932583c8b8aff1233d87f 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f
Commit message: "markdown-example: highlight as3 and mxml"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
'ant.bat' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1305

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 48597d9f2cb779a8014932583c8b8aff1233d87f 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f
Commit message: "markdown-example: highlight as3 and mxml"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f # timeout=10
[royale-asjs_jsonly] $ cmd.exe /C "ant.bat 
-DROYALE_COMPILER_REPO=C:\jenkins\workspace\royale-compiler 
-Denv.ROYALE_TRANSPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler-jx 
'"-Dbrowser=C:\Program Files\Mozilla Firefox\firefox.exe"' 
-DROYALE_TYPEDEFS_HOME=C:\jenkins\workspace\royale-typedefs 
-Dbuild.noprompt=true -Dplayerglobal.version=11.7 
-Denv.ROYALE_COMPILER_HOME=C:\jenkins\workspace\royale-compiler\compiler 
release create-SHA-512 create-SHA-512-jsonly && exit %%ERRORLEVEL%%"
'ant.bat' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Invoke Ant' marked build as failure
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1303

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 48597d9f2cb779a8014932583c8b8aff1233d87f 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f
Commit message: "markdown-example: highlight as3 and mxml"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f # timeout=10
ERROR: Cannot find executable from the chosen Ant installation "Ant 1.9.9"
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1302

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
 > C:\Program Files\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 48597d9f2cb779a8014932583c8b8aff1233d87f 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f
Commit message: "markdown-example: highlight as3 and mxml"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f # timeout=10
ERROR: Cannot find executable from the chosen Ant installation "Ant 1.9.9"
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1301

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe init 
 > 
 >  # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe --version # timeout=10
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
 > C:\Program Files\Git\cmd\git.exe config --add remote.origin.fetch 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > C:\Program Files\Git\cmd\git.exe config remote.origin.url 
 > https://github.com/apache/royale-asjs # timeout=10
Fetching upstream changes from https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe fetch --tags --force --progress -- 
 > https://github.com/apache/royale-asjs +refs/heads/*:refs/remotes/origin/*
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/develop^{commit}" # timeout=10
 > C:\Program Files\Git\cmd\git.exe rev-parse 
 > "refs/remotes/origin/origin/develop^{commit}" # timeout=10
Checking out Revision 48597d9f2cb779a8014932583c8b8aff1233d87f 
(refs/remotes/origin/develop)
 > C:\Program Files\Git\cmd\git.exe config core.sparsecheckout # timeout=10
 > C:\Program Files\Git\cmd\git.exe checkout -f 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f
Commit message: "markdown-example: highlight as3 and mxml"
 > C:\Program Files\Git\cmd\git.exe rev-list --no-walk 
 > 48597d9f2cb779a8014932583c8b8aff1233d87f # timeout=10
ERROR: Cannot find executable from the chosen Ant installation "Ant 1.9.9"
Skipped archiving because build is not successful

Build failed in Jenkins: royale-asjs_jsonly #1300

[apacheroyaleci]

See 


Changes:


--
Started by user Apache Royale
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on agent2 in workspace 

No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/apache/royale-asjs
 > C:\Program Files\Git\cmd\git.exe init 
 > 
 >  # timeout=10
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:918)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:710)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
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.lambda$newThread$0(Engine.java:93)
at java.lang.Thread.run(Unknown Source)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
JNLP4-connect connection from 52.251.60.60/52.251.60.60:53048
at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
at hudson.remoting.Channel.call(Channel.java:957)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown 
Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
at com.sun.proxy.$Proxy65.execute(Unknown Source)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1152)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
at hudson.scm.SCM.checkout(SCM.java:504)
at 
hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at 
jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1815)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at 
hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Caused by: hudson.plugins.git.GitException: Error performing command: 
C:\Program Files\Git\cmd\git.exe init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2181)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2142)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2138)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1743)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:916)
... 12 more
Caused by: java.io.IOException: Cannot run program "C:\Program 
Files\Git\cmd\git.exe" (in directory 
":
 CreateProcess error=2, The system cannot find the file specified
at java.lang.ProcessBuilder.start(Unknown Source)
at hudson.Proc$LocalProc.(Proc.java:250)
at hudson.Proc$LocalProc.(Proc.java:219)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:937)
at hudson.Launcher$ProcStarter.start(Launcher.java:455)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(

Re: Build failed in Jenkins: royale-asjs #1097

[Greg Dove]

Did RoyaleUnits use of sockets change  How were tests running in the past
months?

AFAIK nothing changed in terms of how the tests are run by RoyaleUnit -
they launch the browser (chrome) and use websocket connection back to
royaleunit for js - same as they have been doing for many months now since
Josh set it up. I did make a change not so long ago to launch release
builds instead of debug builds, but I don't understand why that would
suddenly cause anything to stop working after it had been working without
issue for 2 weeks. Everything seemed to be working ok until CI build #1090,
and they also worked as normal for me locally this morning with up to date
code for a full build as well. Maybe something else changed on the server?



On Sun, Apr 19, 2020 at 5:13 PM Alex Harui  wrote:

> Did RoyaleUnits use of sockets change  How were tests running in the past
> months?
>
> -Alex
>
> On 4/18/20, 1:57 PM, "Greg Dove"  wrote:
>
> I am not sure what the actual issue on the server here is. It is saying
> there is a socket timeout issue from the browser launch.
> But this does provide an opportunity for a quick example of the
> information
> I shared recently about the changes to tests for JS, and it might be
> helpful for you to see that with a 'live' example.
>
> For the part of the output:
>
> [royaleunit] Executing 'C:\Program Files
> (x86)\Google\Chrome\Application\chrome.exe' with arguments:
> [royaleunit] '<
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2Fws%2Fframeworks%2Fjs%2Fprojects%2FBasicJS%2Fsrc%2Ftest%2Froyale%2Ftarget%2Fbin%2Fjs-release%2Findex.html&data=02%7C01%7Caharui%40adobe.com%7Cef4f8532c61643bdaee708d7e3db14ec%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637228402406166645&sdata=232mZKfJfIlUCHn4d9vFM1uCecmAyqXtacETu%2BkJyj0%3D&reserved=0
> '>
>
> If you simply launch that link in a browser you will see the normal
> launch
> of the royaleunit BasicJS tests (it is a blank white page - not
> particularly interesting in itself). If you look in the dev tools
> console for that page, you can see that it also did not find a socket
> server to connect to to report back the test results (which is
> definitely
> expected when you launch it like this, because there is of course none
> available).
> But you also will also see this in the console:
> For javascript you can run this locally with console output for
> debugging
> purposes, using "?local" appended to the url.
> It may not work for all browsers with file:// protocol (works with
> Chrome),
> in which case you need a local http server
>
> So if you append
> ?local
> to the url by simply typing that at the end of the original url in the
> browser and reload, you will see the following in the console:
>
> [JS] flexUnitTests::DataGridColumnTest.testLabelProperty .
> [JS] Time: 0.038
> [JS] OK (1 test)
>
> ...which means the tests themselves are not the problem here. There
> was no
> suggestion that they were...this was just to illustrate how you can
> toggle
> between CI style tests and console output of test results.
> The build error may indicate some issue with the chrome launch itself
> I am
> guessing (not sure).
> Aside: The css is not being served as the correct MIME type, so you
> may see
> console errors for that as well, but I think that has always been the
> case
> on the CI server (not sure).
>
>
>
> On Sun, Apr 19, 2020 at 8:19 AM  wrote:
>
> > See <
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2F1097%2Fdisplay%2Fredirect%3Fpage%3Dchanges&data=02%7C01%7Caharui%40adobe.com%7Cef4f8532c61643bdaee708d7e3db14ec%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637228402406166645&sdata=wNkfQBUzJ6HLdzaFBTr6Q4BRMi5p5K3832DcfKiFklc%3D&reserved=0
> > >
> >
> > Changes:
> >
> > [carlosrovira] markdown-example: highlight as3 and mxml
> >
> >
> > --
> > [...truncated 1.34 MB...]
> > [mxmlc] Loading configuration: <
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2Fws%2Fframeworks%2Fprojects%2FBasic%2Fsrc%2Ftest%2Froyale%2FFlexUnitRoyaleApplication-config.xml&data=02%7C01%7Caharui%40adobe.com%7Cef4f8532c61643bdaee708d7e3db14ec%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637228402406166645&sdata=AogF3nawDDPxuy4rnEi1PEGWXCNT1iAKh8WoL8J44us%3D&reserved=0
> > >
> > [mxmlc]
> > [mxmlc] 94132 bytes written to <
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2Froyale-asjs%2Fws%2Fframeworks%2Fprojects%2FBasic%2Fsrc%2Ftest%2Froyale%2FFlex

Re: Prioritize Release Jobs on CI

[OmPrakash Muppirala]

Update - I have successfully attached my VM as a slave agent of our Jenkins
instance.
I am going to pull the job - /royale-asjs_jsonly and tie it to my agent so
I can test it.

It will fail for a sometime while I go set up my VM with all the
dependencies.

Once we have the job successfully building on my VM, we can figure out how
to divide the load between the master and agent.

Thanks,
Om

On Sat, Apr 18, 2020 at 8:59 AM OmPrakash Muppirala 
wrote:

> We could achieve the same by creating a new agent (separate vm) and
> attaching it as a slave to the current Jenkins server.
>
> Then we can use labels/tags to tie release jobs to one agent and non
> release jobs to another agent.
>
> That way we can maintain everything in one UI, one login while achieving
> the concurrent building capabilities we want.
>
> Jenkins is built for this kind of stuff and I think it would be best we
> followed this practice.
>
> Thanks,
> Om
>
> On Sat, Apr 18, 2020, 8:18 AM Alex Harui  wrote:
>
>> Om, I thought you were going to get the image from my VM and run it on
>> another VM.  Then we'd remove all non-release jobs from your VM and all of
>> the release jobs from my VM.  That won't solve the problem of how long it
>> takes for a commit to be built and tested, but will allow the RM to get a
>> release out without getting stuck behind the commit jobs.  Is that
>> currently the plan?
>>
>> -Alex
>>
>> On 4/18/20, 12:43 AM, "OmPrakash Muppirala" 
>> wrote:
>>
>> Makes sense to me.  I will set parallel executors back to 1.
>>
>> And start working on a new Jenkins instance.
>>
>> Thanks,
>> Om
>>
>>
>> On Sat, Apr 18, 2020, 12:28 AM Alex Harui 
>> wrote:
>>
>> > Are you saying that Java, Ant and Maven do not know how to
>> distribute work
>> > to different cores?
>> >
>> > To repeat my main concern:  our Jenkins jobs often use shared
>> resources.
>> > If you want to take the time to fix that, feel free, but I do not
>> know how
>> > you are going to keep two jobs from both trying to launch Flash
>> Player
>> > Debugger at the same time and open the same socket to communicate
>> with it,
>> > or try to parse the flashlog.txt that they have both written to.
>> >
>> > The royale-asjs job will use the royale-compiler workspace to get
>> the
>> > compiler.  If the compiler is building, the jars are not there and
>> the
>> > royale-asjs build fails.
>> >
>> > There is also only so much memory and some of our jobs use all of
>> it and
>> > I'm not sure if jobs slowed down due to paging memory and
>> writing/reading
>> > from disk, even if it is an SSD.
>> >
>> > I'm done for tonight, but that's what I was seeing last time I
>> tried to
>> > have both master and an agent running jobs in parallel.
>> >
>> > Thanks,
>> > -Alex
>> >
>> > On 4/17/20, 11:52 PM, "OmPrakash Muppirala" 
>> wrote:
>> >
>> > A typical setup would be to have 0 executors on master and at
>> least n
>> > number of executors on each agent, where n = number of cpu
>> cores.
>> > I see that the current VM has 2 cores.  So, I started with
>> setting the
>> > num
>> > executors on the current agent to 2.
>> >
>> > This should improve things quite a bit.  If this doesn't work,
>> I will
>> > create a new VM and make it the slave agent of the current
>> Jenkins
>> > master.
>> >
>> >
>> > Thanks,
>> > Om
>> >
>> > On Fri, Apr 17, 2020 at 11:31 PM Alex Harui
>> 
>> > wrote:
>> >
>> > > On your VM or mine?  I don't think mine can handle it.  I
>> used to
>> > run jobs
>> > > of master and agent and we got lots of failures and jobs took
>> > forever.  If
>> > > two jobs are trying to run tests with the shared Flash Player
>> > Debugger, for
>> > > example, you won't get consistent results.
>> > >
>> > > -Alex
>> > >
>> > > On 4/17/20, 11:23 PM, "OmPrakash Muppirala" <
>> bigosma...@gmail.com>
>> > wrote:
>> > >
>> > > I just realized that we have only one Agent (node) listed
>> under
>> > > Jenkins.  I
>> > > am going to add at least one more node to start with.
>> > >
>> > > Thanks,
>> > > Om
>> > >
>> > > On Thu, Apr 16, 2020 at 9:58 AM Alex Harui
>> > 
>> > > wrote:
>> > >
>> > > > I think I followed the instructions and enabled SSH.
>> > > >
>> > > > On 4/16/20, 9:37 AM, "Yishay Weiss" <
>> yishayj...@hotmail.com>
>> > wrote:
>> > > >
>> > > > I haven’t gotten it to work. Could be ssh needs to
>> be
>> > enabled on
>> > > the
>> > > > VM [1]. This is nice to have but not essential. So
>> Alex, let
>> > me know
>> > > if you
>> > > > want to try