You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Paraphrasing from a description of the issue by @bryevdv:
Most legate driver tests were originally developed in an env where there was never "ucx" present, so install_info.networks is not actually tightly controlled in every test, just due to oversight. I.e. "ucx" is explicitly added in tests intended to be "with ucx" but it's not explicitly removed in all other tests that just assume "without ucx" is the defatult state.
We should actually go through and remove the assumption that "no ucx" is always the "default".
Paraphrasing from a description of the issue by @bryevdv:
Most legate driver tests were originally developed in an env where there was never "ucx" present, so
install_info.networks
is not actually tightly controlled in every test, just due to oversight. I.e. "ucx" is explicitly added in tests intended to be "with ucx" but it's not explicitly removed in all other tests that just assume "without ucx" is the defatult state.We should actually go through and remove the assumption that "no ucx" is always the "default".
See https://github.com/nv-legate/legate.core/actions/runs/6571421549/job/17850858678 for a case where this backfired, when ucx was added to the build.
The text was updated successfully, but these errors were encountered: