pegasus-analyzer errors are ugly

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      I think we should spend some time making pegasus-analyzer more user friendly. For example, if you run pegasus-analyzer in the wrong directory, you get:

      $ pegasus-analyzer
      Traceback (most recent call last):
      File "/usr/bin/pegasus-analyzer", line 1529, in <module>
      analyze_db(options.config_properties)
      File "/usr/bin/pegasus-analyzer", line 990, in analyze_db
      output_db_url = connection.url_by_submitdir(input_dir, connection.DBType.WORKFLOW, config_properties, top_dir)
      File "/usr/lib64/python2.6/site-packages/Pegasus/db/connection.py", line 94, in url_by_submitdir
      raise ConnectionError("Unable to process braindump.txt in %s" % (submit_dir))
      Pegasus.db.connection.ConnectionError: Unable to process braindump.txt in /home/rynge/pegasus/gordon-test

      It would be nice if you get a real error, with suggestions on how to fix it, instead of a trace. There are probably more errors like this we could improve.

            Assignee:
            Rafael Ferreira Da Silva [X] (Inactive)
            Reporter:
            Mats Rynge
            Archiver:
            Rajiv Mayani

              Created:
              Updated:
              Resolved:
              Archived: