<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2023-05-24T20:44:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Tracy Smail</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2022-09-27T23:18:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment>Verified w/ DP 4.0.714
 
Using a slice nano,</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2022-09-15T20:23:56Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Jaime Lopez</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-09-14T21:56:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-08-26T15:35:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>Bug was found if Data folder included tests that don't have DAS that use time sync, manifesting as no tests at all showing up in View Data.
 
Changes:
 
 
Prevents exception if no test modules in test have a timestamp
 
Adds check to MinUnixTime for enumerable length
 
 
Testing:
 
 
Create, run, and download data for a test that uses DAS that do not time sync (I used SLICE Micro).
 
Repeat test as normal below. You should see all tests in View Data tab
 
 
r47532 for v4.0 maint and v4.1 dev</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-08-24T23:40:28Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>John Dowling</User>
    <Comment>Reopening, bug found if Data folder includes non-timesync tests</Comment>
    <StatusString>Reopened</StatusString>
    <TimeStamp>2022-08-24T23:26:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Tracy Smail</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-08-10T20:43:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Tracy Smail</User>
    <Comment>Verified the fix using DataPro version 4.0.688.47264.  Timestamp issued with each event showed  Date time with milliseconds.  On my system, the timestamp always ended with 000 milli-seconds.  I verified this was not the typical case by watching it run on the developer's system.</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2022-08-10T20:02:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Tracy Smail</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-08-09T21:50:21Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Farshid Atashband</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-08-09T17:37:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Farshid Atashband</User>
    <Comment>Fixed in DP 4.0 @ rev 47259
QA can verify the "View Data" tab the event now has a "Time Stamp:" with milliseconds part , also in the Graphs the event is shown with the milliseconds info. 
The date &amp; time is parsed from TriggerTimestampSec element from the dts file and milliseconds part is parsed from TriggerTimestampNanoSec, if the date is before 1/1/1990 then the parsed "Timestamp" element value will be used as it was before.

</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2022-08-09T17:31:27Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Farshid Atashband</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-08-04T20:45:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Farshid Atashband</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-08-03T23:13:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Farshid Atashband</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-08-02T19:17:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Farshid Atashband</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-07-28T16:30:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment>\\dts\files\Software\Private\Useful_Test_Files\DataPRO\Data\TSR AIR\MS_29410</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-07-28T15:39:25Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment>"Time Stamp:" in this context may be using a windows file timestamp
 
What we want is a timestamp from TriggerTimeStampSec and TriggerTimeStampNanosec. There is a Common utility function that parses out these attributes to a datetime object.
 

public static Tuple&lt;double, double&gt; MinUnixTime(Test test)</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-07-26T22:58:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-07-26T21:46:33Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-07-26T21:41:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-07-26T21:41:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>There's an existing timestamp in the dataviewer that doesn't seem to be accurate for TSR AIR tests.
 
talking about the left hand side in the test selector in the viewer, this should be using the RTC time to determine the time stamp.
 
note that the implementation should consider that you have hundreds of tests, so parsing the xml for all the tests could be an ugly thing time wise, might be more efficient to have a text search within the file for &lt;start&gt; and &lt;/end&gt; tags for the property.
 
TriggerTimeStampSec
 
is the tag according to chris.</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-07-26T20:56:45Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-07-26T20:50:29Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>Increased time estimate as we may need to discuss what this means</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-07-26T20:32:53Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-07-26T20:32:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-07-26T20:15:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2022-07-26T20:13:16Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2022-07-26T19:09:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Jerry Lawrence</User>
    <Comment>24. [Software] Event names need to have second resolution.
 
[RW] I think 24 is important to have before we consider Phase I done.</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2022-07-26T19:09:10Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>