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

datadeps: Don't skip copy on no writedep #580

Merged
merged 6 commits into from
Jan 22, 2025

Conversation

jpsamaroo
Copy link
Member

It's incorrect to skip on just this, because we might still need to copy for the purpose of adapting types, e.g. CPU -> GPU.

@jpsamaroo jpsamaroo force-pushed the jps/datadeps-no-haswritedep branch 3 times, most recently from db9df26 to 1359bd0 Compare November 26, 2024 15:36
@jpsamaroo jpsamaroo force-pushed the jps/datadeps-no-haswritedep branch from 1359bd0 to 36b269c Compare January 21, 2025 04:18
@jpsamaroo jpsamaroo force-pushed the jps/datadeps-no-haswritedep branch from f98c4bc to 96b4f89 Compare January 21, 2025 22:23
@jpsamaroo
Copy link
Member Author

Julia 1 failures are unrelated

@jpsamaroo jpsamaroo merged commit 496f68b into master Jan 22, 2025
6 of 11 checks passed
@jpsamaroo jpsamaroo deleted the jps/datadeps-no-haswritedep branch January 22, 2025 00:00
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