From b9b49ee66feeecaa76a1b6bfd3e12e4d590256f9 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Wed, 6 Jul 2016 20:26:05 -0700 Subject: [PATCH] test: fix flaky test-fs-read-buffer-tostring-fail The test is memory intensive and times out occasionally on Raspberry Pi devices in CI. Successful test runs take about 90 seconds, but the devices time out after 120 seconds. That's not a lot of headroom. So let's skip the test on devices that have only modest amounts of memory. Fixes: https://github.com/nodejs/node/issues/7042 PR-URL: https://github.com/nodejs/node/pull/7575 Reviewed-By: Rod Vagg Reviewed-By: Evan Lucas Reviewed-By: Santiago Gimeno --- test/parallel/test-fs-read-buffer-tostring-fail.js | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/test/parallel/test-fs-read-buffer-tostring-fail.js b/test/parallel/test-fs-read-buffer-tostring-fail.js index 3a3f77c05bb016..cce33edf4e6947 100644 --- a/test/parallel/test-fs-read-buffer-tostring-fail.js +++ b/test/parallel/test-fs-read-buffer-tostring-fail.js @@ -1,6 +1,13 @@ 'use strict'; const common = require('../common'); + +if (!common.enoughTestMem) { + const skipMessage = 'intensive toString tests due to memory confinements'; + common.skip(skipMessage); + return; +} + const assert = require('assert'); const fs = require('fs'); const path = require('path');