Home → Problems →

"Not found" error

• Edit

Mailaender

21 May, 2015 06:33 AM

See https://ci.appveyor.com/project/OpenRA/openra and all of the current https://github.com/OpenRA/OpenRA/pulls

I can't even press the restart button, because the builds are simply not created.

1. 1 Posted by lasse.schuirman... on 21 May, 2015 07:34 AM

   

   Same here:
   https://ci.appveyor.com/project/sils1297/coala/history

   https://github.com/coala-analyzer/coala/pull/564

   • Edit

2. 2 Posted by Stefanos Anasta... on 21 May, 2015 01:31 PM

   

   Same here

   https://ci.appveyor.com/project/sanastasiou/rtextnpp/history

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 21 May, 2015 01:44 PM

   

   Will take a look.

   - Feodor

   • Edit

4. 4 Posted by Fred on 21 May, 2015 02:27 PM

   

   Same here.

   Forced a new build by clicking att the button on the previously successful build.
   Now it just sits in Queued state

   • Edit

5. 5 Posted by Joshua Smith on 21 May, 2015 02:39 PM

   

   Same here.. lots of builds that appear to queue and sit, blocking the queue, but never generate a build number.

   https://ci.appveyor.com/project/LearningMachine/goodprospect2015/history

   • Edit

6. 6 Posted by Fred on 21 May, 2015 02:42 PM

   

   Mine has started to build again.
   I cancelled a queued build and clicked on RE-BUILD COMMIT,
   then it started working.

   • Edit

7. 7 Posted by James Skimming on 21 May, 2015 02:43 PM

   

   We've noticed the same for us, as well as a few other instabilities (I've no idea if they're related).

   For instance, some of the commit notifications on PRs in GitHub are not always resulting in builds, or sometimes a build completes and build status of the PR commit is still left as building.

   They're all mostly minor niggles, but I thought it worth adding to the mix.

   • Edit

8. 8 Posted by Joshua Smith on 21 May, 2015 02:46 PM

   

   This is blocking us.. our last 10 commits have been unsuccessful and most either have no build log or are not found..

   • Edit

9. 9 Posted by Joshua Smith on 21 May, 2015 02:48 PM

   

   Following up -- this behavior started at around 3:30 PM CST

   • Edit

10. Support Staff 10 Posted by Feodor Fitsner on 21 May, 2015 02:48 PM

    

    It should be OK now. Seems like the issue has been found and fixed.

    • Edit

11. Support Staff 11 Posted by Feodor Fitsner on 21 May, 2015 04:46 PM

    

    The problem was in one of AppVeyor Azure workers having connectivity issues with Redis cache. Restarting that worker helped.

    We are removing those failed builds without version numbers from projects history.

    • Edit

12. Mailaender closed this discussion on 21 May, 2015 07:26 PM.

13. Mailaender re-opened this discussion on 21 May, 2015 07:26 PM

14. 12 Posted by Mailaender on 21 May, 2015 07:26 PM

    

    Thanks!

    • Edit

15. Mailaender closed this discussion on 21 May, 2015 07:26 PM.