6af7101b | 06-Nov-2018 |
Simon Glass <sjg@chromium.org> |
buildman: Show boards with warning with w+
At present we should boards with warnings in the same way as those with errors. This is not ideal. Add a new 'warn' state and show these listed in yellow t
buildman: Show boards with warning with w+
At present we should boards with warnings in the same way as those with errors. This is not ideal. Add a new 'warn' state and show these listed in yellow to match the actual warning lines printing with -e.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
4cf2b221 | 06-Nov-2018 |
Simon Glass <sjg@chromium.org> |
buildman: Rename the good, better, worse variables
At present we don't distinguish between errors and warnings when printing the architecture summary. Rename the variables to better describe their p
buildman: Rename the good, better, worse variables
At present we don't distinguish between errors and warnings when printing the architecture summary. Rename the variables to better describe their purpose.
'Worse' at present means we got an error, so use that as the name.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
2d48333e | 06-Nov-2018 |
Simon Glass <sjg@chromium.org> |
buildman: Detect dtc warnings
At present messages from the device-tree compiler like this:
arch/arm/dts/socfpga_arria10_socdk_sdmmc.dtb: Warning (avoid_unnecessary_addr_size): /clocks: unnec
buildman: Detect dtc warnings
At present messages from the device-tree compiler like this:
arch/arm/dts/socfpga_arria10_socdk_sdmmc.dtb: Warning (avoid_unnecessary_addr_size): /clocks: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
are detected as errors since they don't match the gcc warning regex. Add a new one for dtc to fix this.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
a9f7f1c5 | 05-Nov-2018 |
Peng Fan <peng.fan@nxp.com> |
tools: imx8image: fix coverity CID 184233
Fix: CID 184233: (NEGATIVE_RETURNS) Using variable "container" as an index to array "imx_header.fhdr".
Reported-by: Coverity Signed-off-by: Peng Fan <pe
tools: imx8image: fix coverity CID 184233
Fix: CID 184233: (NEGATIVE_RETURNS) Using variable "container" as an index to array "imx_header.fhdr".
Reported-by: Coverity Signed-off-by: Peng Fan <peng.fan@nxp.com>
show more ...
|
df439e93 | 05-Nov-2018 |
Peng Fan <peng.fan@nxp.com> |
tools: imx8image: fix coverity CID 184234
Fix: CID 184234: (TAINTED_SCALAR) Using tainted variable "header.num_images - 1" as an index into an array "header.img".
Reported-by: Coverity Signed-of
tools: imx8image: fix coverity CID 184234
Fix: CID 184234: (TAINTED_SCALAR) Using tainted variable "header.num_images - 1" as an index into an array "header.img".
Reported-by: Coverity Signed-off-by: Peng Fan <peng.fan@nxp.com>
show more ...
|
11ae93ee | 01-Oct-2018 |
Simon Glass <sjg@chromium.org> |
binman: Run tests concurrently
At present the tests run one after the other using a single CPU. This is not very efficient. Bring in the concurrencytest module and run the tests concurrently, using
binman: Run tests concurrently
At present the tests run one after the other using a single CPU. This is not very efficient. Bring in the concurrencytest module and run the tests concurrently, using one process for each CPU by default. A -P option allows this to be overridden, which is necessary for code-coverage to function correctly.
This requires fixing a few tests which are currently not fully independent.
At some point we might consider doing this across all pytests in U-Boot. There is a pytest version that supports specifying the number of processes to use, but it did not work for me.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
008b0300 | 01-Oct-2018 |
Simon Glass <sjg@chromium.org> |
patman: Don't clear progress in tout unless it was used
At present calling Uninit() always called ClearProgress() which outputs a \r character as well as spaces to remove any progress information on
patman: Don't clear progress in tout unless it was used
At present calling Uninit() always called ClearProgress() which outputs a \r character as well as spaces to remove any progress information on the line. This can mess up the normal output of binman and other tools. Fix this by outputing this only when progress information has actually been previous written.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
4b4bc06e | 01-Oct-2018 |
Simon Glass <sjg@chromium.org> |
buildman: dtoc: Suppress unwanted output from test
There are a few test cases which print output. Suppress this so that tests can run silently in the normal case.
Signed-off-by: Simon Glass <sjg@ch
buildman: dtoc: Suppress unwanted output from test
There are a few test cases which print output. Suppress this so that tests can run silently in the normal case.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
86af511d | 01-Oct-2018 |
Simon Glass <sjg@chromium.org> |
binman: Separate out testSplBssPad()
At present this test runs binman twice, which means that the temporary files from the first run do not get cleaned up. Split this into two tests to fix this prob
binman: Separate out testSplBssPad()
At present this test runs binman twice, which means that the temporary files from the first run do not get cleaned up. Split this into two tests to fix this problem.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|