Mojo: Continuous Delivery for Juju

juju-deployer output should be unbuffered

Bug #1423964 reported by Tom Haddon on 2015-02-20

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	Mojo: Continuous Delivery for Juju	Confirmed	Medium	Unassigned

Currently we do this in mojo/phase.py:

cmd = ['python', deployer, '-c', configs[1], "-l"]

If we change this to this we'd get unbuffered output, which would be helpful when you're sending the output of a mojo run to a log file:

cmd = ['python', '-u', deployer, '-c', configs[1], "-l"]

Tags:

Revision history for this message

Tom Haddon (mthaddon) wrote on 2015-02-20:

Actually, seems it's line 369:

cmd = ('python', deployer)

Which should be:

cmd = ('python', '-u', deployer)

Revision history for this message

Tom Haddon (mthaddon) wrote on 2015-02-23:

Hmm, tried that and unfortunately it didn't work. Will need to look into the bicommand function in mojo/utils.py

Tom Haddon (mthaddon) on 2015-02-23

Changed in mojo:
importance:	Undecided → Low

Revision history for this message

Paul Collins (pjdc) wrote on 2015-04-08:

It's a slightly outsized hammer, but setting PYTHONUNBUFFERED in mojo's environment filters down and affects its juju-deployer invocations suitably.

Tom Haddon (mthaddon) on 2015-10-13

Tom Haddon (mthaddon) on 2015-10-21

tags:

added: papercut

Revision history for this message

David Ames (thedac) wrote on 2016-01-26:

The problem seems to be related to a python script with logging calling another python script with logging.

Juju deployer output is buffered and is flushed at the end of the run like the following example:

When an error occurs this can be hidden by the flushed output.

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.