|
|
-
Re: [jira] [Commented] (FLUME-1943) ExecSource tests failing on JenkinsBrock Noland 2013-03-12, 02:50
Yeah I wonder if {0..5} isn't expanding. We can put that at the tip of the build script to see what the output is.
-- Brock Noland Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Monday, March 11, 2013 at 9:41 PM, Roshan Naik (JIRA) wrote: > > [ https://issues.apache.org/jira/browse/FLUME-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599627#comment-13599627 ] > > Roshan Naik commented on FLUME-1943: > ------------------------------------ > > unable to reproduce locally.. tried both on Linux and Mac. Suspecting something specific to the Jenkins system. Wondering if there is anything about the Jenkins system that is preventing execution of /bin/sh properly. > > Hari, Is it possible to get an output for the following command on the Jenkins system ? > /bin/sh --version > > ExecSource tests failing on Jenkins > > ----------------------------------- > > > > Key: FLUME-1943 > > URL: https://issues.apache.org/jira/browse/FLUME-1943 > > Project: Flume > > Issue Type: Bug > > Reporter: Hari Shreedharan > > Assignee: Roshan Naik > > > > See https://builds.apache.org/job/flume-trunk/371/ for failed tests. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira > > |