implement resilience to warcprox outage, i.e. deal with brozzler.ProxyError in brozzler-worker

This commit is contained in:
Noah Levitt 2017-04-18 17:54:12 -07:00
parent 5603ff5380
commit 8256a34b4f
4 changed files with 142 additions and 6 deletions

View file

@ -17,5 +17,5 @@ vagrant ssh -- 'status warcprox ;
status vnc-websock'
echo
vagrant ssh -- 'source /opt/brozzler-ve34/bin/activate && pip install pytest'
vagrant ssh -- 'set -x ; source /opt/brozzler-ve34/bin/activate && pip install pytest && pip install --upgrade --pre "warcprox>=2.1b1.dev71"'
vagrant ssh -- "source /opt/brozzler-ve34/bin/activate && DISPLAY=:1 py.test -v /brozzler/tests $@"