Project

General

Profile

Bug #5092

env files don't need to define LOCKNAME by default

Added by Josef Sipek almost 6 years ago. Updated almost 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

Defining LOCKNAME in your env file causes nightly to create this lock file in addition to creating a lockfile in the workspace's log directory (as defined by ATLOG).

In other words, not defining LOCKNAME still prevents multiple concurrent builds of the same workspace because of the lock file that's always present in the log directory.

History

#1

Updated by Electric Monk almost 6 years ago

  • % Done changed from 40 to 100
  • Status changed from New to Closed

git commit 60a61f7adabc73a7a0cb70d200ac2a6735f4a6e8

commit  60a61f7adabc73a7a0cb70d200ac2a6735f4a6e8
Author: Josef 'Jeff' Sipek <josef.sipek@nexenta.com>
Date:   2014-08-15T20:08:15.000Z

    5092 env files don't need to define LOCKNAME by default
    5091 illumos.sh env file's LOCKNAME definition is busted
    Reviewed by: Dan McDonald <danmcd@omniti.com>
    Reviewed by: Garrett D'Amore <garrett@damore.org>
    Approved by: Robert Mustacchi <rm@joyent.com>

Also available in: Atom PDF