Project

General

Profile

Actions

Bug #5091

closed

illumos.sh env file's LOCKNAME definition is busted

Added by Josef Sipek over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
tools - gate/build tools
Start date:
2014-08-14
Due date:
% Done:

100%

Estimated time:
Difficulty:
Bite-size
Tags:
needs-triage
Gerrit CR:

Description

The line:

export LOCKNAME="$(basename -- "$CODEMGR_WS")_nightly.lock" 

causes LOCKNAME to be equal to "--_nightly.lock" which causes all nightly runs to try to create the same lock file /tmp/--_nightly.lock. While this is ok on a single-user system that never runs multiple unreleated nightlys, it is only a matter of time before multi-user systems run into this problem. (It gets really annoying if you have an automated system like Jenkins locking out everyone from doing a nightly for hours on end.)

This used to work and the commit for bug 450 introduced the regression.


Related issues

Related to illumos gate - Feature #450: RFE: Do a small illumos.sh cleanupResolved2010-12-06

Actions
Actions

Also available in: Atom PDF