POFile stats warnings are bogus or being ignored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Данило Шеган |
Bug Description
rosetta-
== POFile stats Thu Jul 2 10:05:50 UTC 2009 ==
2009-07-02 10:05:51 INFO creating lockfile
2009-07-02 10:05:56 INFO Starting verification of POFile stats at id 0
2009-07-02 10:08:40 WARNING POFile 115468: cached stats were (0, 0, 110, 0), recomputed as (0, 1, 110, 0)
2009-07-02 10:08:43 WARNING POFile 115533: cached stats were (336, 13, 13, 13), recomputed as (336, 13, 13, 6)
2009-07-02 10:08:44 WARNING POFile 115534: cached stats were (181, 26, 77, 1), recomputed as (182, 36, 77, 1)
2009-07-02 10:08:44 WARNING POFile 115536: cached stats were (63, 0, 0, 0), recomputed as (64, 0, 0, 0)
2009-07-02 10:08:44 WARNING POFile 115539: cached stats were (286, 3, 3, 3), recomputed as (291, 3, 3, 2)
2009-07-02 10:08:44 WARNING POFile 115541: cached stats were (145, 21, 25, 30), recomputed as (148, 21, 25, 27)
If this is normal, these messages should not be warnings (debug or info).
If this is a problem, we need a process in place so the losas can fix it or escalate the problem to someone who can fix it.
Related branches
- Henning Eggers (community): Approve
- Diff: None lines
Changed in rosetta: | |
status: | Triaged → In Progress |
Changed in rosetta: | |
status: | Fix Committed → Fix Released |
Setting to high as this is an operational issue. The volume of output causes genuine issues to get lost in the noise. If these are genuine problems, log level should still be reduced and a note added to the bug report to reinstate the warning once we can cope with the issue.