TST: test_yahoo/test_options is failing (return no data)

[jreback]

#3822 test_options is failing

cc @gliptak

[jreback]

still failing sometimes

cc @gliptak

[gliptak]

@jreback I looked at @cpcloud 's changes, I understand the benefits of smaller tests, but not sure to follow how these are actually failing ...

[jreback]

the test_yahoo/test_options is failing sometimes
in that it returns no data

I have seen it fail on Travis and when I run it locally
it's not very time

see if u can figure out what it is

thanks

[gliptak]

ok, I read through pydata#3982 those should be covered by @network let's see what shows up after all of @cpcloud 's fixes are committed

[jtratner]

I think @cpcloud's handled the AttributeError and others...are you seeing
something different?

On Thu, Jun 27, 2013 at 7:56 PM, gliptak notifications@github.com wrote:

ok, I read through #3982 https://github.com/pydata/pandas/issues/3982those should be covered by
@network let's see what shows up after all of @cpcloudhttps://github.com/cpcloud's fixes are committed

—
Reply to this email directly or view it on GitHubhttps://github.com/pydata/pandas/issues/4028#issuecomment-20162987
.

[jreback]

the option call sometimes returns nothing (not an error just no calls or puts)
it is probably an error somewhere that is being swallowed

[gliptak]

if specifically the options calls failing, I would suspect the parsing of the HTML

[cpcloud]

man this is annoying

[cpcloud]

https://travis-ci.org/pydata/pandas/jobs/8544014

[cpcloud]

i think we should wait for cleanup of data.py...i can finish up this weekend and get to the bottom of this maybe even today

[jreback]

up 2 you...it seems to work sometimes....

i'll bet that the actual call just returns invalid xml sometimes which really should be treated as an error

[cpcloud]

yep, but it's annoying because it's in the method and would be hard to test for the error, because e.g., you could parse in the test and check for the non-null root node, but i bet it willl parse successfully outside the call and then still fail inside

[cpcloud]

waiting for data.py cleanup will enable me to only write the error check once since i've consolidated all of the exact copied code in Options

[jreback]

ok....I thought you were merging the data cleanup now?

[cpcloud]

no i need to do 1 or 2 more things...soon tho