This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 81623 - Progress handle for killed build left open
Summary: Progress handle for killed build left open
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: junit-issues@java
URL:
Keywords: RANDOM
Depends on: 82160
Blocks:
  Show dependency tree
 
Reported: 2006-08-01 18:50 UTC by Jesse Glick
Modified: 2006-10-23 16:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

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 Jesse Glick 2006-08-01 18:50:06 UTC 
If you run all tests for a NB module project, and use Build | Stop Building to
halt it partway through, the JUnit progress handle "Running JUnit tests..."
remains visible, and cannot be removed except by restarting the IDE.
Comment 1 Marian Petras 2006-08-03 15:30:53 UTC 
Reproduced.

Before I committed the source code progress bar, I tried the scenario that the
process is stopped - and it worked as expected. But I always did it using action
"Terminate Process" action on a node selected in the Runtime view.

If I stop the build using the Stop Build/Run action, it does not work.

The reason is that if I stop the process using the Terminate Process action, the
JUnitAntLogger's method buildFinished(...) gets called. If the process is
terminated using the Stop Build/Run action, the method does not get called. I am
affraid I cannot fix unless buildFinished(...) gets called.

Jesse, if I understand correctly, you participated in both the actions for
stopping processes ("Terminate Process" and "Stop Build/Run"). Is it correct
that buildFinished(...) does not get called?
Comment 2 Jesse Glick 2006-08-03 20:44:08 UTC 
I only used Stop Build/Run. I have noticed however that it sometimes works.

SBR can work in one of two ways:

1. If some Ant event occurs within 3 seconds (I think), a BuildException is
thrown, which should cause the build to halt.

2. Otherwise, Thread.stop is called, generally interrupting the running task.

So the difference may depend on how long an individual test takes to run.

Not sure if buildFinished is called in case #2.
Comment 3 Marian Petras 2006-08-11 15:40:52 UTC 
This bug was caused by bug #82160 which was just fixed so I mark this bug as
fixed, too. Tested on a custom build 060811.