Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315621 - Removing/moving a test report causes exception and action is aborted
Summary: Removing/moving a test report causes exception and action is aborted
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: TPTP (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Bozier jerome CLA
QA Contact: Kathy Chan CLA
URL:
Whiteboard: closed472
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-03 12:12 EDT by Ben Chen CLA
Modified: 2016-05-05 11:09 EDT (History)
1 user (show)

See Also:


Attachments
ss (196.74 KB, image/jpeg)
2010-06-08 10:24 EDT, Ben Chen CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Chen CLA 2010-06-03 12:12:13 EDT
Build Identifier: TPTP-4.7.0RC3-201006011014

new test cases required once proven valid

Reproducible: Always

Steps to Reproduce:
1.In test navigator, generated a test report, say test pass report
2.Attempt to move the report to another folder
3.Notice the exception in error log and action is not proceeded
4.Attempt to remove the report
5.Notice the abort message in refactoring pop-up window
6.Notice the exception in error log
Comment 1 Kathy Chan CLA 2010-06-03 15:19:35 EDT
Ben, is this a recent regression?

Jerome, please take a look.
Comment 2 Ben Chen CLA 2010-06-03 15:21:29 EDT
(In reply to comment #1)
> Ben, is this a recent regression?
>

Doubt it since I do not recall any tesst against this scenario
Comment 3 Bozier jerome CLA 2010-06-04 04:50:38 EDT
tested with manual test log (the ones inside testnavigator.tests)

i can not reproduce part 1/2/3

for part 4/5/6, i can only reproduce it when test log is in a project imported from another workspace (see bugzilla 315093)

if test log project is in the current workspace, i can not reproduce part 4/5/6

i'd be tempted to mark it as duplicate of 315093 but i would need more precision before :

. what kind of test did you used ?
. what was the project hierarchy ?

simpler would be to attach the workspace you used + saying me operation you done (witch test log was moved in what folder)

many thanks in advance

Jerome
Comment 4 Ben Chen CLA 2010-06-08 10:23:33 EDT
(In reply to comment #3)
> tested with manual test log (the ones inside testnavigator.tests)
> 
> i can not reproduce part 1/2/3
> 
> for part 4/5/6, i can only reproduce it when test log is in a project imported
> from another workspace (see bugzilla 315093)
> 
> if test log project is in the current workspace, i can not reproduce part 4/5/6
> 
> i'd be tempted to mark it as duplicate of 315093 but i would need more
> precision before :
> 
> . what kind of test did you used ?
> . what was the project hierarchy ?
> 
> simpler would be to attach the workspace you used + saying me operation you
> done (witch test log was moved in what folder)
> 
> many thanks in advance
> 
> Jerome

Ok I tried to reproduce it and it can occur constantly on one of my machines but not the other, both have the exact same setup. 

How I encountered this symptom is simply create a java project and a folder inside it, create a URL test, right click on the test and choose report, generate a test pass report and try to move it to the folder or try to remove it.
Comment 5 Ben Chen CLA 2010-06-08 10:24:42 EDT
Created attachment 171406 [details]
ss

Ok I cannot even export the workspace now as shown in the SS. It might not be a tptp problem.
Comment 6 Bozier jerome CLA 2010-06-08 10:56:02 EDT
seeing your error snapshot, i think i understand the problem
it seems that the workspace you are using have been changed outside eclipse.
so, eclipse have a resource model that does not match with the physical files on your disk
it can explain why exceptions are raised on move / remove of object (we access physical files to read them to construct proxy)

try this :
. select all your projects
. right click => refresh
. wait until all rebuild are done (if any rebuild is needed)
. retry to reproduce the bug
Comment 7 Ben Chen CLA 2010-06-08 11:04:38 EDT
(In reply to comment #6)
> seeing your error snapshot, i think i understand the problem
> it seems that the workspace you are using have been changed outside eclipse.
> so, eclipse have a resource model that does not match with the physical files
> on your disk
> it can explain why exceptions are raised on move / remove of object (we access
> physical files to read them to construct proxy)
> 
> try this :
> . select all your projects
> . right click => refresh
> . wait until all rebuild are done (if any rebuild is needed)
> . retry to reproduce the bug

Thanks for the comment, however, the steps you provided does not prevent the symptom.
Comment 8 Paul Slauenwhite CLA 2010-06-22 10:15:46 EDT
This requires the container to be refreshed in the workspace after the report is generated.
Comment 9 Paul Slauenwhite CLA 2010-06-22 13:56:47 EDT
Of interested but not formally requested by a consuming product.  As such, a candidate defect for TPTP 4.7.0.1.
Comment 10 Paul Slauenwhite CLA 2010-06-23 08:27:15 EDT
Since the consuming products do not use this reporting infrastructure and the work-around is to refresh the workspace to pick up the new files on the local file system, we will defer this defect.
Comment 11 Paul Slauenwhite CLA 2010-11-26 07:28:29 EST
Insufficient resources to complete.
Comment 12 Kathy Chan CLA 2011-02-11 13:41:06 EST
This defect had been resolved as WONTFIX for more than 1 month.  Closing this on the reporter's behalf.  Please re-open if you have further comment on this issue.
Comment 13 Kathy Chan CLA 2011-02-11 14:51:30 EST
Closed in TPTP 4.7.2.