Emit a warning from cronscript/checkwatches.py if http(s)_proxy is not set
Bug #235275 reported by
Gavin Panella
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Colin Watson | ||
Bug Description
This often causes problems at QA time. Normally http_proxy and https_proxy are set in the crontab, but when running checkwatches.py manually it's easy to forget. This means that we just end up with lots of ECONNREFUSED errors instead of the results of connecting to the remote tracker.
Fixing bug 235497 would also fix this bug.
| description: | updated |
| Changed in malone: | |
| status: | New → Confirmed |
| description: | updated |
| Changed in launchpad: | |
| status: | Confirmed → Triaged |
| importance: | Undecided → Low |
| visibility: | private → public |
| tags: | added: canonical-losa-lp |
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| Changed in launchpad: | |
| assignee: | nobody → Colin Watson (cjwatson) |
| status: | Triaged → Fix Released |
To post a comment you must log in.
I don't think this is an issue any more now that bug 235497 is fixed.