Workaround for 'could not acquire lock', see https://issues.apache.org/jira/browse/MNG-7868#8063
Conversation
There was a problem hiding this comment.
If the issue is related to mvn -T one option would be to run a go-offline phase first and then build with -o but that won't work unfortunately, or at least it didn't every time I've tried in the past. mvn dependency:go-offline won't actually pull everything it needs to build with -o. There is other plugin to "actually go offline" that I can't remember right now, but in any case I'd say lets try these maven params and see if we get less of these lock errors.
aaime
added
backport 2.25.x
|
The backport to stderrTo backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.26.x 2.26.x
# Navigate to the new working tree
cd .worktrees/backport-2.26.x
# Create a new branch
git switch --create backport-8063-to-2.26.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 9e4bb4b6444ae11718427638149f32a1be3a4a0b
# Push it to GitHub
git push --set-upstream origin backport-8063-to-2.26.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.26.xThen, create a pull request where the |
|
The backport to stderrTo backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.25.x 2.25.x
# Navigate to the new working tree
cd .worktrees/backport-2.25.x
# Create a new branch
git switch --create backport-8063-to-2.25.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 9e4bb4b6444ae11718427638149f32a1be3a4a0b
# Push it to GitHub
git push --set-upstream origin backport-8063-to-2.25.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.25.xThen, create a pull request where the |
3 participants
We have a fair amount of builds randomly failing with "could not acquire lock" in Maven itself.
Tracked it back to this, looks like it might be a networking issue, it's not solved but they propose workarounds to make it less likely:
https://issues.apache.org/jira/browse/MNG-7868
Those extra settings have been added to the maven options in this PR.
Checklist
mainbranch (backports managed later; ignore for branch specific issues).For core and extension modules:
[GEOS-XYZWV] Title of the Jira ticket.