Slow TestGetEmail using socks
See original GitHub issueWhen I run tests (just as python qucktest.py helpdesk
) they take 40 minutes; IF i set variable case_socks
to just [False]
in the test_get_email.py file it works fine.
To Reproduce
- run virtualenv or install test and base requirements in other way
- run
python quicktest.py
- observe it’s slow
- open helpdesk/tests/test_get_email.py and set
case_socks
variable to[False]
- re-run the tests and observe it’s working fast now
Expected behavior It works fine from the box
May be it lacks the documentation how to configure these socks things, but I feel that it’s just misconfigured from the box and tries to connect to some non-existent service (which is incorrect because these tests are unit, not integration, and generally shouldn’t be connecting anywhere).
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
How to Set up SSH SOCKS Tunnel for Private Browsing in ...
In this tutorial, we will initiate the process of building an encrypted SSH tunnel and configuring Google Chrome and Firefox web browsers to...
Read more >Frequently asked questions and Help | SOCCER.COM
Shop for all your soccer equipment and apparel needs including soccer shoes, ... How do I check the status of an Order that...
Read more >Diabetes and Your Feet - CDC
Always wear socks with your shoes. Trim your toenails straight across and gently smooth any sharp edges with a nail file. Have your...
Read more >How to test email and SMS with Cypress | Mailosaur Docs
Learn how to test email and SMS messages in Cypress, using Mailosaur. ... Automate email tests with Cypress and Mailosaur ... This will...
Read more >Foot Problems | NIDDK - Diabetes
Wear shoes and socks at all times. Protect your feet from hot and cold. Keep the blood flowing to your feet. Get a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@gwasser Sorry, I didn’t look any furhter, saw a ‘fix’ was in place and reported back. I’d say close for now and re-address later if needed.
I think I remember this as some kind of syntax change that caused problems. Has it been handled somewhere else in the code? It seems like the tests have been running much faster recently, if so I think we could just close this ticket.