Bug 63731 - if you have 2 testsuites, wrong name can appear in events
Summary: if you have 2 testsuites, wrong name can appear in events
Status: CLOSED DUPLICATE of bug 61265
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dominique Guilbaud CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 61727
Blocks:
  Show dependency tree
 
Reported: 2004-05-24 14:14 EDT by dirkers CLA
Modified: 2016-05-05 11:06 EDT (History)
2 users (show)

See Also:

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 dirkers CLA 2004-05-24 14:14:44 EDT 
I have 2 testsuites and a deployment going to a remote location. If I switch 
testsuites to run and then switch back the first testsuite can end up with an 
execution history events file that starts with the name of the second 
testsuite. For example, I have 'p1.testsuite' and 'wral.testsuite'. If I first 
run p1, then wral, then try to run p1 again, the execution history shows that I 
ran p1 BUT the name of the events file under the p1 execution history is wral
[p1] rather than p1[p1].
Comment 1 Valentina Popescu CLA 2005-01-12 00:21:53 EST 
Update component so that the defect can be tracked by the Test group
Comment 2 Dominique Guilbaud CLA 2005-01-24 09:45:26 EST 
The problem here is similar to the one described in bugzilla #61265. It is not
exactly a bug, but is caused by a confusing interface. Bugzilla #61727 "Launch
Configuration: need to differentiate automatic/manual naming of the Execution
Results" is an enhancement for removing the confusion.

*** This bug has been marked as a duplicate of 61265 ***
Comment 3 Paul Slauenwhite CLA 2006-11-16 09:02:10 EST 
ACTION: Please verify/close this defect.
Comment 4 Paul Slauenwhite CLA 2007-02-12 12:56:51 EST 
Closing by default since not closed by the originator in the 7+ months since being resolved.  

Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct.