build output is impossible to read due to nested json dumps

Bug #1801388 reported by Sorin Sbarnea
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Low
Unassigned

Bug Description

Build output should be readable by humans and JSON and especially nested JSON output is clearly not making the output readable.

While there is nothing wrong on saving output as JSON as this is easily parsed by computers we should avoid printing JSON output on console, or at least not if is more than like 1000 chars.

Newlines should appear as real newlines and not being converted to "\n"

We should avoid extra quoting on output lines (stdout/stderr)

Example: http://logs.openstack.org/91/610491/26/check/tripleo-ci-fedora-28-standalone/d1f01e3/logs/undercloud/home/zuul/standalone_deploy.log.txt.gz#_2018-10-31_21_01_59

Revision history for this message
Juan Antonio Osorio Robles (juan-osorio-robles) wrote :

Is this still an issue?

Changed in tripleo:
status: New → Triaged
importance: Undecided → Low
milestone: none → stein-3
Changed in tripleo:
milestone: stein-3 → train-1
Changed in tripleo:
milestone: train-1 → train-2
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
milestone: train-3 → ussuri-1
Changed in tripleo:
milestone: ussuri-1 → ussuri-2
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-2 → ussuri-3
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-3 → ussuri-rc3
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-rc3 → victoria-1
Changed in tripleo:
milestone: victoria-1 → victoria-3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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