Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Logstash tests #243

Closed
smithwil opened this issue Feb 7, 2018 · 2 comments
Closed

Add Logstash tests #243

smithwil opened this issue Feb 7, 2018 · 2 comments
Labels
enhancement type:external 3rd party application tests (invoked by the make target 'external')
Milestone

Comments

@smithwil
Copy link

smithwil commented Feb 7, 2018

This request comes from a Java support case, where a developer was getting unexpected errors running Logstash, on Java 8 and the critical part was the platform: Power9 Linux PPCLE. The errors did not happen on Power8.

I don't know when AdoptOpenJDK will get Power9 hardware to test on, but maybe that doesn't matter. Perhaps any test material set up here can be reused by whatever project does get Power9 test hardware.

The errors below came from jruby (running Logstash). The LoadError happened once and the SyntaxError was reported at many points in the jruby script:

LoadError: library 'jruby' could not be loaded: java.lang.NullPointerException

SyntaxError: class/module name must be CONSTANT

Here are the details I could get, of the test set up that found
errors.


  1. download the application from https://artifacts.elastic.co/downloads/logstash/logstash-5.4.2.tar.gz
  2. extract the jruby application
  3. export JAVA_HOME environment
  4. create a simple configuration file named index.conf in the folder logstash-5.4.2 with below content

input {
beats {
port => "5045"
congestion_threshold => 60
}
}

filter {
}

output {

}

  1. start the application with command line:

bin/logstash -f index.conf

then you will see the exception and programme terminated. [Only Power9 platform only].


Reference PMR 02048,001,866 from Zhan Wei Wang

@smlambert smlambert added the type:external 3rd party application tests (invoked by the make target 'external') label Mar 28, 2018
@smlambert
Copy link
Contributor

Plan to address this issue:
thirdparty_containers/startup directory for a set of tests that just starts up applications (doesn't run a suite of tests), as a quick sniff. These tests can/should be run on actual machines, vs in Docker containers if needed.

@smlambert
Copy link
Contributor

Closing this issue (now added to the list in #172).

@karianna karianna added this to the December 2020 milestone Dec 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement type:external 3rd party application tests (invoked by the make target 'external')
Projects
None yet
Development

No branches or pull requests

3 participants