-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
rubyTests failing in 8.12.2 logstash #16025
Comments
@andsel , Could you help here.. Thanks in Advance! |
Sorry @nikhithakarennagari but I wasn't able to reproduce locally:
Did you try |
@andsel , May I know if you are running the OSS version of logstash? Because I see that I am running org.logstash.RSpecTests > rspecTests[core tests] FAILED and for you it is org.logstash.xpack.test.RSpecTests > rspecTests PASSED |
I checkout the sources, the tests runs the full source base, it doesn't bother if OSS or not. |
@andsel , Thank you very much for checking on it. Let me tell you what I tried. After the last step, I am facing the errors as indicated above. One thing I have observed is, If I reverted these changes in this commit #15348 , the rubyTests passed successfully. Let me know if I have to change any settings/configuration in the repo. Once again Thank you for your time and efforts to check this. |
When running with logstash/x-pack/lib/geoip_database_management/extension.rb Lines 11 to 17 in ee9dfd3
Therefore the config variable(s) remains "unknown" for
and since the config variable was not registered it will print error
If running Error happens also if just running logstash
and it seems still to be happening in main. |
@nikhithakarennagari His analysis is correct, the point is that |
Repro line:
./gradlew rubyTests --stacktrace
Below errors are seen during execution of above command:
org.logstash.RSpecTests > rspecTests[core tests] FAILED java.lang.AssertionError: RSpec test suite
core testssaw at least one failure. at org.junit.Assert.fail(Assert.java:88) at org.logstash.RSpecTests.rspecTests(RSpecTests.java:72
Below are some of the failures:
rspec ./logstash-core/spec/logstash/api/modules/root_spec.rb:26 # LogStash::Api::Modules::Root should respond to root resource rspec ./logstash-core/spec/logstash/api/modules/root_spec.rb:23 # LogStash::Api::Modules::Root should return a 404 to unknown request rspec './logstash-core/spec/logstash/api/modules/node_stats_spec.rb[1:1]' # LogStash::Api::Modules::NodeStats should return a 404 to unknown request rspec './logstash-core/spec/logstash/api/modules/node_stats_spec.rb[1:2:1]' # LogStash::Api::Modules::NodeStats GET / should respond OK rspec './logstash-core/spec/logstash/api/modules/node_stats_spec.rb[1:2:3]' # LogStash::Api::Modules::NodeStats GET / should set 'jvm.uptime_in_millis' at '/' to be a 'Numeric' rspec './logstash-core/spec/logstash/api/modules/node_stats_spec.rb[1:2:4]' # LogStash::Api::Modules::NodeStats GET / should set 'jvm.threads.count' at '/' to be a 'Numeric' rspec './logstash-core/spec/logstash/api/modules/node_stats_spec.rb[1:2:5]' # LogStash::Api::Modules::NodeStats GET / should set 'jvm.threads.peak_count' at '/' to be a 'Numeric' rspec './logstash-core/spec/logstash/api/modules/node_stats_spec.rb[1:2:6]' # LogStash::Api::Modules::NodeStats GET / should set 'jvm.gc.collectors.young.collection_count' at '/' to be a 'Numeric' rspec './logstash-core/spec/logstash/api/modules/node_stats_spec.rb[1:2:7]' # LogStash::Api::Modules::NodeStats GET / should set 'jvm.gc.collectors.young.collection_time_in_millis' at '/' to be a 'Numeric' rspec './logstash-core/spec/logstash/api/modules/node_stats_spec.rb[1:2:8]' # LogStash::Api::Modules::NodeStats GET / should set 'jvm.gc.collectors.old.collection_count' at '/' to be a 'Numeric'
Most of the failures are like below, with Argument Errors as:
` LogStash::Api::Modules::Logging#logging when setting a logger's log level should throw error when key logger is invalid
Failure/Error: status = RSpec::Core::Runner.run(ARGV.empty? ? ($JUNIT_ARGV || ["spec"]) : ARGV).to_i
`
Reproduces locally?: yes
Applicable branches: 8.12.0 onwards
Failure history:
Fails from 8.12.0
The text was updated successfully, but these errors were encountered: