diff --git a/test/exec-errors.js b/test/exec-errors.js
index <HASH>..<HASH> 100644
--- a/test/exec-errors.js
+++ b/test/exec-errors.js
@@ -24,7 +24,6 @@ suite.addBatch({
 			'a `ChildProcess` object is returned': childProcessTest,
 			'an error is sent to the callback': function(childProcess, err, stdout) {
 				assert(err);
-				assert.equal(err.toString(), 'Error: spawn nonexistant ENOENT');
 			},
 			'the result is the null string': function(childProcess, err, stdout) {
 				assert.equal(stdout, '');
Don't test the error string of exec errors

These errors are generated directly by the Node.js runtime and passed
on unchanged. Making assertions about their contents is needlessly
coupling things to implementation, doesn't give us anything, and in
fact actively harms us because the fact that the error text varies
across Node versions causes CI failures.

Therefore, remove the relevant assertion.