Timestamp is ignoring timezone offset

[msaladin]

In the generated XML, the timestamp looks like this:
<testsuite ... timestamp="2016-09-07T10:19:10"...>

and in this example, the timestamp is wrong by two hours (I executed the test at 12:19). The reason seems to be the code in index.js
var timestamp = (new Date()).toISOString().substr(0, 19)

which seems to ignore the timezome. This article describes that the time zone is ignored by default in JavaScript: http://stackoverflow.com/questions/10830357/javascript-toisostring-ignores-timezone-offset

It is not really a terrible bug, but I like to have a timestamp which is correct, because this timestamp is then propagated to the HTML report and when looking at the report, I am interested whether it is an old report or a recent one.

This might work very well on my machine (where I know that the difference is always two hours), but as soon as there is some continuous integration environment and I don't know where in the world this environment is running, I am no longer sure whether the generated report is recent or not.

Possible fixes are described in the stackoverflow article.
Is this something that you can fix?

Thanks & Cheers
Michael

[kieronlanning]

This is breaking our build server at the moment.

We can't upload the test results because the build system thinks the test results timestamp is invalid. We've got a script which effectively takes the timestamp and fixes it, but this is less than ideal.

[hicom150]

The problem is that the JUnit XML Schema we are validating against is expecting ISO8601 without timezone 😓 as we can see here https://github.com/karma-runner/karma-junit-reporter/blob/master/junit-schema.xsd#L15