Stack trace is missing from the end of the build log

dnephin's Avatar


18 Nov, 2015 06:10 PM


I've noticed this a few times, you can see an example of it at the very end of this build:

The last line is Stop: Traceback (most recent call last):, but it's missing the actual traceback. If I run it locally I see a traceback which contains the important details required to fix the problem.

  1. Support Staff 1 Posted by Feodor Fitsner on 18 Nov, 2015 06:27 PM

    Feodor Fitsner's Avatar

    How is that traceback generated/outputted?

  2. 2 Posted by dnephin on 18 Nov, 2015 06:30 PM

    dnephin's Avatar

    I'm not that familiar with the windows terminology. On linux it would be printed to stderr. It should be just printed to the console the same way as the other error messages. The traceback itself comes from python.

  3. Support Staff 3 Posted by Feodor Fitsner on 18 Nov, 2015 07:23 PM

    Feodor Fitsner's Avatar

    Maybe that's because build script runs as PowerShell? Here, for example, traceback is visible:

  4. 4 Posted by dnephin on 18 Nov, 2015 07:47 PM

    dnephin's Avatar

    That's possible. Is there something special about powershell that might be causing it?

  5. Support Staff 5 Posted by Feodor Fitsner on 18 Nov, 2015 07:49 PM

    Feodor Fitsner's Avatar

    Well, when it's being run as PowerShell then PS collects the output. Anyway, you should give it a try.

    - Feodor

  6. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:02 AM.

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