How to restart an appveyor job?
Locked
How to restart an appveyor job?
 
|
Hi all, I wanted to solve the gcc compiler bug for pharo.sista.spur.https://ci.appveyor.com/project/OpenSmalltalk/vm/build/1.0.1207/job/dd3lnytbwb5jjlqa Running Install scripts Start-FileDownload "http://cygwin.com/setup-x86.exe" -FileName "setup-x86.exe" Start-FileDownloadInternal : Error downloading remote file: One or more errors occurred. Inner Exception: Unable to connect to the remote server At C:\Program Files\AppVeyor\BuildAgent\Modules\build-worker-api\build-worker-api.psm1:242 char:2 + Start-FileDownloadInternal -Url $Url -FileName $FileName -Timeout ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Start-FileDownloadInternal], Exception + FullyQualifiedErrorId : System.Exception,Appveyor.BuildAgent.Api.Utils.StartFileDownloadInternalCmdlet We depend on volatile URL... Do you know if there is a way to restart a job in appveyor? |
Re: How to restart an appveyor job?
|
|
I don't know if upvoting will change a thing, but I did. 2018-04-02 14:32 GMT+02:00 Nicolas Cellier <[hidden email]>:
|
|
|
In reply to this post by Nicolas Cellier
On 2 April 2018 at 20:32, Nicolas Cellier <[hidden email]> wrote:
Two questions in ignorance... Why do we download & install Cygwin when it seems already included? I don't see "image:" in https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/.appveyor.yml so should I presume our builds use "Visual Studio 2015" image? cheers -ben btw, I followed your lead to add an upvote. |
Re: How to restart an appveyor job?
|
|
2018-04-02 16:09 GMT+02:00 Ben Coman <[hidden email]>:
Hi Ben, It's because we rely on specific pre-built packages which are not on the appveyor machine. But in the next build that's Smalltalk-CI which failed to be downloaded, so we have multiple weakness.
Maybe it's leading to nowhere, but thanks Ben ;) |
Re: How to restart an appveyor job?
|
|
2018-04-02 16:20 GMT+02:00 Nicolas Cellier <[hidden email]>:
This happened again https://ci.appveyor.com/project/OpenSmalltalk/vm/build/1.0.1212/job/jtau0f796r5xd06u and will happen again and again... I am trying to replace 'Start-FileDownload "http://cygwin.com/setup-x86.exe" -FileName "setup-x86.exe"' with curl, so as to at least manage the timeout and retry options: See https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/aaaa4b1e8c1fb5448ea45856479cc51c60324b26
|
|
|
In reply to this post by Nicolas Cellier
On 2 April 2018 at 20:32, Nicolas Cellier <[hidden email]> wrote: (https://www.cygwin.com/faq.html)
Seems quite susceptible to the ground unknowingly moving under our feet. Actually I found it quite difficult (i.e. failed) to determine a hard link to the version being installed. To enhance reproduciblity, we should host our own versioned archive of the required packages somewhere fairly permanent. This seems pertinent... 2.2.What about an automated Cygwin installation? If you are deploying to multiple systems, the best way is to run through a full installation once, saving the entire downloaded package tree. Then, on target systems, run Cygwin Setup as a "Local Install" pointed at your downloaded package tree. You could do this non-interactively with the command line options -q -L -l x:\cygwin-local\, where your downloaded package tree is in x:\cygwin-local\ (see the next FAQ for an explanation of those options.) And "pmcyg" looks interesting... "intended to support construction of a self-contained CDROM or DVD that can be used to install or upgrade Cygwin on computers that do not have network access to a Cygwin mirror site." That could be stored as a versioned archive which is added to the appveyor build cache so its only downloaded once,
saving per job build time and ensuring if it succeeds at the first job, all other jobs *should* succeed. Options to host this versioned-cygwin-installer-archive (should be somewhere fairly permanent): * bintray * github releases * git large file storage cheers -ben |
|
On Mon, Apr 2, 2018 at 5:55 PM Ben Coman <[hidden email]> wrote:
Instead of hosting our own Cygwin setup, maybe it's better to use the build cache [1]? We are already using that cache for third-party libs [2] and I also thought we'd cache Cygwin as well. @Nicolas: could you give this a go? Fabio
|
Re: How to restart an appveyor job?
|
|
Hi Fabio, I've switched to curl for now and have a build in progress...2018-04-02 18:13 GMT+02:00 Fabio Niephaus <[hidden email]>:
|
|
|
On Mon, Apr 2, 2018 at 6:23 PM Nicolas Cellier <[hidden email]> wrote:
curl makes sense!
That's right. Another idea for hosting our custom Cygwin: another Git repository, for example OpenSmalltalk/build-cygwin. This way, we could track changes as well.
|
|
|
On 3 April 2018 at 00:34, Fabio Niephaus <[hidden email]> wrote:
This might fork https://github.com/cygwin/cygwin. Then later when its time to upgrade cygwin, someone would fork upstream https://github.com/cygwin/cygwin
to their local machine, and after testing just push to
https://github.com/OpenSmalltalk/cygwin. Or for the parnoid, clone locally direct from https://cygwin.com/git.html and push to
https://github.com/OpenSmalltalk/cygwin-mirror.
Build instructions here are not clear what is required to then install it. Would its setup.exe still need to be run anyway? Somewhere would still be needed to host the binaries produced. The cygwin build would only need to be done infrequently. cheers -ben
|
«
Return to Squeak VM
|
1 view|%1 views
| Free forum by Nabble | Edit this page |