You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Harbs <ha...@gmail.com> on 2022/01/09 15:58:11 UTC
CI Server back on track
I spent some time today getting the CI Server builds working again.
We just had our first successful js-only build in two weeks.
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/
Fingers crossed that royale-asjs will work too…
Harbs
Re: CI Server back on track
Posted by Harbs <ha...@gmail.com>.
I didn’t spend time figuring out which version was already there. I downloaded the version being used by the scripts.
Anyway, all good now. :-)
> On Jan 9, 2022, at 7:00 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> We don’t necessarily want the latest version there [1]. My aim was to place in c:\goog2 whatever was getting downloaded by the builds.
>
> [1] Re: [MAVEN-BUILD] Royale » Royale-asjs - Build # 2015 - Still Failing!-Apache Mail Archives<https://lists.apache.org/thread/w6l44g8kcqn9zovp030531osq7n7sof5>
>
> From: Harbs<ma...@gmail.com>
> Sent: Sunday, January 9, 2022 6:43 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: CI Server back on track
>
> I’m pretty sure the version in there was a newer version. We were getting ES6 errors. GCC probably changed some defaults in newer versions.
>
>> On Jan 9, 2022, at 6:17 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>>
>> I had already replaced C:\goog2 contents, and added a job to terminate all FF processes after a royale-asjs-jsonly run.
>
RE: CI Server back on track
Posted by Yishay Weiss <yi...@hotmail.com>.
We don’t necessarily want the latest version there [1]. My aim was to place in c:\goog2 whatever was getting downloaded by the builds.
[1] Re: [MAVEN-BUILD] Royale » Royale-asjs - Build # 2015 - Still Failing!-Apache Mail Archives<https://lists.apache.org/thread/w6l44g8kcqn9zovp030531osq7n7sof5>
From: Harbs<ma...@gmail.com>
Sent: Sunday, January 9, 2022 6:43 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: CI Server back on track
I’m pretty sure the version in there was a newer version. We were getting ES6 errors. GCC probably changed some defaults in newer versions.
> On Jan 9, 2022, at 6:17 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> I had already replaced C:\goog2 contents, and added a job to terminate all FF processes after a royale-asjs-jsonly run.
Re: CI Server back on track
Posted by Harbs <ha...@gmail.com>.
I’m pretty sure the version in there was a newer version. We were getting ES6 errors. GCC probably changed some defaults in newer versions.
> On Jan 9, 2022, at 6:17 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> I had already replaced C:\goog2 contents, and added a job to terminate all FF processes after a royale-asjs-jsonly run.
Re: CI Server back on track
Posted by Harbs <ha...@gmail.com>.
> I hope that was the missing piece. Did you do it after a successful run or before?
Before.
> On Jan 9, 2022, at 6:17 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
>> Basically just downloaded https://github.com/google/closure-library/archive/v20180910.zip and replaced the contents of C:\goog2.
>
>> I also needed to close Firefox.
>
> I had already replaced C:\goog2 contents, and added a job to terminate all FF processes after a royale-asjs-jsonly run.
>
>> I needed to make some of the new tests more tolerant to slower processors too.
>
> I hope that was the missing piece. Did you do it after a successful run or before?
>
> From: Harbs<ma...@gmail.com>
> Sent: Sunday, January 9, 2022 6:07 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: Re: CI Server back on track
>
> Basically just downloaded https://github.com/google/closure-library/archive/v20180910.zip and replaced the contents of C:\goog2.
>
> I also needed to close Firefox.
>
> I needed to make some of the new tests more tolerant to slower processors too.
>
>> On Jan 9, 2022, at 5:59 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>>
>> Great to hear. How did you fix it?
>>
>> From: Harbs<ma...@gmail.com>
>> Sent: Sunday, January 9, 2022 5:58 PM
>> To: dev@royale.apache.org<ma...@royale.apache.org>
>> Subject: CI Server back on track
>>
>> I spent some time today getting the CI Server builds working again.
>>
>> We just had our first successful js-only build in two weeks.
>> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/
>>
>> Fingers crossed that royale-asjs will work too…
>>
>> Harbs
>>
>
RE: CI Server back on track
Posted by Yishay Weiss <yi...@hotmail.com>.
>Basically just downloaded https://github.com/google/closure-library/archive/v20180910.zip and replaced the contents of C:\goog2.
>I also needed to close Firefox.
I had already replaced C:\goog2 contents, and added a job to terminate all FF processes after a royale-asjs-jsonly run.
> I needed to make some of the new tests more tolerant to slower processors too.
I hope that was the missing piece. Did you do it after a successful run or before?
From: Harbs<ma...@gmail.com>
Sent: Sunday, January 9, 2022 6:07 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: CI Server back on track
Basically just downloaded https://github.com/google/closure-library/archive/v20180910.zip and replaced the contents of C:\goog2.
I also needed to close Firefox.
I needed to make some of the new tests more tolerant to slower processors too.
> On Jan 9, 2022, at 5:59 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> Great to hear. How did you fix it?
>
> From: Harbs<ma...@gmail.com>
> Sent: Sunday, January 9, 2022 5:58 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: CI Server back on track
>
> I spent some time today getting the CI Server builds working again.
>
> We just had our first successful js-only build in two weeks.
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/
>
> Fingers crossed that royale-asjs will work too…
>
> Harbs
>
Re: CI Server back on track
Posted by Harbs <ha...@gmail.com>.
Basically just downloaded https://github.com/google/closure-library/archive/v20180910.zip and replaced the contents of C:\goog2.
I also needed to close Firefox.
I needed to make some of the new tests more tolerant to slower processors too.
> On Jan 9, 2022, at 5:59 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
> Great to hear. How did you fix it?
>
> From: Harbs<ma...@gmail.com>
> Sent: Sunday, January 9, 2022 5:58 PM
> To: dev@royale.apache.org<ma...@royale.apache.org>
> Subject: CI Server back on track
>
> I spent some time today getting the CI Server builds working again.
>
> We just had our first successful js-only build in two weeks.
> http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/
>
> Fingers crossed that royale-asjs will work too…
>
> Harbs
>
RE: CI Server back on track
Posted by Yishay Weiss <yi...@hotmail.com>.
Great to hear. How did you fix it?
From: Harbs<ma...@gmail.com>
Sent: Sunday, January 9, 2022 5:58 PM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: CI Server back on track
I spent some time today getting the CI Server builds working again.
We just had our first successful js-only build in two weeks.
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/
Fingers crossed that royale-asjs will work too…
Harbs
Re: CI Server back on track
Posted by Harbs <ha...@gmail.com>.
Yay!
create-SHA-512 <> <>:
[echo] Generating SHA-512 hashes for release artifacts
create-SHA-512-jsonly <> <>:
[echo] Generating SHA-512 hashes for release artifacts
BUILD SUCCESSFUL
Total time: 54 minutes 9 seconds
> On Jan 9, 2022, at 5:58 PM, Harbs <ha...@gmail.com> wrote:
>
> Fingers crossed that royale-asjs will work too…