slack-ruby / slack-ruby/slack-ruby-client
JRuby build fails on stdout output
Open
Nobody has claimed this yet.
chore
confirmed bug
- Dominant language
- Ruby
- Stars
- 1.3k
- Forks
- 222
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 3
Description
https://travis-ci.org/slack-ruby/slack-ruby-client/jobs/426123541
Looks like some trivial failures.
expected: "error: not_authed\n"
got: "Picked up _JAVA_OPTIONS: -Xmx2048m -Xms512m\nerror: not_authed\n"
Contributor guide
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
Start with the linked Travis CI job and inspect the JRuby build output around the failing stdout assertion. Determine where the _JAVA_OPTIONS line is introduced and verify the build passes with the expected error: not_authed\n output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, ruby
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100