#22398 Lockfiles not written for successful resolves if one resolve fails during generation Issue created by jasonwbarnett Describe the bug When generating lockfiles with multiple resolves using Pants, if any one resolve fails, none of the successful lockfiles are written to disk. This creates friction in monorepos with many resolves — for example, if 12 out of 13 resolves succeed but 1 fails, you have to re-run the entire process with the failing one excluded, even though the others completed just fine. Pants version 2.26.0 OS macOS and Linux Additional info This could be either a design decision or an implementation quirk — we're mainly asking if this behavior is intentional and if it could be improved to persist successfully generated lockfiles even if one fails. Related Slack thread: https://pantsbuild.slack.com/archives/C046T6T9U/p1749589092353329 pantsbuild/pants