Łukasz 'sil2100' Zemczak
aa880c0d38
SRU ADT regression: add newlines to the list of failures.
2019-08-29 14:30:53 +02:00
Łukasz 'sil2100' Zemczak
36047784d9
SRU ADT regression: use the SRU team special bot-account for sending notifications.
2019-08-29 09:34:43 +02:00
Łukasz 'sil2100' Zemczak
32467742bd
SRU ADT regression: use the right policy_info to determine if tests have regressed.
2019-08-28 18:29:45 +02:00
Łukasz 'sil2100' Zemczak
e51cc58a2b
Switch logic of detecting failures to looking for failed tests in policy_info. Explicitly list all failing tests in the bug comment. Change wording.
2019-07-19 15:43:54 +02:00
Łukasz 'sil2100' Zemczak
316fad3442
SRU ADT regression: temporarily use my e-mail in the From: header.
2019-06-25 18:49:38 +02:00
Łukasz 'sil2100' Zemczak
d21bd600cc
SRU ADT regression: handle errors in sendmail.
2019-06-25 16:16:26 +02:00
Łukasz 'sil2100' Zemczak
1cbc21d258
SRU ADT regression: Fix state checking as now it again needs to include the info for distro and series. Add unit test.
2019-05-24 16:18:34 +02:00
Łukasz 'sil2100' Zemczak
49e3d7e51c
SRU ADT regression: Remove the no-longer-needed state-file backup functionality as currently there's basically low risk that we'd crash mid-state-save. Add a test for this.
2019-05-23 19:08:29 +02:00
Iain Lane
c8492d4cc7
SRU ADT regression: Need to decode the returned bytes from urlopen()
2019-05-23 10:47:59 +01:00
Iain Lane
f10caba01d
SRU ADT regression: Handle unset changes_url (e.g. for syncs)
2019-05-23 10:27:24 +01:00
Iain Lane
c49f1ad8d5
SRU ADT regression: src is a dict
2019-05-23 10:26:22 +01:00
Iain Lane
bb032d98d8
SRU ADT: Be clear when printing log messages in dry-run mode
2019-05-22 17:47:29 +01:00
Łukasz 'sil2100' Zemczak
1690624d11
Add a new policy to message bugs on SRU regressions
...
It works like this. We wait until all tests have finished running. and
then grab their results. If there are any regressions, we mail each bug
with a link to pending-sru.html. There's a state file which records the
mails we've sent out, so that we don't mail the same bug multiple times.
2019-05-22 17:47:17 +01:00
