I'm not super keen on vendoring a separate copy of `wptserve` just to have Python 2 compatibility as telemetry-tests-client is the last mach command and is also blocking a bunch of mach / build system cleanup. Seems like we should try and figure the timeouts out. After applying [D108834](https://phabricator.services.mozilla.com/D108834) locally and running `python3 ./mach telemetry-tests-client`, I also see a bunch of timeouts. Here is a snippet of the gecko.log: ```
Bug 1559976 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I'm not super keen on vendoring a separate copy of `wptserve` just to have Python 2 compatibility as telemetry-tests-client is the last mach command and is also blocking a bunch of mach / build system cleanup. Seems like we should try and figure the timeouts out. After applying [D108834](https://phabricator.services.mozilla.com/D108834) locally and running `python3 ./mach telemetry-tests-client`, I also see a bunch of timeouts. I've attached a snippet of my gecko.log. Lots of errors trying to submit to wptserve. James, does wptserve dump a log file somewhere?
I'm not super keen on vendoring a separate copy of `wptserve` just to have Python 2 compatibility as telemetry-tests-client is the last mach command and is also blocking a bunch of mach / build system cleanup. Seems like we should try and figure the timeouts out. After applying https://phabricator.services.mozilla.com/D108834 locally and running `python3 ./mach telemetry-tests-client`, I also see a bunch of timeouts. I've attached a snippet of my gecko.log. Lots of errors trying to submit to wptserve. James, does wptserve dump a log file somewhere?