Asyc failing with citgm on linux

[gdams]

ASNC 2.1.2
NODE 6.9.1

npm install -g citgm

`citgm -v verbose -q error async

when running citgm I get the following failure on SLES12, RHEL7 & UBUNTU 14.04.

not ok 48 - async v2.1.2 The canary is dead:
# > async@2.1.2 test /tmp/11e63884-890e-4494-b112-b889369aec9f/async
# > npm run lint && npm run mocha-node-test
# > async@2.1.2 lint /tmp/11e63884-890e-4494-b112-b889369aec9f/async
# > eslint lib/ mocha_test/ perf/memory.js perf/suites.js perf/benchmark.js support/build/ support/*.js karma.conf.js
# > async@2.1.2 mocha-node-test /tmp/11e63884-890e-4494-b112-b889369aec9f/async
# > mocha mocha_test/ --compilers js:babel-core/register
# <--- Last few GCs --->
#10030 ms: Mark-sweep 494.7 (707.6) -> 492.5 (704.6) MB, 116.7 / 0.0 ms [allocation failure] [GC in old space requested].
#10157 ms: Mark-sweep 492.5 (704.6) -> 492.5 (700.6) MB, 126.8 / 0.0 ms [allocation failure] [GC in old space requested].
#10301 ms: Mark-sweep 492.5 (700.6) -> 492.4 (669.6) MB, 143.9 / 0.0 ms [last resort gc].
#10432 ms: Mark-sweep 492.4 (669.6) -> 492.4 (651.6) MB, 130.9 / 0.0 ms [last resort gc].
# <--- JS stacktrace --->
# ==== JS stack trace =========================================
# Security context: 0x4d47b815 <JS Object>
#1: SparseJoinWithSeparatorJS(aka SparseJoinWithSeparatorJS) [native array.js:~75] [pc=0x29252eab] (this=0x4d4081d9 <undefined>,w=0xc52869d1 <JS Array[10168]>,F=0xd53956bd <JS Array[10168]>,x=10168,I=0x4d46dd61 <JS Function ConvertToString (SharedFunctionInfo 0x4d4365f5)>,J=0xd539569d <String[4]\: ,\n  >)
#2: DoJoin(aka DoJoin) [native array.js:137] [pc=0xc485623e] (this=0x4d4081d9 <undefined...
# FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
#1: node::Abort() [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#2: 0x8c7a986 [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#3: v8::Utils::ReportApiFailure(char const*, char const*) [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#5: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#6: v8::internal::Runtime_SparseJoinWithSeparator(int, v8::internal::Object**, v8::internal::Isolate*) [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#7: 0x53f0a7fe
#8: 0x29252eab
#9: 0xc485623e
#10: 0xc4855d22
#11: 0xc4850737
#12: 0xc485098f
#13: 0xc484ff74
#14: 0xc4876336
#15: 0xc486232e
#16: 0xc48300f7
#17: 0x53f0bc36
#18: 0xc484f7eb
#19: 0xc484f42d
#20: 0xc484f189
#21: 0xc485f865
#22: 0xc485f718
#23: 0x53f38db2
#24: 0x53f37606
#25: 0x53f327fe
#26: 0x53f218c3
#27: v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#28: v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#29: v8::Function::Call(v8::Local<v8::Value>, int, v8::Local<v8::Value>*) [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#30: node::LoadEnvironment(node::Environment*) [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#31: node::Start(int, char**) [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#32: main [/run/shm/usenode.jenkins0/node-v6.9.1-linux-x86/bin/node]
#33: __libc_start_main [/lib/i386-linux-gnu/libc.so.6]
# sh: line 1:  1307 Aborted                 npm run mocha-node-test
# npm ERR! Test failed.  See above for more details.

[megawac]

Works for me on my machine

$ citgm -v verbose -q error async

# ...

info:    passing module(s)   |                     
info:    module name:        | async               
info:    version:            | 2.1.2               
info:    done                | The smoke test has passed.

Likely an intermittent failure

[hargasinski]

This might be related to #1303. If the issue is reported a couple more times, we might want to take a look at what could be done to make the test more stable.

[gdams]

@megawac @hargasinski, i'm happy to take a look into what might be different about our two environments but a single pass shouldn't validate closing this issue yet

[megawac]

I closed the issue because there is another issue open about the flakey
tests

On Monday, 24 October 2016, George Adams notifications@github.com wrote:

@megawac https://github.com/megawac @hargasinski
https://github.com/hargasinski, i'm happy to take a look into what
might be different about our two environments but a single pass shouldn't
validate closing this issue yet

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1311 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADUIEO4hhmx9eIkRrMJN7uCZEF2V4RSXks5q3FT6gaJpZM4KdVW5
.