I added variable WHOAMI=/usr/ucb/whoami to job config but still "java.io.IOException: Cannot run program "whoami": error=2, No such file or directory"
https://builds.apache.org/job/Hama-Nightly/ws/trunk/core/target/surefire-reports/org.apache.hama.bsp.TestLocalRunner.txt By the way, How can I log in to 192.87.106.251 to fix/manage hama-* jobs? 2011/12/16 Thomas Jungblut <thomas.jungb...@googlemail.com>: > I believe that the return of different linuxs' are different. > > 2011/12/16 Edward J. Yoon <edwardy...@apache.org> > >> This nightly build runs on solaris. Maybe I can set environment variables >> to fix this problem. >> >> Sent from my iPhone >> >> On 2011. 12. 16., at 오후 3:32, Thomas Jungblut < >> thomas.jungb...@googlemail.com> wrote: >> >> >> >> >> Test set: org.apache.hama.bsp.TestLocalRunner >> >> >> >> >> ------------------------------------------------------------------------------- >> >> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.008 >> sec >> >> <<< FAILURE! >> >> testOutputJob(org.apache.hama.bsp.TestLocalRunner) Time elapsed: 0.003 >> >> sec <<< ERROR! >> >> org.apache.hadoop.util.Shell$ExitCodeException: id: >> >> thomas-desktopthomas.jungblut: No such user >> >> at org.apache.hadoop.util.Shell.runCommand(Shell.java:195) >> >> at org.apache.hadoop.util.Shell.run(Shell.java:134) >> >> at >> >> >> org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:286) >> > >> > >> > I can reproduce this issue in windows, but not in linux. >> > When I go to the cygwin shell, everything is correct. >> > >> > $ whoami >> >> thomas.jungblut >> >> thomas.jungblut@thomas-desktop ~ >> >> $ bash -c id -Gn thomas.jungblut >> >> uid=1001(thomas.jungblut) gid=513(None) groups=513(None),0(root) >> > >> > >> > On my ubuntu box the tests execute well. >> > What do you think? >> > >> > 2011/12/16 Apache Jenkins Server <jenk...@builds.apache.org> >> > >> >> See <https://builds.apache.org/job/Hama-Nightly/388/> >> >> >> >> ------------------------------------------ >> >> [...truncated 490 lines...] >> >> 11/12/15 23:29:14 INFO ipc.Server: IPC Server handler 8 on 50984: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping server on 50983 >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 0 on 50983: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping IPC Server listener on 50983 >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 5 on 50983: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 8 on 50983: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 9 on 50983: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 7 on 50983: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 6 on 50983: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping server on 50984 >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 2 on 50983: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 0 on 50984: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 3 on 50984: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 2 on 50984: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 7 on 50984: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 8 on 50984: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping IPC Server Responder >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 3 on 50983: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 4 on 50983: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 1 on 50983: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 9 on 50984: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 5 on 50984: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 6 on 50984: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 4 on 50984: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping IPC Server listener on 50984 >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping IPC Server Responder >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 1 on 50984: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO metrics.RpcMetrics: Initializing RPC Metrics with >> >> hostName=0, port=50989 >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server Responder: starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 1 on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 3 on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 5 on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 7 on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 9 on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 8 on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 6 on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 4 on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 2 on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 0 on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server listener on 50989: >> starting >> >> >> >> 11/12/15 23:29:15 INFO metrics.RpcMetrics: Initializing RPC Metrics with >> >> hostName=0, port=50990 >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server Responder: starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server listener on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 1 on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 3 on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 4 on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 6 on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 8 on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 9 on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 0 on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 7 on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 5 on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 2 on 50990: >> starting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping server on 50989 >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 1 on 50989: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping IPC Server listener on 50989 >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 7 on 50989: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 8 on 50989: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping server on 50990 >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 2 on 50989: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 1 on 50990: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 7 on 50990: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 8 on 50990: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping IPC Server Responder >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 6 on 50989: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 3 on 50989: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 9 on 50990: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 6 on 50990: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 5 on 50990: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 4 on 50990: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping IPC Server Responder >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 3 on 50990: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: Stopping IPC Server listener on 50990 >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 2 on 50990: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 0 on 50990: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 5 on 50989: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 0 on 50989: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 9 on 50989: >> exiting >> >> >> >> 11/12/15 23:29:15 INFO ipc.Server: IPC Server handler 4 on 50989: >> exiting >> >> >> >> 11/12/15 23:29:16 INFO ipc.Client: Retrying connect to server: / >> >> 127.0.0.1:10. Already tried 0 time(s). >> >> >> >> 11/12/15 23:29:17 INFO ipc.Client: Retrying connect to server: / >> >> 127.0.0.1:10. Already tried 1 time(s). >> >> >> >> 11/12/15 23:29:18 INFO ipc.Client: Retrying connect to server: / >> >> 127.0.0.1:10. Already tried 2 time(s). >> >> >> >> 11/12/15 23:29:19 INFO ipc.Client: Retrying connect to server: / >> >> 127.0.0.1:10. Already tried 3 time(s). >> >> >> >> 11/12/15 23:29:20 INFO ipc.Client: Retrying connect to server: / >> >> 127.0.0.1:10. Already tried 4 time(s). >> >> >> >> 11/12/15 23:29:21 INFO ipc.Client: Retrying connect to server: / >> >> 127.0.0.1:10. Already tried 5 time(s). >> >> >> >> 11/12/15 23:29:22 INFO ipc.Client: Retrying connect to server: / >> >> 127.0.0.1:10. Already tried 6 time(s). >> >> >> >> 11/12/15 23:29:23 INFO ipc.Client: Retrying connect to server: / >> >> 127.0.0.1:10. Already tried 7 time(s). >> >> >> >> 11/12/15 23:29:24 INFO ipc.Client: Retrying connect to server: / >> >> 127.0.0.1:10. Already tried 8 time(s). >> >> >> >> 11/12/15 23:29:25 INFO ipc.Client: Retrying connect to server: / >> >> 127.0.0.1:10. Already tried 9 time(s). >> >> >> >> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 >> sec >> >> Running org.apache.hama.zookeeper.TestZKTools >> >> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec >> >> Running org.apache.hama.ipc.TestRPC >> >> 11/12/15 23:29:27 INFO metrics.RpcMetrics: Initializing RPC Metrics with >> >> hostName=TestRPC$TestImpl, port=1234 >> >> >> >> 11/12/15 23:29:27 INFO ipc.Server: IPC Server Responder: starting >> >> >> >> 11/12/15 23:29:27 INFO ipc.Server: IPC Server listener on 1234: starting >> >> >> >> 11/12/15 23:29:27 INFO ipc.Server: IPC Server handler 0 on 1234: >> starting >> >> >> >> 11/12/15 23:29:27 INFO ipc.Server: IPC Server handler 0 on 1234, call >> >> error() from 192.87.106.251:51035: error: java.io.IOException: bobo >> >> java.io.IOException: bobo >> >> at org.apache.hama.ipc.TestRPC$TestImpl.error(TestRPC.java:102) >> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> >> at >> >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> >> at >> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> >> at java.lang.reflect.Method.invoke(Method.java:597) >> >> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:508) >> >> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:959) >> >> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:955) >> >> at java.security.AccessController.doPrivileged(Native Method) >> >> at javax.security.auth.Subject.doAs(Subject.java:396) >> >> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:953) >> >> >> >> 11/12/15 23:29:27 INFO ipc.Server: Stopping server on 1234 >> >> >> >> 11/12/15 23:29:27 INFO ipc.Server: IPC Server handler 0 on 1234: exiting >> >> >> >> 11/12/15 23:29:27 INFO ipc.Server: Stopping IPC Server listener on 1234 >> >> >> >> 11/12/15 23:29:27 INFO ipc.Server: Stopping IPC Server Responder >> >> >> >> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec >> >> >> >> Results : >> >> >> >> Tests in error: >> >> >> >> Tests run: 36, Failures: 0, Errors: 3, Skipped: 0 >> >> >> >> [INFO] >> >> ------------------------------------------------------------------------ >> >> [INFO] Reactor Summary: >> >> [INFO] >> >> [INFO] Apache Hama parent POM ............................ SUCCESS >> [3.910s] >> >> [INFO] Apache Hama Core .................................. FAILURE >> >> [51.342s] >> >> [INFO] Apache Hama Graph Package ......................... SKIPPED >> >> [INFO] Apache Hama Examples .............................. SKIPPED >> >> [INFO] Apache Hama YARN .................................. SKIPPED >> >> [INFO] >> >> ------------------------------------------------------------------------ >> >> [INFO] BUILD FAILURE >> >> [INFO] >> >> ------------------------------------------------------------------------ >> >> [INFO] Total time: 56.443s >> >> [INFO] Finished at: Thu Dec 15 23:29:28 GMT+00:00 2011 >> >> [INFO] Final Memory: 21M/265M >> >> [INFO] >> >> ------------------------------------------------------------------------ >> >> [ERROR] Failed to execute goal >> >> org.apache.maven.plugins:maven-surefire-plugin:2.6:test (default-test) >> on >> >> project hama-core: There are test failures. >> >> [ERROR] >> >> [ERROR] Please refer to >> >> >> /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/Hama-Nightly/trunk/core/target/surefire-reports >> >> for the individual test results. >> >> [ERROR] -> [Help 1] >> >> [ERROR] >> >> [ERROR] To see the full stack trace of the errors, re-run Maven with the >> >> -e switch. >> >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> >> [ERROR] >> >> [ERROR] For more information about the errors and possible solutions, >> >> please read the following articles: >> >> [ERROR] [Help 1] >> >> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException >> >> [ERROR] >> >> [ERROR] After correcting the problems, you can resume the build with the >> >> command >> >> [ERROR] mvn <goals> -rf :hama-core >> >> Build step 'Invoke top-level Maven targets' marked build as failure >> >> >> >> >> > >> > >> > -- >> > Thomas Jungblut >> > Berlin <thomas.jungb...@gmail.com> >> > > > > -- > Thomas Jungblut > Berlin <thomas.jungb...@gmail.com> -- Best Regards, Edward J. Yoon @eddieyoon
