Skip to content

Commit 517aa95

Browse files
authored
Fix exit code in certutil packaging test (elastic#38393)
The exit code is different on windows, and we don't really care about which code it is, we just need to check that it's not 0 (success)
1 parent 57600c5 commit 517aa95

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

qa/vagrant/src/main/java/org/elasticsearch/packaging/test/ArchiveTestCase.java

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,7 @@
5050
import static org.elasticsearch.packaging.util.ServerUtils.makeRequest;
5151
import static org.hamcrest.CoreMatchers.containsString;
5252
import static org.hamcrest.CoreMatchers.is;
53+
import static org.hamcrest.CoreMatchers.not;
5354
import static org.hamcrest.CoreMatchers.notNullValue;
5455
import static org.hamcrest.Matchers.isEmptyString;
5556
import static org.junit.Assume.assumeThat;
@@ -293,7 +294,7 @@ public void test90SecurityCliPackaging() {
293294

294295
// Ensure that the exit code from the java command is passed back up through the shell script
295296
result = sh.runIgnoreExitCode(bin.elasticsearchCertutil + " invalid-command");
296-
assertThat(result.exitCode, is(64));
297+
assertThat(result.exitCode, is(not(0)));
297298
assertThat(result.stdout, containsString("Unknown command [invalid-command]"));
298299
};
299300
Platforms.onLinux(action);

0 commit comments

Comments
 (0)