dramaticlly commented on PR #13645:
URL: https://github.com/apache/iceberg/pull/13645#issuecomment-3114133518
> ```
> ./gradlew spotlessApply
iceberg-13630
> Starting a Gradle Daemon, 2 incompatible Daemons could not be reused, use
--status for details
> Configuration on demand is an incubating feature.
>
> [Incubating] Problems report is available at:
file:///Users/melbeher/go/src/apache/iceberg/build/reports/problems/problems-report.html
>
> Deprecated Gradle features were used in this build, making it incompatible
with Gradle 9.0.
>
> You can use '--warning-mode all' to show the individual deprecation
warnings and determine if they come from your own scripts or plugins.
>
> For more on this, please refer to
https://docs.gradle.org/8.14.3/userguide/command_line_interface.html#sec:command_line_warnings
in the Gradle documentation.
>
> BUILD SUCCESSFUL in 4s
> 71 actionable tasks: 71 up-to-date
> ```
@Elbehery
Usually I would run `./gradlew -DallVersions revapi spotlessApply
checkStyleMain checkStyleTest` before commit
Looks like CI is failing on spotless, I would double check if there's any
files changed as the result of running linter (spotlessApply command). In case
if there's files changed on disk but not reflect in the patch yet, I would add
them and push a new commit and this would make next CI run pass build checks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
