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

[BUG]: test_add_scores_stage_pipe intermittently fails #432

Closed
dagardner-nv opened this issue Nov 2, 2022 · 3 comments
Closed

[BUG]: test_add_scores_stage_pipe intermittently fails #432

dagardner-nv opened this issue Nov 2, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@dagardner-nv
Copy link
Contributor

Version

22.11

Which installation method(s) does this occur on?

Source

Describe the bug.

This test has failed a few times in CI with the following error:

FAILED test_add_scores_stage_pipe.py::test_add_scores_stage_pipe[use_python-10-2048-C] - pandas.errors.EmptyDataError: No columns to parse from file

Related to #423 & #427

Minimum reproducible example

No response

Relevant log output

FAILED test_add_scores_stage_pipe.py::test_add_scores_stage_pipe[use_python-10-2048-C] - pandas.errors.EmptyDataError: No columns to parse from file


### Full env printout

_No response_

### Other/Misc.

_No response_

### Code of Conduct

- [X] I agree to follow Morpheus' Code of Conduct
- [X] I have searched the [open bugs](https://github.com/nv-morpheus/Morpheus/issues?q=is%3Aopen+is%3Aissue+label%3Abug) and have found no duplicates for this bug report
@dagardner-nv dagardner-nv added the bug Something isn't working label Nov 2, 2022
@mdemoret-nv
Copy link
Contributor

I also see issues with this test that look like:

FAILED tests/test_add_scores_stage_pipe.py::test_add_scores_stage_pipe[use_python-10-2048-C] - RuntimeError: dictionary changed size during iteration
FAILED tests/test_add_scores_stage_pipe.py::test_add_scores_stage_multi_segment_pipe[use_python] - RuntimeError: dictionary changed size during iteration

Which is due to the repeat option on the FileSource stage. This will be fixed in PR #427. @dagardner-nv Do you think they are related?

@dagardner-nv
Copy link
Contributor Author

Which is due to the repeat option on the FileSource stage. This will be fixed in PR #427. @dagardner-nv Do you think they are related?

I saw the same thing, I added an explicit test for that by parameterizing the repeat value
23e3304

@dagardner-nv
Copy link
Contributor Author

This bug appears to be fixed by #444
I'm running the test in a loop to be sure, but it hasn't failed yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

2 participants