Skip to content

Conversation

@gsnedders
Copy link
Member

Previously we stopped parser tests once DataLossWarning was raised; we
now run let the parser run to completion before checking for raised
warnings. This hid several cases of where real exceptions were raised
after DataLossWarning was raised. This commit reveals these real
exceptions in the testsuite and fixes current failure.

Similar fixes are needed for the other tests.

Previously we stopped parser tests once DataLossWarning was raised; we
now run let the parser run to completion before checking for raised
warnings. This hid several cases of where real exceptions were raised
after DataLossWarning was raised. This commit reveals these real
exceptions in the testsuite and fixes current failure.

Similar fixes are needed for the other tests.
@gsnedders
Copy link
Member Author

72f2169

@gsnedders gsnedders closed this May 17, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant