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

[BUG] gradlew clean doesn't remove JNI artifacts #2515

Closed
sam-herman opened this issue Feb 10, 2025 · 1 comment · Fixed by #2516
Closed

[BUG] gradlew clean doesn't remove JNI artifacts #2515

sam-herman opened this issue Feb 10, 2025 · 1 comment · Fixed by #2516
Labels
bug Something isn't working untriaged

Comments

@sam-herman
Copy link
Contributor

What is the bug?
./gradlew clean is a standard task that is supposed to allow for subsequent builds to have a clean idempotent start.
At the moment all the JNI artifacts from previous builds remain and pollute the builds.
This is making it hard to reproduce locally when something breaks on the remote build and vice versa. For example:
#2442 (comment)

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. ./gradlew clean; ./gradlew build
  2. pull new code
  3. ./gradlew clean; ./gradlew build
  4. Will result in unexpected behavior see fix broken build flag, move build to one directory #2442 (comment)

What is the expected behavior?
After this change the expected behavior should make sure we have no left over build artifacts for JNI and they will all build from scratch

@sam-herman
Copy link
Contributor Author

Please assign to me( @sam-herman ) I have a PR already submitted for this:
#2516

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant