Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
UW-Glance
UW-Glance
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Eva Schiffer
  • UW-GlanceUW-Glance
  • Issues
  • #45

Closed
Open
Opened Aug 12, 2020 by Eva Schiffer@evas
  • Report abuse
  • New issue
Report abuse New issue

Glance sometimes terminates with an error code when nothing is wrong when run on the command line with a config file

This came from Mike Walters. I haven't seen this one in my command line tests with a config file, so there may be some subtle issue with how forking is working differently (if I can't find a way to reproduce on my machine I should do some tests on SSEC servers). Mike said:

Glance terminates abnormally, with the message "Aborting". This occurs when I run reportGen on the command line with a configuration file, which is how I normally run Glance. As far as I can tell, Glance generates the report and performs all of the requested operations successfully. The exit status should be 0 for success, but instead it's 134, which indicates failure. This is a bit of a problem because our cluster software tries to rerun failed jobs, so Glance jobs get run over and over. I can create a workaround if necessary, but that will have side effects. Anyway, I tracked the issue back to the os.fork() and os.waitpid() functions in the plot.py module. I'm not very familiar with forking in Python, so I wasn't able to narrow it down more than that.

To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: evas/UW-Glance#45