Last modified: 2013-05-06 19:20:43 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T49638, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47638 - Jenkins: Jobs should not be affected by .git/index.lock of previous run
Jenkins: Jobs should not be affected by .git/index.lock of previous run
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
wmf-deployment
All All
: Normal critical (vote)
: ---
Assigned To: Antoine "hashar" Musso (WMF)
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-25 13:10 UTC by Krinkle
Modified: 2013-05-06 19:20 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Comment 1 Krinkle 2013-04-25 14:19:28 UTC
It was causing it to fail for REL1_19,20,21 and master. Something was likely interrupted.

Doesn't workspace cleanup prevent this?

I've manually rm'ed the index.lock for now. Jobs are working again.
Comment 2 Antoine "hashar" Musso (WMF) 2013-04-29 20:24:55 UTC
Most probably related to a git process that crashed.  I will investigate the build logs to find out if that occurred on other repositories.
Comment 3 Antoine "hashar" Musso (WMF) 2013-05-06 19:20:43 UTC
I could not find any other occurrences of 'index.lock' in the April logs.

The job most probably got triggered when Jenkins was getting mad or restarting and git got unproperly killed leaving the lock behind.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links