Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some runPostCrab cleaning #73

Open
OlivierBondu opened this issue Feb 26, 2016 · 0 comments
Open

Some runPostCrab cleaning #73

OlivierBondu opened this issue Feb 26, 2016 · 0 comments

Comments

@OlivierBondu
Copy link
Member

It seems the specification of the crabCommand API changed (or maybe they just improved the documentation 😄) and we don't need the dirty workaround around getoutput and crab report to silence the terminal from displaying the result

Namely, from their example:

    # If you want crabCommand to be quiet:
    #from CRABClient.UserUtilities import setConsoleLogLevel
    #from CRABClient.ClientUtilities import LOGLEVEL_MUTE
    #setConsoleLogLevel(LOGLEVEL_MUTE)
    # With this function you can change the console log level at any time.

    # To retrieve the current crabCommand console log level:
    #from CRABClient.UserUtilities import getConsoleLogLevel
    #crabConsoleLogLevel = getConsoleLogLevel()

    # If you want to retrieve the CRAB loggers:
    #from CRABClient.UserUtilities import getLoggers
    #crabLoggers = getLoggers()

It would avoid the silent crashes of runPostCrab.py that hide in fact crab crashes...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant