Closed daveneeley closed 12 years ago
Thank you for the issue. What locale was on your system? Do you have a patch for it?
The current culture is 1033 / en-US, on both the client and the teamcity server. I'm not sure how to patch it, because I don't see why it's invalid. ;)
If I drop the timezone offset (zzz) the issue goes away:
public IServiceMessage UpdateServiceMessage(IServiceMessage message)
{
if (message.DefaultValue != null) return message;
return new PatchedServiceMessage(message) { { "timestamp", myTimeService().ToString("yyyy-MM-dd'T'HH:mm:ss.fff", CultureInfo.InvariantCulture) } };
}
Thank you for info. It turned out, TeamCity expected timezone format without hour-minutes separator, i.e. -0700, but, .NET formatter used to return -07:00. I've added the fix
This code
Produces this error message in the output log
[06:52:48]: [Step 2/4] ##teamcity[buildStatisticValue key='CodeCoverageL' value='0.330792774812305' flowId='606841684' timestamp='2012-02-06T06:52:48.611-07:00'] [06:52:48]: [Step 2/4] Unparseable date: "2012-02-06T06:52:48.611-07:00"
I can see that the timestamp is being produced by this code in TimeStampUpdater.cs:
However, I'm not sure how to override this format for TC 6.5.