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

[WIP] Move xfail to allow_non_gpu for non-UTC time zone. #9869

Closed
wants to merge 34 commits into from

Conversation

res-life
Copy link
Collaborator

@res-life res-life commented Nov 28, 2023

This is based on #9719
This PR will be merged to #9719
It's here for review purpose.

@res-life res-life force-pushed the ferdinand_fine_grained branch from abf5b61 to 8ce99fd Compare November 28, 2023 09:01
@res-life res-life force-pushed the ferdinand_fine_grained branch from 8ce99fd to 778fa00 Compare November 28, 2023 09:32


# allow non gpu when time zone is non-UTC because of https://github.com/NVIDIA/spark-rapids/issues/9653'
non_utc_allow=['ProjectExec', 'FilterExec', 'FileSourceScanExec', 'BatchScanExec', 'CollectLimitExec', 'DeserializeToObjectExec', 'DataWritingCommandExec', 'WriteFilesExec'] if is_not_utc() else []
Copy link
Collaborator

Choose a reason for hiding this comment

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

FYI. ShuffleExchangeExec based on my local test.

@res-life res-life force-pushed the ferdinand_fine_grained branch from b6ad928 to 3f90a9d Compare November 28, 2023 13:35
@res-life res-life changed the base branch from branch-24.02 to branch-23.12 November 28, 2023 14:01
@revans2
Copy link
Collaborator

revans2 commented Nov 28, 2023

@res-life can you please explain why you are making this change? I think it is to allow us to verify that we get the right answer instead of seeing data corruption. If so I am conflicted here. I like the idea of verifying that we got the right answer. But I don't like that this is done with one list of operators that are allowed to not be on the GPU for every test. Each test is unique and I get that you don't want to spend a ton of time to customize it per test. But if we don't look at each test and know what we expect to fall back how do we know that we are doing the right thing?

I am not going to block this from going in, because I think it is better than what we have now. But I really would like to see a follow on issue to go back for all of the tests and customize it.

@res-life res-life force-pushed the ferdinand_fine_grained branch from 3f90a9d to bb1cbca Compare November 29, 2023 08:59
@res-life res-life force-pushed the ferdinand_fine_grained branch from 094c533 to 70c2167 Compare November 29, 2023 14:09
@winningsix winningsix closed this Dec 1, 2023
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.

3 participants