Bug 6492 – gram tests kill all personal gatekeepers

Bug 6492 - gram tests kill all personal gatekeepers

Summary:

gram tests kill all personal gatekeepers

Status:	RESOLVED FIXED

Product:	GRAM
Component:	gt2 tests
Version:	4.2.1
Platform:	Macintosh All

Importance:	P3 normal
Target Milestone:	---
Assigned To:	Joe Bester

URL:
Keywords:

Depends on:	6495
Blocks:
	Show dependency tree / graph

Reported:	2008-10-20 16:47 by Charles Bacon
Modified:	2008-10-24 10:56 (History)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Charles Bacon 2008-10-20 16:47:33

globus_gram_client_tools_test has multiple times where it invokes
"globus-personal-gatekeeper -killall".  I'm using one machine to test both
globus_4_2_branch and HEAD, and it turns out that one instance of
globus_gram_client_tools_test can accidentally kill the personal gatekeeper
being used by the other branch's globus_gram_client_tools_test.  Just saw that
happen today, in fact.

The test should get the contact returned by -start instead of assuming that the
first entry in -list is the one it started.  Then when it shuts it down, it
should use -kill <contact> instead of -killall.

------- Comment #1 From Joe Bester 2008-10-21 14:22:08 -------

This also can occur with globus_gram_cleint_test and
globus_gram_jobmanager_test.

------- Comment #2 From Joe Bester 2008-10-21 16:01:22 -------

Added a new bug---the reason the code does -killall and -list is to avoid hangs
when attempting to capture stdout of globus-personal-gatekeeper.

------- Comment #3 From Joe Bester 2008-10-24 10:56:48 -------

Fix committed to 4.2 branch and trunk.