>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<mailto:harbs.li...@gmail.com> Sent: Sunday, January 9, 2022 6:07 PM To: dev@royale.apache.org<mailto:dev@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 <yishayj...@hotmail.com> wrote: > > Great to hear. How did you fix it? > > From: Harbs<mailto:harbs.li...@gmail.com> > Sent: Sunday, January 9, 2022 5:58 PM > To: dev@royale.apache.org<mailto:dev@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 >
