Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

QuickBuild

Log output new lines - not in seperated prints ? #2210

#1
nmanos ·
Hi Robin,
Is it possible to change the log output to print command/script output in a single section, instead of seperating each new line of the command output into Debug/Info line ?

For example, this Step Log:

13:24:15,267 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO - Running step...
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO - Started: Wed, 06 Mar 2013 11:24:15 +0000
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO -
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO - UnitTest checker...
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO - Error: Failed because of 'TEST_EXECUTION_MODE' attribute not defined in following unit tests
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO -
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO - --DisplayTestGroup
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO - |-- Osd2Palette8Bit
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO -
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO - Found 1 illegal test(s):
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO - UnitTest Checker ended
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO -
13:24:19,859 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO - Ended: Wed, 06 Mar 2013 11:24:19 +0000



Could have been more readble if it was printed this way:

13:24:15,267 [master>Testing stage>EQS_UnitTest?TestParameters=15s+PLATFORM(CAMMINI_EXT)+SENSOR(MT9J001)+TCF_TAB(1of2)&TestType=UnitTest>Create Test Attribute XML file@ZML-DSC-QA48:8811] INFO - Running step...
Started: Wed, 06 Mar 2013 11:24:15 +0000

UnitTest checker...
Error: Failed because of 'TEST_EXECUTION_MODE' attribute not defined in following unit tests

--DisplayTestGroup
|-- Osd2Palette8Bit

Found 1 illegal test(s):
UnitTest Checker ended

Ended: Wed, 06 Mar 2013 11:24:19 +0000


Thanks!
Noam.
  • replies 5
  • views 1486
  • stars 0
#2
robinshen ADMIN ·
The problem is that QB simply collects the output line by line but does not know its meaning.
#3
nmanos ·
I see, and is it possible to set the log output, not to print the step name and/or timestamp before each new line ?
This could help to read process/script output.

Thanks,
Noam.
#4
robinshen ADMIN ·
Yes, there is an option to turn off this info in QB5.
#5
nmanos ·
That's a great enhancement in QB5!
The "show step" info is very useful once viewing the whole build log, but for a single step it could be great to see hostname in the step log headline (even without "show steps"), just as it is shown in the step status page, e.g.:
Publish CL content | successful | 19 seconds | ZML-DSC-QA74:8811
{Step Log output}


Thanks,
Noam.
#6
robinshen ADMIN ·
Just showing hostname is not enough even for a single step, as a single step might also contain child steps. So we still suggest to go with the "show steps" option to check host info.
Log in to reply