-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
8185 - Refactor test #8231
base: dev
Are you sure you want to change the base?
8185 - Refactor test #8231
Conversation
Performance Before: 94.81s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_default_value_1_model 20.95s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_default_value_0_ 15.26s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_export_2_model 14.86s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_default_value_2_model 14.55s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_export_1_model 14.28s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_export_0_ Performance after: 1.62s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_ckpt_export_2_model 1.25s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_ckpt_export_default_2_model 0.64s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_ckpt_export_0_ 0.57s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_ckpt_export_1_model 0.57s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_ckpt_export_default_1_model 0.55s call tests/test_bundle_ckpt_export.py::TestCKPTExport::test_ckpt_export_default_0_ 0.01s setup tests/test_bundle_ckpt_export.py::TestCKPTExport::test_ckpt_export_0_
3e0fe76
to
1667eb7
Compare
Hi @ericspod, Just for context, last week, I started working in Jorge Cardoso's team at KCL, so I am still getting access to the cluster and waiting for a new laptop with a dedicated GPU. I am currently working on a laptop with integrated graphics, which is not very powerful. So, it has been hard for me to tackle the slow tests since they would run SUPER slow for me. This is why I moved to reorganise the tests. Since this obscures any further changes in these files on the tracking records, I suggest you review this part first, and I create a new pull request for the other points in your issue. Please let me know what you think. Many thanks |
Hi @garciadias I see that the tests have been moved which is good, but there's a few files that seem to have gone missing and some conflicts that need to be resolved. I'm sure you've kept what you were working on earlier so we can come back to that when you're ready. These changes are going to represent a significant change from what's in the tests folder so we'll have to discuss with other developers more. We discussed it briefly at the Core meeting but we should again, what I can suggest now is that the directory structure doesn't have to be so deep as you have it, so perhaps the Good to hear you've come on board with us, we should meet in person and discuss things further. Thanks! |
Hi @ericspod, thank you very much for reviewing this and for the welcoming regards. Missing files:When you say there are some missing files, are you referring to these file files?
If these are all missing files you are referring to, I can confirm that git marked them as deleted, but they are present at:
I don't understand why these were flagged as deleted. Conflicts:I will do my best to merge the current dev branch to this and keep solving the conflicts while we wait for approval of this change. Folder depth:Fair enough, I will move them. I am happy to keep adjusting until we are satisfied with the result. Please keep me posted on the conversation with the core group. Many thanks, Eric. |
for more information, see https://pre-commit.ci
Hi @garciadias There were 2 files mentioned as deleted in the "Files changed" section here, the second of these |
Thank you, @ericspod. I have now restored the I will be working on solving the other issues. Am I pushing too often? I see the whole pipeline is triggered. Should I accumulate some changes before pushing? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unittest logic didn't update here.
Now:
[2025-02-03T15:33:49.029Z] With file pattern: '^(?!test_integration).*(?<!_dist)$'
[2025-02-03T15:33:49.029Z] monai test runner: excluding tests.test_call_dist
[2025-02-03T15:33:49.029Z] monai test runner: excluding tests.test_timedcall_dist
[2025-02-03T15:33:49.029Z] ['tests.test_rand_torchio', 'tests.test_query_memory', 'tests.test_utils', 'tests.test_rand_torchiod', 'tests.test_masked_autoencoder_vit', 'tests.test_torchiod', 'tests.test_torchio', 'tests.test_print_info', 'tests.test_set_visible_devices', 'tests.test_auto3dseg']
[2025-02-03T15:33:49.029Z] time to discover tests: 1.4007233679294586s, total cases: 66.
Previous:
time to discover tests: 10.140145242214203s, total cases: 15864.
BTW, didn't check other tests.
also cc @ericspod
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am looking into the runtests.py file and trying to solve this. This regular expression seems to be filtering the tests, which is ok, but it is probably looking only on the root folder of the tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems related to https://github.com/Project-MONAI/MONAI/blob/dev/tests/runner.py#L127
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@garciadias This is one of those places that we need to do recursive glob searching like the other areas we discussed. The whole block mentioned here can be done as something like:
with PerfContext() as pc:
# the files are searched from `tests/` folder, starting with `test_`
cur_dir = os.path.dirname(__file__)
files = glob.glob(os.path.join(cur_dir, "**", "test_*.py"), recursive=True)
files = [f for f in files if re.match(args.pattern, f)]
cases = [os.path.relpath(f, cur_dir).replace(os.sep, ".").replace(".py", "") for f in files]
print(cases)
tests = unittest.TestLoader().loadTestsFromNames(cases)
I think what you have in the current version if equivalent, I'm double checking myself in case we've missed something but then any other issues could be in runtests.sh as you mentioned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just noticed that it has been updated. Please ignore.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that was the problem. I think I have now fixed it. I can't find any coverage report for the most recent commits. Is that something I need to trigger?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that was the problem. I think I have now fixed it. I can't find any coverage report for the most recent commits. Is that something I need to trigger?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codecov used to post a link for things in PRs, but the page is always https://app.codecov.io/gh/Project-MONAI/MONAI I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link for this PR however isn't so helpful at the moment: https://app.codecov.io/gh/Project-MONAI/MONAI/pull/8231
It appears that there has been a significant drop in code coverage. Do you have any insights into why this might be happening, and should we be concerned about it? @ericspod @garciadias |
I think it is related to the issue you pointed out on the unittest. I will work on fixing this. |
/build |
I suggest that we add |
for more information, see https://pre-commit.ci
tests/CT_DICOM/__init__.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding __init__.py
files to directories which do not contain code leads to unexpected behaviour, I think some of your test fails are related to this. I'd remove this and any others added to pure data directories, but leave those in directories containing subdirectories with code.
Signed-off-by: R. Garcia-Dias <[email protected]>
Signed-off-by: R. Garcia-Dias <[email protected]>
Signed-off-by: R. Garcia-Dias <[email protected]>
Fixes #8185
Description
Reorganize tests
I have looked at the imports in each test file and the test title to identify which files were being tested. I mirrored the file structure of MONAI on the
tests
folder and moved the files accordingly. I used some helper scripts, but the process required substantial manual intervention. When uncertain, I moved the tests to theintegration
folder since the confusion always involved many imports, and I could not find clarity from the test name.Please review the integration folder carefully, which is the one that I feel the least confident about.