ppc64le mvn -Ptest fails on tip of jruby master branch.

[bugproxy]

== Comment: #0 - Ralph E. Bellofatto <email address hidden> - 2015-03-16 10:18:47 ==
we got a snapshot of the tip of the master jruby branch to test running on ppc64le.

```
[tulgpu002 jruby] $ uname -a
Linux tulgpu002 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:07:11 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

git clone https://github.com/jruby/jruby.git
cd jruby/
mvn compile
mvn test

mvn -Ptest
```
When we ran "mvn -Ptest" as suggested in the BUILDING.md file we get the following error summary:

```
Test results :

Failed tests:
  TestRuby.testPrintErrorShouldPrintErrorMessageAndStacktraceWhenBacktraceIsPresent:169 expected:<[]Line 1: A message (N...> but was:<[io/console on JRuby shells out to stty for most operations
]Line 1: A message (N...>

Tests run: 362, Failures: 1, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JRuby ............................................. SUCCESS [0.643s]
[INFO] JRuby Core ........................................ FAILURE [4:12.958s]
[INFO] JRuby Truffle ..................................... SKIPPED
[INFO] JRuby Lib Setup ................................... SKIPPED
[INFO] JRuby Integration Tests ........................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4:13.960s
[INFO] Finished at: Sun Mar 15 18:54:50 EDT 2015
[INFO] Final Memory: 18M/316M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.15:test (default-test) on project jruby-core: There are test failures.

```

the complete output here:
https://github.com/jruby/jruby/issues/2706

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1434483/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Matthias Klose (doko)]

please recheck with jruby in wily.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-01-26 10:57 EDT-------
No activity in over a year. Closing...