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 196642 - Cannot incrementally run tests
Summary: Cannot incrementally run tests
Status: RESOLVED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Harness (show other bugs)
Version: 7.0.1
Hardware: PC Linux
: P2 normal (vote)
Assignee: Jesse Glick
URL:
Keywords: REGRESSION
: 197941 (view as bug list)
Depends on: 196779 197113 200055
Blocks:
  Show dependency tree
 
Reported: 2011-03-13 14:19 UTC by Jan Lahoda
Modified: 2011-07-11 17:20 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Test project. (9.14 KB, application/zip)
2011-03-13 14:19 UTC, Jan Lahoda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Lahoda 2011-03-13 14:19:36 UTC
Created attachment 106952 [details]
Test project.

Product Version: NetBeans IDE Dev (Build 110313-107ad57a12d9)
Java: 1.6.0_20; OpenJDK 64-Bit Server VM 19.0-b09
System: Linux version 2.6.35-25-generic running on amd64; UTF-8; en_US (nb)
Userdir: /tmp/nbuser

Steps to reproduce:
1. Download the attached example project, unpack, open both suite1 and module1
2. Open class "A" from the module1 project.
3. Test File (Ctrl-F6) - passes.
4. Do a dummy modification to the "A" class (e.g. a modification in a comment).
5. Test File again - fails with:

do-unit-test-build:
/usr/local/home/lahvac/src/nb/outgoing/nbbuild/netbeans/harness/common.xml:594: The following error occurred while executing this line:
/usr/local/home/lahvac/src/nb/outgoing/nbbuild/netbeans/harness/common.xml:584: 
java.io.IOException: /tmp/suite1/build/cluster/modules/o-t-m1.jar is not the same as /tmp/suite1/build/testdist/extralibs/o-t-m1.jar; will not overwrite
	at org.netbeans.nbbuild.ShorterPaths.copyExtraLib(ShorterPaths.java:284)
	at org.netbeans.nbbuild.ShorterPaths.simplyPath(ShorterPaths.java:248)
	at org.netbeans.nbbuild.ShorterPaths.execute(ShorterPaths.java:163)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
	at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
	at org.apache.tools.ant.Task.perform(Task.java:348)
	at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
	at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
	at org.apache.tools.ant.Task.perform(Task.java:348)
	at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:398)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
	at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
	at org.apache.tools.ant.Task.perform(Task.java:348)
	at org.apache.tools.ant.Target.execute(Target.java:390)
	at org.apache.tools.ant.Target.performTasks(Target.java:411)
	at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
	at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
	at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
	at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
	at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:284)
	at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:539)
	at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:154)
BUILD FAILED (total time: 0 seconds)
Comment 1 Jan Lahoda 2011-03-13 19:36:08 UTC
Does not affect 7.0, AFAIK.
Comment 2 Jesse Glick 2011-03-14 19:00:21 UTC
Immediate cause is bab969793f5c but real problem is that a module JAR is being copied to extralibs at all - possibly long broken.
Comment 3 Jesse Glick 2011-03-14 19:57:12 UTC
core-main #177a4676720e
Comment 4 Quality Engineering 2011-03-15 09:47:00 UTC
Integrated into 'main-golden', will be available in build *201103150400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/177a4676720e
User: Jesse Glick <jglick@netbeans.org>
Log: #196642: incremental test runs broken for external modules.
Should not have been creating testdist artifacts since this is supported only for nb.org modules.
Comment 5 Jesse Glick 2011-04-27 07:22:17 UTC
*** Bug 197941 has been marked as a duplicate of this bug. ***
Comment 6 Jan Lahoda 2011-05-30 16:03:46 UTC
Still happens for me for:
-contrib modules (e.g. contrib/javahints and contrib/java.ext.editor)
-modified nb-javac (running e.g. java.hints tests, when libs.javacimpl/external/javac-impl-nb-7.0-b07.jar between two "incremental" runs of the tests)
Comment 7 Jesse Glick 2011-05-31 21:19:21 UTC
(In reply to comment #6)
> Still happens for me for...

Sounds like a different use case than originally reported -> should be filed separately. Probably not a P2 since I guess just cleaning the test build dir suffices, and changing a binary Class-Path extension of some dep is much less common than changing module source code.
Comment 8 Jan Lahoda 2011-07-11 13:31:42 UTC
FYI: I have added a workaround for this into contrib/{javahints|java.ext.editor} and will add analogous one into nb-javac if annoying enough.
Comment 9 Jesse Glick 2011-07-11 14:10:13 UTC
(In reply to comment #8)
> I have added a workaround for this

Workaround for what? This issue is FIXED. If you are still observing some issue, please file a separate bug with steps to reproduce.
Comment 10 Jan Lahoda 2011-07-11 14:31:06 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > I have added a workaround for this
> 
> Workaround for what? This issue is FIXED. If you are still observing some

Workaround for unability to "incrementally" run tests for contrib/{javahints|java.ext.editor} tests, as said in comment#6.

> issue, please file a separate bug with steps to reproduce.

I have reopened this one, and assumed that you will create a new one yourself when you were closing it again with some use cases unsolved. I can file it myself, if you prefer.
Comment 11 Jesse Glick 2011-07-11 15:25:25 UTC
(In reply to comment #10)
> I can file it myself, if you prefer.

Yes please, as requested in comment #7.