Notes on fdatasync for the test suite

[vila]

>>>>> Martin Pool <mbp at canonical.com> writes:

    >> The last line is weird as the time stamp appears to be *after* the
    >> selftest start (22h36 >> 21:10) and I have no good guess here. I'd be
    >> inclined to guess for UTC+2 (so 22h36 UTC+2 == 20h36 UTC) but that would
    >> mean that even for that last submission, it took ~45 minutes to do
    >> whatever is needed before starting the 'make check', compile extensions
    >> and generate the doc ? A bit too much...
    >> 
    >> Anyone knows how/when the file time stamp is created and in which TZ ?

    > file times will normally be updated every time data is written to them
    > (so, the last time anything was written) and they're stored in utc and
    > displayed as whatever tz you ask for.  It's possible but probably
    > unlikely a machine's clock is set wrong.

I'm not talking about the file modification or creation times but about
the stamp that is embedded in the file *name*. As such I suspect it's
the current time when the file is created or even when the submission is
received (but with a resolution of 1 second, I except it's taken at a
place where the processing will take more than one second).

I.e.:

  -rw-r--r-- 1 vila vila     2932 2011-09-02 01:15 patch.1314909400.log

 patch.1314909400.log ==> 2011-09-01 22:36:40

2011-09-01 22:36:40: duration: 2:04:57 start: 2011-09-01 21:10:23, end: 2011-09-01 23:15:20

so the modification time roughly matches the end time but the origin of
the stamp in the name is unclear. No big deal, just surprising and not
worth investigating for now (I asked in case people already knows).

      Vincent