An "empty" build failure
I'm getting an immediate failure with *no log messages* at all.
See https://ci.appveyor.com/project/mzgol/grunt-defs/build/15/job/3r0ojmto49ugdcj3
On Travis the same build passes: https://travis-ci.org/EE/grunt-defs/builds/35438556
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Michał Gołębiow... on 16 Sep, 2014 02:25 PM
Ah, there is a message, just not in the console but on the Messages tab. But it shows that it's AppVeyor's problem in fact:
ErrorCode<ERRCA0018>:SubStatus<ES0001>:The request timed out.. Additional Information : The client was trying to communicate with the server: net.tcp://appveyorciwest.cache.windows.net:22233.
Support Staff 2 Posted by Feodor Fitsner on 16 Sep, 2014 02:51 PM
Will take a look.
-Feodor
Support Staff 3 Posted by Feodor Fitsner on 16 Sep, 2014 04:19 PM
It's been sporadic error while accessing Azure Cache.
4 Posted by Michał Gołębiow... on 17 Sep, 2014 11:19 AM
OK, but I'm still getting a lot of different errors: see eg. https://ci.appveyor.com/project/mzgol/check-dependencies/build/69/job/bgi2aij4v1cdcf7a
This whole project has been failing a lot recently; errors look like npm network issues but at the same time Travis builds fine.
Support Staff 5 Posted by Feodor Fitsner on 17 Sep, 2014 04:43 PM
Yeah, we are not happy with recent Azure outages/maintenance/connectivity issues as well and are actively working to mitigate these issues.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:48 AM.