-
Notifications
You must be signed in to change notification settings - Fork 242
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] Issues found by Spark UT Framework on RapidsRegexpExpressionsSuite #10774
Comments
Initial scope is triaging unit test failures to determine priorities of individual issues. |
So the 4 tests pass if I disable Whole-stage codegen in
I would recommend disabling it and retrying the whole suite of tests to check up on this issue and #10775 and maybe others. |
So most of these tests are falling back to the CPU (the ignored test is a codegen verification test):
These tests are all falling back to CPU for a couple of reasons: Use of non-literal patterns:
ConstantFolding is excluded:
Recommend to disable this suite until the tests can be rewritten to avoid these errors. Otherwise, this suite is just running the same tests run by Apache Spark. |
will be fixed by #10851, suggest to close this issue |
If we want to close this issue when #10851 is merged, then we can simply link that PR as closing this issue. Then it will be closed iff that PR is merged. I've updated this issue accordingly. |
Close by #10861 |
Describe the bug
Spark UT Framework enabled RapidsRegexpExpressionsSuite (#10743), with the following test cases explicitly excluded:
These excluded test cases needs further investigating!!!
Notice: Other test cases in this suite may pass with falling back!
Steps/Code to reproduce bug
mvn -Dbuildver=330 install -DskipTests
mvn -nsu -Dbuildver=330 -pl tests -Dsuites="org.apache.spark.sql.rapids.suites.RapidsXXXSuite" test
(replace RapidsXXXSuite with the right name in issue header). ALWAYS double check if your suite name coincide with in source code, as it may contain typos!Expected behavior
The suite can pass without excluding any test case.
The text was updated successfully, but these errors were encountered: