[SERVER-8171] Logging to stdout can break in V8 Created: 14/Jan/13 Updated: 11/Jul/16 Resolved: 15/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 2.3.2 |
| Fix Version/s: | 2.4.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Edit jstests/drop2.js to put a print statement after the last call to assert.soon, before it runs killOp. Run that test under v8 - the print statement never prints. Run it under spidermonkey and it does. I initially thought the output buffer just wasn't being flushed, but sleeping any amount of time, and/or adding more print statements with newlines doesn't help. |
| Comments |
| Comment by auto [ 15/Jan/13 ] |
|
Author: {u'date': u'2013-01-15T02:13:58Z', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: Use code that is more similar to native_print in engine_spidermonkey |
| Comment by Spencer Brody (Inactive) [ 14/Jan/13 ] |
|
This is making it difficult to debug a test failure in this test. |