Unit tests fail when run in Australia

Re:Unit tests fail when run in Australia by encoderer on Tuesday April 07, 2015 @10:41PM (#9338531)

Oh, this is an interesting lead.... I feel pretty certain the request isn't coming from our Python after stepping-thru the code.

The other suggestions -- using a SSL proxy -- has been my plan of attack.

[ Parent | on HN ]

Re:Unit tests fail when run in Australia by Someone on Wednesday April 08, 2015 @02:12AM (#9339035)

If it takes several seconds to set up a test, I would give this a try:

  - start a test from the IDE,
  - wait a second or so,
  - manually pause all threads,
  - look at the stacks of the threads.

Might take two or three attempts, but likely should learn you a lot. Alternatively, use a real profiler to find the call(s) that take lots of time.

[ Parent | on HN ]

Re:Unit tests fail when run in Australia by ekimekim on Wednesday April 08, 2015 @08:02AM (#9340144)

Try an strace?

    strace -e trace=network ./run_my_unit_tests

[ Parent | on HN ]

Re:Unit tests fail when run in Australia by mst on Wednesday April 08, 2015 @12:35PM (#9341963)

Also -f so it follows forking (I always forget that the first time, swear, and have to re-run strace with it)

[ Parent | on HN ]

Re:Unit tests fail when run in Australia by airza on Wednesday April 08, 2015 @10:22AM (#9340927)

What OS are you running? It's pretty straightforward to get going on OSX in my experience.

[ Parent | on HN ]

Re:Unit tests fail when run in Australia by RubyPinch on Wednesday April 08, 2015 @07:20AM (#9339975)

mocking/replacing the http/urllibs? save a traceback when a connection is made?

[ Parent | on HN ]