[Bug 39380] test.winehq.org: Provide a way to know why a report was rejected

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=39380

François Gouget <fgouget at codeweavers.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|wine-bugs at winehq.org        |fgouget at codeweavers.com
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #3 from François Gouget <fgouget at codeweavers.com> ---
I figured out what happens.

When dissect rejects a report no build directory is marked as outdated. As a
result gather has nothing to do and thus the main index files don't need an
updated. So the cron script skips re-running build-index. However build-index
is also responsible for updating errors.html.

So when a report is rejected one will not know why until another report is
accepted.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.