Make Simfactory tell you what it's doing

Issue #1517 closed
Steven R. Brandt created an issue

Sometimes I'd like to know what shell commands Simfactory is running. This patch causes Simfactory to print out messages of the form "COMMAND: ...." when the --verbose flag is set.


Comments (21)

  1. Roland Haas
    • changed status to open
    • removed comment

    The commit ended up in the ET_2012_11 branch.

    There are also uses of os.popen. The attached patch also provides output for them.

  2. Roland Haas
    • changed status to open
    • removed comment

    ok to apply (both :-) )? Should we revert rev 2250 (there is nothing wrong with the patch after all)?

  3. Steven R. Brandt reporter
    • removed comment

    The attached patch looks pretty good to me. I notice that a few of these popens are followed by "Executing uberftp command" or something similar. These seem redundant now.

    It also might be nice to distinguish between an os.system() and an os.popen(). Maybe do this with os.popen()?

    print "Executing:",cmd,"|"

  4. Roland Haas
    • removed comment

    Hmm, outputting the same information twice certainly should be avoided. Having lookied at the dprint routine that the uberftp cude uses, I think we are not quite doing the right thing though. Most likely we should use info() or dprint() instead of just print to make sure that the information also appears in the simfactory log file. Currently both info() and dprint() always write to the log file, so to get the behaviour we just implemented (but also writing to the log) we'd need another dprint wrapper eg "verbose_info" (or replicate the verbosity level in the callers).

    Also seems to me as if's dprint code contains a bug in that it does not check for flag == USE_VERBOSE and does not actually implement what the comment just above indicates.

  5. Erik Schnetter
    • removed comment

    I think we should use info for output (and not check for "verbose" when calling it). Having the executed command always in the log file won't hurt.

  6. Ian Hinder
    • changed status to open
    • removed comment

    I think the current situation is that the patch was applied to an old release branch, not the trunk, and there are still issues with the patch as discussed above. The patch would never have been applied to the release branch, so I suggest reverting it.

    I can't quite tell what the remaining issues are from the discussion above. Maybe you could list them here, or fix them? This feature would be very useful to have in simfactory, especially when debugging problems, so we should try to add it.

  7. Steven R. Brandt reporter
    • removed comment

    I've merged the patches and made another small change to prevent redundant output.

  8. Ian Hinder
    • changed status to open
    • removed comment

    I have reverted this commit because it causes the automated build and test to fail completely. See The failure is

    Skeleton Created
    Job directory: "/home/jenkins/workspace/EinsteinToolkit/../simulations/EinsteinToolkit_a639fc5731c04d0ace7e147133c453e5b82ad5bb_1"
    Option --testsuite given
    Executable: "/home/jenkins/workspace/EinsteinToolkit/exe/cactus_sim"
    Option list: "/home/jenkins/workspace/EinsteinToolkit/../simulations/EinsteinToolkit_a639fc5731c04d0ace7e147133c453e5b82ad5bb_1/SIMFACTORY/cfg/OptionList"
    Submit script: "/home/jenkins/workspace/EinsteinToolkit/../simulations/EinsteinToolkit_a639fc5731c04d0ace7e147133c453e5b82ad5bb_1/SIMFACTORY/run/SubmitScript"
    Run script: "/home/jenkins/workspace/EinsteinToolkit/../simulations/EinsteinToolkit_a639fc5731c04d0ace7e147133c453e5b82ad5bb_1/SIMFACTORY/run/RunScript"
    Simulation name: EinsteinToolkit_a639fc5731c04d0ace7e147133c453e5b82ad5bb_1
    Assigned restart id: 0 
    Copying testsuite data
    Traceback (most recent call last):
      File "simfactory/bin/../lib/", line 148, in <module>
      File "simfactory/bin/../lib/", line 144, in main
      File "simfactory/bin/../lib/", line 106, in CommandDispatch
      File "/home/jenkins/workspace/EinsteinToolkit/simfactory/lib/", line 397, in main
      File "/home/jenkins/workspace/EinsteinToolkit/simfactory/lib/", line 376, in CommandDispatch
        exec("command_%s()" % command)
      File "<string>", line 1, in <module>
      File "/home/jenkins/workspace/EinsteinToolkit/simfactory/lib/", line 183, in command_create_run
      File "/home/jenkins/workspace/EinsteinToolkit/simfactory/lib/", line 220, in command_run
      File "/home/jenkins/workspace/EinsteinToolkit/simfactory/lib/", line 956, in userRun
      File "/home/jenkins/workspace/EinsteinToolkit/simfactory/lib/", line 494, in copyTestsuiteData
        rsyncversion = simlib.RsyncVersion(rsyncInfo)
      File "/home/jenkins/workspace/EinsteinToolkit/simfactory/lib/", line 1055, in RsyncVersion
        versionText = ExecuteCommand('%s --version' % rsynccmd, True)
      File "/home/jenkins/workspace/EinsteinToolkit/simfactory/lib/", line 545, in ExecuteCommand
        if (not output) or (global_dict['VERBOSE']):
    KeyError: 'VERBOSE'

    The script which is running when this failure occurs is at and the relevant command is presumably the

    simfactory/bin/sim create-run --testsuite $tests --procs $cores --num-threads $((cores/nprocs)) $simname

    Maybe you can reproduce the failure with a similar command line?

  9. Roland Haas
    • changed status to open
    • removed comment

    Please apply (personal communication: Steve could reproduce the issue and fix it with the new patch).

  10. Log in to comment