Comment 6 for bug 1902249

On 20/11/2020 21:18, Klaus Heinrich Kiwi wrote:
> I'm afraid we'll have to reopen this, since the master version still
> seems to be generating invalid json files, albeit for another detail
> now:
>
> The python 3.6 json parser says this:
> "Exit unexpectedly with Exception=Invalid \escape: line 418 column 166 (char 15377)"
>
> the Line in question on the master fwts (line 418 is the second-to-last line below)
> {
> "line_num":25,
> "date":"20/11/20",
> "time":"14:59:56",
> "field_type":"Info",
> "level":"None",
> "status":"None",
> "failure_label":"None",
> "log_text":"Region name ibm,firmware-code@30000000 start: 0x30000000, len: 0x00500000\
> "
> }
>
> on fwts V19.12.00, the same entry is shown as:
> {
> "line_num":25,
> "date":"20\/11\/20",
> "time":"15:08:58",
> "field_type":"Info",
> "level":"None",
> "status":"None",
> "failure_label":"None",
> "log_text":"Region name ibm,firmware-code@30000000 start: 0x30000000, len: 0x00500000\n"
> },
>
> So looks like we need to escape the carriage-returns for '\n', not
> simply escape them with '\'.
>
My bad, I'll fix that up before next week's release

Colin