Build failed, reason unknown

chris+appveyor's Avatar


19 Apr, 2017 09:09 PM

Dear AppVeyor support,

This build failed, and I don't know why:

All the output looks fine, all the tests pass, something must have gone wrong but I don't know what.

It suspiciously ends without the usual lines, but doesn't tell me why:

Time Elapsed 00:00:04.53
Command exited with code 1

Would it be possible to add the reason for failure to the summary at the top, and/or to the last line of console output?

Thanks, Chris.

  1. 1 Posted by Ilya Finkelshte... on 19 Apr, 2017 09:28 PM

    Ilya Finkelshteyn's Avatar

    Hi Chris,

    Build you sent is still building :). What about previous one, command which failed is cmake --build . --config %CONFIGURATION% --target package. I do not believe that we can create good summary for every custom command... To understand what command is failed you can just scroll up from the end till latest command called by build scenario (line in cyan color) and investigate traces after that.
    Actually I agree that scrolling up and looking for line in cyan is not very convenient, we need to improve that.


  2. 2 Posted by chris+appveyor on 20 Apr, 2017 08:46 PM

    chris+appveyor's Avatar

    Thanks for the quick reply! Sorry for sending the wrong link.

    In this build I had to search half way through the log to find the error message (at least it was highlighted in red):

    Error creating GitHub release: Provider setting not found.
    Parameter name: auth_token

    The system must know that this is an error, because it knows to highlight it in red. Couldn't it put a copy of this information at the top (in the summary) or at the end of the build log?

    There were also warnings, which it would be great to be able to see on the "messages" tab as well:

    No artifacts found matching 'packages\BoxBackup-*.zip' path
    No artifacts found matching 'packages\BoxBackup-*.exe' path

    Also, is there anything you can do to speed up logfile loading? It seems much slower than Travis for example, and it also doesn't appear to use the browser cache, since it takes ages to load every time I visit the page.

    Thanks, Chris.

  3. 3 Posted by Ilya Finkelshte... on 21 Apr, 2017 03:21 AM

    Ilya Finkelshteyn's Avatar

    Filed this issue to track slow console loading with long logs.
    Not sure about error summary though. Error message is not always complete enough to make good conclusions and root cause of error can be actually found somewhere much earlier in logs.

  4. chris+appveyor closed this discussion on 01 Jan, 2018 08:03 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? 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