test: fix postmortem metadata test

Recent changes to spawnSync (#23027) broke our V8 postmortem tests since the output from nm was larger than the new default maxBuffer for spawnSync. Changing the maxBuffer to Infinity fixes the issue. PR-URL: #27265 Refs: v8/v8@7.4.288.18...7.4.288.21 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
nodejs · Apr 18, 2019 · 8712edf53a5f71f183a6a49b364d2bcb439d00ff · 8712edf
1 parent 7f29117
commit 8712edf53a5f71f183a6a49b364d2bcb439d00ff
Showing with 1 addition and 1 deletion.

+1 −1 test/v8-updates/test-postmortem-metadata.js
diff --git a/test/v8-updates/test-postmortem-metadata.js b/test/v8-updates/test-postmortem-metadata.js
@@ -21,7 +21,7 @@ if (common.isAIX)
 if (common.isOpenBSD)
   common.skip('no v8 debug symbols on OpenBSD');
 
-const nm = spawnSync('nm', args);
+const nm = spawnSync('nm', args, { maxBuffer: Infinity });
 
 if (nm.error && nm.error.errno === 'ENOENT')
   common.skip('nm not found on system');