I have written these commits since last Sunday and all of them are running in
the current patchew.org deployment. The only thought is we should do a better
job on making use of next.patchew.org, which is always apparent but
nevertheless challenging: we don't have enough spare time and resources for a
full replication of the server, importers and testers.
On the other hand we've done a fairly good job with writing tests, and the only
real bug here is that we missed the regression caused by property to result
conversion for git, which leaded to a disjoint between git and testing: the
"event" connecting them was abandoned. The end-to-end
"importer->server->tester" case using patchew-cli should help catch such a bug
in the future.
Fam Zheng (10):
testing: Avoid masking out outter iterator r
cli: Default -N of tester command to -1
deploy-testers: Allow deploy with normal user access
testing: Fix git info for testing-get method
git: Emit git result update event
testing: Reset testing upon git result update
testing: Move do_apply to base class
tests: Create repo automatically for projects
tests: Fix "testing"
docker: Unlimited restart of systemd service
mods/git.py | 12 +++++--
mods/testing.py | 21 +++++++++---
patchew-cli | 2 +-
scripts/playbooks/deploy-testers.yml | 8 +----
scripts/playbooks/templates/docker.service.j2 | 2 ++
tests/patchewtest.py | 16 +++++++--
tests/test_git.py | 5 ---
tests/test_testing.py | 33 +++----------------
8 files changed, 47 insertions(+), 52 deletions(-)
--
2.17.1
_______________________________________________
Patchew-devel mailing list
Patchew-devel@redhat.com
https://www.redhat.com/mailman/listinfo/patchew-devel