JUnit XML: Fix reported timestamp is wrong

Timestamps in the generated report are in local time but it is missing the timezone indicator. Because of this, Azure Pipelines interprets the timestamp as UTC, which is typically wrong. Fixed by always reporting timestamps in UTC and adding "Z" to the value.
logmanoriginal · Jan 7, 2024 · 03fffb8 · 03fffb8
1 parent 11379cd
commit 03fffb8
Show file tree

Hide file tree

Showing 4 changed files with 0 additions and 0 deletions.
diff --git a/JUnit XML/To ISO8601 Time.vi b/JUnit XML/To ISO8601 Time.vi
diff --git a/...ite.Serialize - Invalid character in Hostname - XML does not contain invalid character.vi b/...ite.Serialize - Invalid character in Hostname - XML does not contain invalid character.vi
diff --git a/...t Suite.Serialize - Invalid character in Name - XML does not contain invalid character.vi b/...t Suite.Serialize - Invalid character in Name - XML does not contain invalid character.vi
diff --git a/...uite.Serialize - Invalid character in Package - XML does not contain invalid character.vi b/...uite.Serialize - Invalid character in Package - XML does not contain invalid character.vi