Mark tool installation as failed when stderr contains traceback

[mvdbeek]

Apparently this is not happening right now (and is the source for some confusion on http://dev.list.galaxyproject.org/ERROR-PIP-is-not-a-legl-parament-of-an-Ansible-Play-td4669045.html).
I guess we could check for the exit code / or cleanup messages that go to stderr?

[afgane]

In principle I don't see why not. There's a lot of log content in the thread you mention - did you find a portion where it indicates that checking the exit code would fix the problem?
(btw, I'm really still not sure where the problem is stemming from the in that whole exchange)

[mvdbeek]

he's getting a traceback due to the absence of logging.capture() in python-2.6 (you can see that in ansible.log), but it looks like ansible reported success on the tool installation. So a better error / exit code detection wouldn't solve the problem, but it would be easier to see that somewthing went wrong. I will take a look at this.