You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✖ mjob create --close -or date
Assertion Message: stdout is a date: Sat Jan 14 00:33:04 2017
AssertionError: false == true
at Object.ok (/ws/node-manta/node_modules/nodeunit/lib/types.js:83:39)
at /ws/node-manta/test/mjob-simple.test.js:80:11
at ChildProcess.<anonymous> (/ws/node-manta/test/mjob-simple.test.js:61:9)
at ChildProcess.emit (events.js:110:17)
at maybeClose (child_process.js:1019:16)
at Process.ChildProcess._handle.onexit (child_process.js:1091:5)
It's a little hard to tell, but I think this was introduced in coreutils 8.24 and fixed in coreutils 8.26.
If you run the node-manta test suite against a Manta with a default compute image of 16.1.0, you run into this issue. This ends up true for new deployments, though not the Joyent public Manta.
The text was updated successfully, but these errors were encountered:
Reviewed by: Brian Bennett <brian.bennett@joyent.com>
Reviewed by: Robert Mustacchi <rm@joyent.com>
Approved by: Brian Bennett <brian.bennett@joyent.com>
Approved by: Robert Mustacchi <rm@joyent.com>
There was a regression in GNU date where the time zone was not printed:
http://www.mail-archive.com/bug-coreutils@gnu.org/msg28332.html
It's a little hard to tell, but I think this was introduced in coreutils 8.24 and fixed in coreutils 8.26.
If you run the node-manta test suite against a Manta with a default compute image of 16.1.0, you run into this issue. This ends up true for new deployments, though not the Joyent public Manta.
The text was updated successfully, but these errors were encountered: