aloof-angle-91616
01/22/2019, 8:24 AM> ./pants --compile-zinc-workunit-output="+{'stdout': {'output.txt': ['COMPILE']}}" test ::
and the stdout
corresponds to workunit.output('stdout')
, but we can extend that to other output types to allow for non-hierarchical output labelling for an asynchronous v2 UI!red-balloon-89377
01/22/2019, 12:00 PMaloof-angle-91616
01/23/2019, 9:08 AMWorkUnitMessageType
i proposed in comments in the linked issue> ./pants --compile-zinc-workunit-output="+{'MESSAGE': {'message-output.txt': ['COMPILE']}, 'stdout': {'process-output.txt': ['COMPILE']}, 'stderr': {'error-log.txt': ['COMPILE']}, 'ERROR': {'error-log.txt': ['COMPILE']}}" test ::
MESSAGE
vs ERROR
(`WorkUnitMessageType`s) can be an extended form of log message types like debug/warn/info/exceptionred-balloon-89377
01/23/2019, 10:13 AMaloof-angle-91616
01/23/2019, 6:32 PM