Stefan Sperling wrote on Tue, Dec 18, 2012 at 09:54:08 +0100: > On Tue, Dec 18, 2012 at 01:55:55AM +0200, Daniel Shahaf wrote: > > Not sure. For unattended scripts, the only difference between passing > > --non-interactive or not passing it is the error message they get, right? > > > > I mean, if they pass it they will get "Cannot prompt because we aren't > > interactive" (or is it "libsvn_auth has run out of username > > providers"?), and if they don't pass it they will on stderr an "Should > > I accept this SSL certificate?" prompt followed by an "End of file found on > > stdin" error. > > Depends. Sometimes the command just hangs and gives no output. > It may not always get an EOF from whatever file descriptor it is > blocking on. stderr might show the prompt but stderr might not
Why? Shouldn't the automated test have either answered the prompt or closed stdin? > always be visible e.g. if it is being piped back to a controlling So don't discard stderr when you investigate why a build fails. > process which is also blocking, waiting for svn to finish before > it will show the result. > > I've seen this happen in Jenkins builds that run 'svn export' and > adding --non-interactive fixed it.
