[Bug 39380] New: test.winehq.org: Provide a way to know why a report was rejected
wine-bugs at winehq.org
wine-bugs at winehq.org
Sat Oct 3 18:29:13 CDT 2015
https://bugs.winehq.org/show_bug.cgi?id=39380
Bug ID: 39380
Summary: test.winehq.org: Provide a way to know why a report
was rejected
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs at winehq.org
Reporter: fgouget at codeweavers.com
Distribution: ---
When WineTest submits a report that report can get thrown away. Either because
it's too big, because it has too many failures, because too many tests were
skipped or because of other reasons unknown.
The WineTest.exe is never notified of this because the report analysis is run
asynchronously with respect tot he submission process. But annoyingly there is
no way for the submitter to know why the report was rejected even later,
levaing him to guess as to what needs fixing.
One way to plug this hole would be to send an email with the reason to the
address field in the report. But that could probably be abused to send emails
to arbitrary persons.
A very simple alternative would be to create a per-commit text file containing
one line per ignored report with the report's tag, timestamp of when it was
analyzed and the reason why it was ignored.
--
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.
More information about the wine-bugs
mailing list