Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S Slicer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 40
    • Merge requests 40
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Sam Horvath
  • Slicer
  • Merge requests
  • !1018

BUG: Report error if --python-script associated with non-existent file

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Sam Horvath requested to merge github/fork/jcfr/report-error-with-unexistent-python-script into master Sep 07, 2018
  • Overview 2
  • Commits 1
  • Changes 2

Created by: jcfr

This commit ensures an exception is raised when the python script does not exist. When associated with the --exit-after-startup option, a non-zero status code is now returned when Slicer exit.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/jcfr/report-error-with-unexistent-python-script