-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major
-
Affects Version/s: master, 5.0.6
-
Component/s: CLI: pegasus-plan
-
None
as part of PM-1474 when pegasus-plan is invoked with --json option, all the logging of the planner goes to stderr ; while on stdout the contents of the braindump file get dumped as a json object
this --json option is also passed when pegasus-plan is invoked from the python workflow api plan function.
however, it seems in the default case the interleaving of stdout and stderr can be confusing to the users
For example
2024.01.31 15:53:10.344 CST: -----------------------------------------------------------------------
2024.01.31 15:53:11.310 CST: Database version: '5.0.6dev' (sqlite:////home/rynge/.pegasus/workflow.db)
2024.01.31 15:53:12.336 CST: Pegasus database was successfully created.
2024.01.31 15:53:12.342 CST: Database version: '5.0.6dev' (sqlite:////home/rynge/workflows/runs/rynge/pegasus/wordfreq-workflow/run0002/wordfreq-workflow-0.replicas.db)
2024.01.31 15:53:12.382 CST: Output replica catalog set to jdbc:sqlite:/home/rynge/workflows/runs/rynge/pegasus/wordfreq-workflow/run0002/wordfreq-workflow-0.replicas.db
[WARNING] Submitting to condor wordfreq-workflow-0.dag.condor.sub
2024.01.31 15:53:13.315 CST: Time taken to execute is 3.662 seconds
Your workflow has been started and is running in the base directory:
/home/rynge/workflows/runs/rynge/pegasus/wordfreq-workflow/run0002
-
-
- To monitor the workflow you can run ***
-
pegasus-status -l /home/rynge/workflows/runs/rynge/pegasus/wordfreq-workflow/run0002