JRuby: tests fail on output assertions about warnings emitted by syslog
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 55
- Forks
- 33
- Avg merge
- 7d 3h
- Merged PRs (30d)
- 1
Description
Tests about output currently fail on JRuby due to this warning being output (and we assert on "", so this fails).
Source locally installed gems is ignoring #<Bundler::StubSpecification name=syslog version=0.4.0 platform=ruby> because it is missing extensions
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by running the output tests under JRuby and locating the assertions expecting an empty string. Use the missing syslog extension warning as the reproduction signal, review PR #107 for context, and consider the work complete when those assertions pass without unintended warning output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100