Coverage remained the same at 94.402% when pulling e7b2b8e9bf062fb00bd6855e540074b713fef9cc on tests into cb1dbf1ff8198106bff52c5bdc44a630d6f3c150 on master.
Coverage remained the same at 94.402% when pulling e7b2b8e9bf062fb00bd6855e540074b713fef9cc on tests into cb1dbf1ff8198106bff52c5bdc44a630d6f3c150 on master.
Coverage decreased (-0.3%) to 94.148% when pulling 5007c2677f5e990ffe4b29846e10bbde05160415 on tests into cb1dbf1ff8198106bff52c5bdc44a630d6f3c150 on master.
Coverage remained the same at 94.402% when pulling 55fd36ee04fd4049fa18888f33378aa5db49dc81 on tests into cb1dbf1ff8198106bff52c5bdc44a630d6f3c150 on master.
Issue type
Summary
Using a threaded HTTPServer should be better and more reliable. This should also fix some random issues on Travis.