Logs from node.js commands are missing some output
I'm seeing odd log results with some node.js build and test
output. I've disable colors thinking that might be the issue, but
the problem persists. Take for example how on line 1479 the
mocha test output stops abruptly on this node-mapnik
build:
https://ci.appveyor.com/project/springmeyer/node-mapnik/build/1.0.4...
at should not be painted after rendering. You can see
from the travis output that there should be a lot more test output
(https://travis-ci.org/mapnik/node-mapnik/jobs/26183941#L561).
Note: the oddly formatted travis output (missing line breaks) I
think is due to disabling colors.
Any idea what might be going on or further things to test? My experience with the interplay of subprocess and stdout/stderr on windows is limited. The reason this is important is not just missing test output but what appears to be completely missing stderr where node.js is throwing exceptions but the stack trace does not show up at all - so I can't figure out what is wrong.
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
Support Staff 1 Posted by Feodor Fitsner on 28 May, 2014 04:32 AM
Hi Dane,
Each command line is run as a separate process (if no
ps:prefix is used) and I can confirm (looking into the code) that both stdout and stderr are collected.You can try redirecting
npm testoutput to a file, push it to artifacts and then see its contents. I can't exclude it's AV console problem...so this simple test will check that.2 Posted by dane on 13 Jun, 2014 12:55 AM
Closing this issue. The problem is now solved thanks to fixes from Feodor. More details at https://github.com/mapnik/node-mapnik/issues/257#issuecomment-45571226.
dane closed this discussion on 13 Jun, 2014 12:56 AM.