From bb686a2236961da7a6076d337f334fddde992449 Mon Sep 17 00:00:00 2001 From: ridiculousfish Date: Sat, 21 Jan 2017 12:56:22 -0800 Subject: [PATCH] Enable some test_illegal_command_exit_code tests A comment suggests these cause bad_alloc, but this doesn't seem to happen. If it does happen, we want to hit it so we can track it down! --- src/fish_tests.cpp | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/fish_tests.cpp b/src/fish_tests.cpp index ad8fd6af5..e5d6d9b11 100644 --- a/src/fish_tests.cpp +++ b/src/fish_tests.cpp @@ -4080,10 +4080,8 @@ static void test_illegal_command_exit_code(void) { {L"**", STATUS_ILLEGAL_CMD}, {L"%", STATUS_ILLEGAL_CMD}, {L"%test", STATUS_ILLEGAL_CMD}, - // the following two inputs cause errors during tests for unknown reasons - // ("terminate called after throwing an instance of 'std::bad_alloc'") - // {L"?", STATUS_ILLEGAL_CMD}, - // {L"abc?def", STATUS_ILLEGAL_CMD}, + {L"?", STATUS_ILLEGAL_CMD}, + {L"abc?def", STATUS_ILLEGAL_CMD}, {L") ", STATUS_ILLEGAL_CMD}}; int res = 0;