Home → Problems →

Why is the build hanging in 'on_success'?

• Edit

Hari Menon

29 Apr, 2014 05:55 AM

Here is the latest build that is still running at the point of creating this issue - https://ci.appveyor.com/project/floydpink/flickr-downloadr-gtk/buil...

I had cancelled a few before this and unfortunately the log is not anymore visible on those cancelled builds (another separate issue, I guess)...

I have not been able to figure out why, though the script is a little involved. Could you please take a look and let me know if you see something?

Here is the on_success part of the appveyor.yml (It is hanging in the penultimate line):

on_success:  
- git config --global user.name "The CI Bot"
- git config --global user.email "[email blocked]"
- set /p buildNumber= <build.number
- cd ..\..
- git clone -b master %REPO%
- cd flickr-downloadr.github.io
- git config credential.helper "store --file=.git\fd-credentials"
- echo "https://%GH_TOKEN%:@github.com" > .git\fd-credentials
- git config push.default tracking
- git checkout -b deploy-v%buildNumber%
- xcopy /E ..\flickr-downloadr-gtk\dist installer
- git add -f .
- git commit -m "created release v%buildNumber% (appveyor) [ci skip]" -s
- git pull --rebase origin deploy-v%buildNumber%
- git push -u origin deploy-v%buildNumber%

1. Support Staff 1 Posted by Feodor Fitsner on 29 Apr, 2014 06:02 AM

   

   I think the script requires an interactive input at some point - this is the most typical cause of hanging build. Most probably it's one of git commands. Have you tried this script locally?

   • Edit

2. 2 Posted by Hari Menon on 29 Apr, 2014 03:51 PM

   

   Thank you, Feodor.

   These commands run fine without breaking into interactive mode when ran locally.

   Also, when the build died yesterday taking the maximum 30 minutes, it was stuck at the very last line above - git push -u origin deploy-v%buildNumber%, which is basically pushing the local, rebased commits to GitHub.

   I had a feeling that the network speed on the VM could be one of the reasons - because this repo is in the order of 200+ MBs at this point and maybe that's the root cause.

   Also, as an aside, the fact that all the failed/cancelled builds doesn't show the log anymore is something that is not helping to troubleshoot the issue either - all builds 1.0.75 to 1.0.80 here does not show anything in the build log (console).

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 29 Apr, 2014 07:03 PM

   

   OK, the problem with disappearing cache is a problem. I suspect it was caused by eviction settings for the app cache. I've increased TTL - it should be fixed now.

   VM is connected to 100MB network, but yes there are lags sometimes.

   I'm wondering if using tagging would make the process lighter?

   • Edit

4. 4 Posted by Hari Menon on 29 Apr, 2014 09:56 PM

   

   Good to know that the logs will now be retained - will keep an eye out for that.

   I switched to using Shell scripting instead of CMD - and that seems to have helped with the git commands working well...

   Issues with the reliability of the connection is still there with some intermittent builds failing to download things - but guess that is not too bad.

   Thank you, as always.

   • Edit

5. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:43 AM.