https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8041
Bug ID: 8041
Summary: test spam for t/pyzor.t expires from pyzor server,
breaking test
Product: Spamassassin
Version: 4.0.0
Hardware: All
OS: All
Status: NEW
Severity: minor
Priority: P2
Component: Regression Tests
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: Undefined
During final testing for 4.0.0rc2 t/pyzor.t started failing because
t/data/spam/pyzor no longer was flagged as spam by pyzor check. This apparently
also happened about a year ago, as indicated by a comment in t/pyzor.t and
commit of revision 1893711 that replaced t/data/spam/pyzor with a more recent
spam example.
The symptom was failure of the two subtests in t/pyzor.t that check
t/data/spam/pyzor, and it could be verified by running the command
pyzor check < t/data/spam/pyzor
which returned a 200 OK with report count 0 and whitelist 0.
To fix it, I ran
pyzor report < t/data/spam/pyzor
after which the pyzor check command returned a report count of 1, and t/pyzor.t
started working again.
I'm not comfortable adding pyzor reporting to the test as a way of ensuring
that the test spam doesn't expire, causing everyone who runs the tests to keep
reporting it to the pyzor public server. We just have to make sure that every
so many months a pyzor report does get run.
I'll leave this issue open so if the test spam does expire again this can be
found by whoever investigates.
If anyone comes up with a more automatic solution, this can be closed.
In the meantime, I'll run the pyzor report command from time to time when I
think about it.
Note that pyzor does not recognize GTUBE, so that is not a solution unless the
pyzor developers can be convinced to add that or some other non-expiring test
spam as a feature.
--
You are receiving this mail because:
You are the assignee for the bug.
