Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TEST-#7066: Explicitly check for exceptions in test_io.py #7067

Merged
merged 3 commits into from
Mar 12, 2024

Conversation

anmyachev
Copy link
Collaborator

@anmyachev anmyachev commented Mar 12, 2024

What do these changes do?

  • first commit message and PR title follow format outlined here

    NOTE: If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

  • passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
  • passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
  • signed commit with git commit -s
  • Resolves Explicitly check for exceptions in test_io.py #7066
  • tests added and passing
  • module layout described at docs/development/architecture.rst is up-to-date

Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
@anmyachev anmyachev marked this pull request as ready for review March 12, 2024 14:23
"parse_dates3" in request.node.callspec.id
or "parse_dates4" in request.node.callspec.id
):
raising_exceptions = False
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we put a similar FIXME here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I specified an exception

from ray.exceptions import RayTaskError

# unwrap ray exceptions from remote worker
if isinstance(md_e, RayTaskError):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have similar problems for Dask and Unidist?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems not, otherwise they would have to break these tests too.

Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
@@ -380,9 +383,14 @@ def test_read_csv_parsing_1(
).columns
}

raising_exceptions = None
if engine == "c" and skipfooter != 0:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In all other cases there are no exceptions, right? or we just don't check raising exceptions in those cases?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In all other cases there are no exceptions, right?

Yes and no. There really are no exceptions in these situations, but this is not being checked now, but it will be after #6954

@YarShev YarShev merged commit a285f8a into modin-project:master Mar 12, 2024
37 checks passed
@anmyachev anmyachev deleted the issue7066 branch March 12, 2024 20:48
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.

Explicitly check for exceptions in test_io.py
2 participants