Enhancement #1842

Make errors of failing sub-commands visible

Added by J. Wienke almost 9 years ago. Updated almost 9 years ago.

Status:ResolvedStart date:04/16/2014
Priority:NormalDue date:
Assignee:J. Moringen% Done:

100%

Category:User Interface
Target version:0.2

Description

In case one of the sub-commands like svn fails, please also show the reason for the failure, which probably means the original error output. So far I can only see things like

SIMPLE-ERROR:
  Command (JENKINS.ANALYSIS::SVN :NON-INTERACTIVE :QUIET "co" "https://projects.cor-lab.org/svn/flexirob/modules" #P"/tmp/project.aAXP0k/modules/") failed in directory #P"/tmp/project.aAXP0k/" 

without any reason for the failure.

Associated revisions

Revision fc18a038
Added by J. Moringen almost 9 years ago

Report errors from subversion, git subprocesses in src/analysis/*.lisp

fixes #1842

  • src/analysis/util.lisp (header): updated copyright
    (run): new function; execute command capturing its standard and error
    output
  • src/analysis/subversion.lisp (%svn-and-global-options): use friendlier
    specification; at least for UNIX lovers
    (%run-svn): new function; helper function for executing subversion
    commands
    (analyze uri eql :svn): use `run' and `%run-svn'
  • src/analysis/git.lisp (%run-git): new function; helper function for
    running git commands
    (analyze uri eql :git): use `%run-git'; friendlier specifications
    (analyze pathname eql :git/authors): friendlier specifications

History

#1 Updated by J. Moringen almost 9 years ago

  • Status changed from New to In Progress

#2 Updated by J. Moringen almost 9 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

#3 Updated by J. Moringen almost 9 years ago

  • Target version set to 0.2

Also available in: Atom PDF