filter_csv.txt 1.4 KB

12345678910111213141516171819202122232425262728293031323334353637
  1. There is a new log filter to generate a comma-separated-values (.csv) file
  2. listing all the errors, warnings, remarks etc. For example,
  3. sbs --filters=csv -f name
  4. will produce an output file "name.csv" in the current directory.
  5. Text in the Raptor logs is classified as Error, Critical, Warning or Remark
  6. using the list of regular expressions in the file,
  7. SBS_HOME/lib/config/logfile_regex.csv
  8. but this can be overriden by placing a file of the same name in the kit in
  9. its EPOCROOT/epoc32/sbs_config folder. This is exactly the same mechanism
  10. used by the HTML filter.
  11. The output .csv file can be sorted and then compared (using tools like diff
  12. or a spreadsheet viewer) to the results of a previous build.
  13. The format of the .csv file is: type,component,configuration,text
  14. where,
  15. * type is one of (ok, error, critical, warning, remark, missing)
  16. * component is the full path to the related bld.inf
  17. * configuration is the raptor build config name (e.g. armv5_urel)
  18. * text is the command run and its output (from the <recipe> element)
  19. Sometimes you may want to exclude some types of message from the .csv file.
  20. If the logs are very large you probably don't want to compare all the "ok"
  21. lines. So a list of message types to *ignore* can be passed as a parameter
  22. to the filter. For example,
  23. sbs --filters=csv[ok,remark] -f name
  24. will produce a .csv file without any "ok" or "remark" lines.