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

LUCENE-10331: don't emit the contents of the inputs file until we're actually running the task #554

Merged
merged 2 commits into from Dec 20, 2021

Conversation

dweiss
Copy link
Contributor

@dweiss dweiss commented Dec 20, 2021

No description provided.

@dweiss dweiss requested a review from rmuir December 20, 2021 17:23
@dweiss
Copy link
Contributor Author

dweiss commented Dec 20, 2021

This should do it, @rmuir

Copy link
Member

@rmuir rmuir left a comment

Choose a reason for hiding this comment

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

looks good, so we were creating the file at task definition time, which meant clean would always then wipe it? You probably don't even need a 2-core laptop to hit it :)

was able to reproduce the original problem against main branch with a gradle clean check. Can confirm gradle clean check works again with this fix. Thanks!

@dweiss
Copy link
Contributor Author

dweiss commented Dec 20, 2021

so we were creating the file at task definition time, which meant clean would always then wipe it?

Yep. the separation of evaluation/ configuration/ execution stages and what happens when is the meanest part of gradle in my experience.

@dweiss dweiss merged commit e790125 into apache:main Dec 20, 2021
dweiss added a commit that referenced this pull request Dec 20, 2021
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.

None yet

2 participants