-
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
Windows test results #2487
Comments
We can ignore any tests that failed because the generator input was missing: (output csv, etc), the error looks like this:
Plugin test suites affected by this:
|
one more test failing in the S3 output look related to the generator input. |
@ph can you link to the issue here? |
I proposed a fix for encoding issues in #2507 |
We will need to merge #2507 or find a better fix for windows and rerun the tests with the latest changes. |
Second run of test in https://gist.github.com/ph/1d83c833d89b7c1de9b4 |
My latest results with the bundler-move branch: Using the following as "rake test:plugins2": task "plugins" do
gem_root = File.expand_path('./vendor/bundle/jruby/1.9/')
pattern = File.join(*"gems/logstash-*/spec/{input,filter,codec,output}s/*_spec.rb".split("/"))
sh "#{LogStash::Environment::LOGSTASH_HOME}/bin/logstash rspec --format documentation --order rand #{gem_root} -P '#{pattern}'"
end rake test:plugins => 30 failures |
Closing this since all the related tickets were closed, will open a new one if needed. |
@ph and I are working on fixing logstash bugs on Windows in the
wip/bundler-move
branch (Confusingly name, I know. It's a mix of work in there)I had to disable some plugins because they were causing rspec to crash (not a test failure, rspec would raise exception and abort execution)
The full test output is here: https://gist.github.com/jordansissel/622db419dc1b284794bd
I will file bugs on individual repos as a result, but this ticket tracks the study.
The text was updated successfully, but these errors were encountered: