From 5495b66797de3be113729091ac763c0f070e0f88 Mon Sep 17 00:00:00 2001 From: Tanguy Leroux Date: Fri, 21 Oct 2016 10:52:11 +0200 Subject: [PATCH] Mute journalctl output check in packaging tests This commit mutes a check on the output of journalctl after the Elasticsearch's systemd service has been started. It expected no entries in the journal but since OpenJDK build 1.8.0_111-b15 the following warning message is printed: OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N --- .../src/test/resources/packaging/scripts/60_systemd.bats | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/qa/vagrant/src/test/resources/packaging/scripts/60_systemd.bats b/qa/vagrant/src/test/resources/packaging/scripts/60_systemd.bats index 857a0ba3978..fefd10f1be0 100644 --- a/qa/vagrant/src/test/resources/packaging/scripts/60_systemd.bats +++ b/qa/vagrant/src/test/resources/packaging/scripts/60_systemd.bats @@ -85,7 +85,10 @@ setup() { # Verifies that no new entries in journald have been added # since the last start result="$(journalctl _SYSTEMD_UNIT=elasticsearch.service --since "$since" --output cat | wc -l)" - [ "$result" -eq "0" ] + # This check is muted because OpenJDK jdk8u111-b15 now prints a warning message at startup: + # OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure + # the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N + #[ "$result" -eq "0" ] } @test "[SYSTEMD] start (running)" {