Your message dated Tue, 13 Nov 2018 21:46:36 +0100
with message-id <[email protected]>
and subject line Re: Bug#913613: data/cronjobs/vcsstats: line 1: warning:
Skipping data file with no valid points
has caused the Debian Bug report #913613,
regarding data/cronjobs/vcsstats: line 1: warning: Skipping data file with no
valid points
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
913613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913613
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qa.debian.org
Severity: important
X-Debbugs-CC: Christoph Berg <[email protected]>
User: [email protected]
Usertags: vcswatch
Every day since 2018-10-05 00:00 UTC we get a mail from vcsstats:
From: Cron Daemon <[email protected]>
To: [email protected]
Subject: Cron <qa@quantz> nice -15 flock -n
/srv/qa.debian.org/lock/vcsstats /srv/qa.debian.org/data/cronjobs/vcsstats
line 1: warning: Skipping data file with no valid points
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Re: Paul Wise 2018-11-13
<[email protected]>
> Package: qa.debian.org
> Severity: important
> X-Debbugs-CC: Christoph Berg <[email protected]>
> User: [email protected]
> Usertags: vcswatch
>
> Every day since 2018-10-05 00:00 UTC we get a mail from vcsstats:
>
> From: Cron Daemon <[email protected]>
> To: [email protected]
> Subject: Cron <qa@quantz> nice -15 flock -n
> /srv/qa.debian.org/lock/vcsstats /srv/qa.debian.org/data/cronjobs/vcsstats
>
> line 1: warning: Skipping data file with no valid points
The immediate blame goes to Darcs for producing the first ERROR result
ever on 2018-10-05. Before that, there were only OK and NEW scan
results.
Of course the real blame goes to gnuplot for refusing to plot a column
with a lot of null values and only a real single '1'.
I fixed the issue by adding a '0' ERROR count to the vcsstats table
for the first date where Darcs results were recorded, 2006-10-01
00:00:00+00.
Christoph
--- End Message ---
