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

Documentation regarding running/regenerating stability test plans #1393

Open
EmilyMatt opened this issue Feb 12, 2025 · 7 comments
Open

Documentation regarding running/regenerating stability test plans #1393

EmilyMatt opened this issue Feb 12, 2025 · 7 comments
Labels
enhancement New feature or request

Comments

@EmilyMatt
Copy link
Contributor

What is the problem the feature request solves?

I think the documentation is not clear enough on this.
Using a clean main branch, I tried running
./mvnw -pl spark -Dsuites="org.apache.spark.sql.comet.CometTPCDSV1_4_PlanStabilitySuite" -Pspark-3.5 -nsu test

It does not compile, I get an error in regards to

[ERROR] /home/emily/projects/datafusion-comet/spark/src/main/scala/org/apache/comet/CometExecIterator.scala:27: value COMET_METRICS_UPDATE_INTERVAL is not a member of object org.apache.comet.CometConf
[ERROR] /home/emily/projects/datafusion-comet/spark/src/main/scala/org/apache/comet/CometExecIterator.scala:75: not found: value COMET_METRICS_UPDATE_INTERVAL

I've tried compiling everything first, I've tried running all the tests first and only then running this, to no avail.
I've tried removing the -nsu, thinking snapshots might be interfering, as well as removing the -pl spark to see if maybe the general package is needed, the latter led to more general issues such as ByteBuffer not being found.

I'm compiling for Spark 3.5, using Ubuntu 24.04, on an x86 machine, with OpenJDK 8 installed, along with Scala 2.12
I've tried setting all the Profiles as well, this did not change anything.
I'm not sure which common snapshot does it use, as I've tried running make clean, mvn clean, as well as manually deleting all the target directories, tried running the tests directly afterwards, as well as after recompiling after the clean.
I think the documentation needs to be updated, as they present simple commands, which doesn't seem to be the case.

It's worth mentioning that compilation as well as all the tests work as expected, so this is not a general issue.
Leaving this as a feature request for updated documentation as I'm not sure whether there's a bug or I'm doing something wrong

Describe the potential solution

No response

Additional context

No response

@EmilyMatt EmilyMatt added the enhancement New feature or request label Feb 12, 2025
@wForget
Copy link
Member

wForget commented Feb 13, 2025

You can try adding -am like ./mvnw -am -pl spark ..., or run your command after mvn install.

@andygrove
Copy link
Member

I agree that the documentation is in need of improvement. I also found that the files get generated to $SPARK_HOME, so I usually set this env var to point to the root of the source repo.

@andygrove
Copy link
Member

It is also necessary to use different Java versions for different Spark versions. I use JDK 11 for Spark 3.x.x and JDK 17 for Spark 4.x.x

@EmilyMatt
Copy link
Contributor Author

@andygrove Is this mandatory? I have been running JDK 8 with Spark 3.5.1 for a while

@EmilyMatt
Copy link
Contributor Author

also, I've been able to run the tests by running without "-pl spark" now, but then my code is not ran but a default/previous version of Comet somehow? I'm truly stumped by this, I think there is something I seriously don't understand about what Maven is doing

@andygrove
Copy link
Member

also, I've been able to run the tests by running without "-pl spark" now, but then my code is not ran but a default/previous version of Comet somehow? I'm truly stumped by this, I think there is something I seriously don't understand about what Maven is doing

@EmilyMatt This may be because the diff files in the main branch currently have the wrong Comet version. This is fixed in #1404

@andygrove
Copy link
Member

@EmilyMatt This may be because the diff files in the main branch currently have the wrong Comet version. This is fixed in #1404

Sorry, ignore this. I was conflating two different issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants