CITGM test failing on s390

[gdams]

I get the following failure when running citgm-all on s390

# > fs-extra@0.30.0 test /tmp/0d719494-4ba8-4112-ae69-7921be2dfb03/fs-extra
# > npm run lint && npm run unit
# > fs-extra@0.30.0 lint /tmp/0d719494-4ba8-4112-ae69-7921be2dfb03/fs-extra
# > standard
# > fs-extra@0.30.0 unit /tmp/0d719494-4ba8-4112-ae69-7921be2dfb03/fs-extra
# > node test.js
# Can't write to device. Skipping test.
# ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
# ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
# ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
# ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
# ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
# ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
# ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
# ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
#433 passing (4s)
#2 pending
#1 failing
#1) utimes hasMillisResSync() should return a boolean indicating whether it has support:
# AssertionError: false == true
# + expected - actual
# -false
# +true
# 
# at Context.<anonymous> (lib/util/__tests__/utimes.test.js:40:16)
# npm ERR! Linux 3.10.0-327.13.1.el7.s390x
# npm ERR! argv "/dev/shm/usenode.jenkins0/node-v6.7.0-linux-s390/bin/node" "/dev/shm/usenode.jenkins0/node-v6.7.0-linux-s390/bin/npm" "run" "unit"
# npm ERR! node v6.7.0
# npm ERR! npm  v3.10.3
# npm ERR! code ELIFECYCLE
# npm ERR! fs-extra@0.30.0 unit: `node test.js`
# npm ERR! Exit status 1
# npm ERR! 
# npm ERR! Failed at the fs-extra@0.30.0 unit script 'node test.js'.
# npm ERR! Make sure you have the latest version of node.js and npm installed.
# npm ERR! If you do, this is most likely a problem with the fs-extra package,
# npm ERR! not with npm itself.
# npm ERR! Tell the author that this fails on your system:
# npm ERR!     node test.js
# npm ERR! You can get information on how to open an issue for this project with:
# npm ERR!     npm bugs fs-extra
# npm ERR! Or if that isn't available, you can get their info via:
# npm ERR!     npm owner ls fs-extra
# npm ERR! There is likely additional logging output above.
# npm ERR! Please include the following file with any support request:
# npm ERR!     /tmp/0d719494-4ba8-4112-ae69-7921be2dfb03/fs-extra/npm-debug.log
# npm ERR! Test failed.  See above for more details.

Any help would be apreciated

[gdams]

forgot to mention that this is on node 6.7.0

[jprichardson]

@GeorgeAdams95 could there be something going on with libuv and sub-millisecond time precision on the s390?

I've had this issue with Windows before. If you feel like digging:

• Windows: Setting fs.futimes{Sync} subsecond (millisecond) precision? nodejs/node#2069
• File timestamp resolution is inconsistent with fs.stat / fs.utimes nodejs/node-v0.x-archive#7000
• Node 0.12.0: fs.utimes does not set sub-second time on windows nodejs/node-v0.x-archive#9369

Thanks.

[RyanZim]

@GeorgeAdams95 @jprichardson Does this need to stay open?

[gdams]

well its an issue that we need to resolve right ? I suggest leaving it open to see if we can get a fix and close it if we can't within a few weeks

[RyanZim]

Closing for lack of action.