Clover stores "magic" date in dbVersion

[Vladyslav Kurmaz]

Hi.

I need any suggestions about how I can debug next issue:

After applying instrumentalization and running e2e tests, we try to generate coverage. But every time clover shows some magic date Thu Nov 28 09:40:07 EST 2019 as base for calculation. We delete clover.db before every run, but this date appears every time. Host VM date is ok, stat clover.db also shows date when calculation is run Thu Jan 16 10:35:39 EST 2020

Question: Which date/time API is used during instrumentalization phase to get date to store it in dbVersion?

Thanks in advance.

Read data for file "/opt/bmc/bwf/coverage/e2e/api/./clover/clover.dbid0vx6_k5gwbg20": FileBasedCoverageRecordingTranscript[header=Header[dbVersion=1574952007703, writeTimeStamp=1579188939152, format=0], coverageSum=47, hitCounts.length=28521]
Global recording file:
  file=RecordingTranscripts.FileRef[datafile=/opt/bmc/bwf/coverage/e2e/api/./clover/clover.dbid0vx6_k5gwbg20, testRecording=false, typedTestId=-1, runId=0, hash=1110267546, timestamp=1579188934152]
  dbVersion=1574952007703 (Thu Nov 28 09:40:07 EST 2019)
  writeTimeStamp=1579188939152 (Thu Jan 16 10:35:39 EST 2020)
Ignoring coverage recording FileBasedCoverageRecordingTranscript[header=Header[dbVersion=1574952007703, writeTimeStamp=1579188939152, format=0], coverageSum=47, hitCounts.length=28521] because no FileInfo supports its coverage range

[Vladyslav Kurmaz]

The issue can be closed. The problem was in outdated docker images at our CI.