Closed EricR86 closed 6 years ago
Original comment by Eric Roberts (Bitbucket: ericr86, GitHub: ericr86).
I've confirmed this behavior and I've traced the first bad commit to 7ce987d70edd72d9773ea9a5c2d921678f15149e. To double check I also confirmed that a3b9724778e8b5e8a2a23855bd113aa7284869bf (the commit before), works as intended. It's not clear from the changeset what causes the change.
Original comment by Eric Roberts (Bitbucket: ericr86, GitHub: ericr86).
I suspect since it was just changing training to be submitted as a task, and that stderr is captured correctly, that the same mechanism used for stderr should be used for stdout and should have been updated with this change but wasn't.
Original report (BitBucket issue) by Rachel Chan (Bitbucket: rcwchan).
I noticed that standard output is no longer being captured (eg the
traindir/output/o
folder). I tested this usingsimpleseg
on changeset37e5b7a0acd003386c0c8a1fbd2917777bd57d4d
(prior to the GMM and validation pull requests). Standard error is fine.In particular, the files exist but are empty:
the touchstones seems to expect content there:
but the tests pass anyway (which may be a separate issue--it's possible that comparisons to empty return
TRUE
for some reason).An example of an expected output is: