Created attachment 25081 [details]
Log

"Special InputOutput to log into NbTestCase.getLog files. In case of failure 
can help find out what went wrong in the build files" 
 
Checking in nbproject/project.properties; 
/cvs/apisupport/project/nbproject/project.properties,v  <--  
project.properties 
new revision: 1.18; previous revision: 1.17 
done 
RCS 
file: /cvs/apisupport/project/test/unit/src/META-INF/services/org.openide.windows.IOProvider,v 
done 
Checking in test/unit/src/META-INF/services/org.openide.windows.IOProvider; 
/cvs/apisupport/project/test/unit/src/META-INF/services/org.openide.windows.IOProvider,v  
<--  org.openide.windows.IOProvider 
initial revision: 1.1 
done 
RCS 
file: /cvs/apisupport/project/test/unit/src/org/netbeans/modules/apisupport/project/InputOutputProviderImpl.java,v 
done 
Checking in 
test/unit/src/org/netbeans/modules/apisupport/project/InputOutputProviderImpl.java; 
/cvs/apisupport/project/test/unit/src/org/netbeans/modules/apisupport/project/InputOutputProviderImpl.java,v  
<--  InputOutputProviderImpl.java 
initial revision: 1.1 
done 
Checking in 
test/unit/src/org/netbeans/modules/apisupport/project/TestBase.java; 
/cvs/apisupport/project/test/unit/src/org/netbeans/modules/apisupport/project/TestBase.java,v  
<--  TestBase.java 
new revision: 1.21; previous revision: 1.20 
 

OK, will reopen w/ more logs if I see it again.

Failed again. I don't think it's random; just doesn't pass for me. All I do is
run nbbuild/misc/full-build-linux.sh with testedmodule=apisupport/project.
Failure result did not include any additional info as compared to last time; I
searched around for any log files or anything, but nothing.

Are you testing it under JDK 1.4?

I've seen the failure, but only few times. Usually it works for me. Somehow 
the test continues without executing the build scripts, I do not know why. If 
you can reproduce the failure in 100% of cases then you could tell me what 
happens after ActionProvider.invokeAction. For logging I use 
NbTestCase.getLog("name of the output tab").  

The same for me. So far everytime I run it. See attached output log. Runned with:

ant
-Dtest.includes=org/netbeans/modules/apisupport/project/jnlp/GenerateJNLPApplicationTest.java
-f apisupport/project/build.xml netbeans test-single

from NB_CVS_ROOT.

Created attachment 25183 [details]
failed_GenerateJNLPApplicationTest.txt

Guys, this is not the log file. The log file should contain the output of the 
ant. Can't you really do 
 
cd apisupport/project/test 
ant 
 
and sent me the failure? 

Doesn't worth it. It looks exactly the same like my previous log + success in
percentage (50%). If you really want it, just do s/[junit]/[jvmTestRunner] on
the previous attachment.
Did you really tried it with the fresh build? It really happens in 100% cases.

You closed it?

"#64940: Waiting for the build process to finish" 
 
 
Checking in 
project/src/org/netbeans/modules/apisupport/project/ui/SuiteActions.java; 
/cvs/apisupport/project/src/org/netbeans/modules/apisupport/project/ui/SuiteActions.java,v  
<--  SuiteActions.java 
new revision: 1.9; previous revision: 1.8 
done 
RCS 
file: /cvs/apisupport/project/test/unit/src/META-INF/services/org.openide.ErrorManager,v 
done 
Checking in project/test/unit/src/META-INF/services/org.openide.ErrorManager; 
/cvs/apisupport/project/test/unit/src/META-INF/services/org.openide.ErrorManager,v  
<--  org.openide.ErrorManager 
initial revision: 1.1 
done 
RCS 
file: /cvs/apisupport/project/test/unit/src/org/netbeans/modules/apisupport/project/ErrorManagerImpl.java,v 
done 
Checking in 
project/test/unit/src/org/netbeans/modules/apisupport/project/ErrorManagerImpl.java; 
/cvs/apisupport/project/test/unit/src/org/netbeans/modules/apisupport/project/ErrorManagerImpl.java,v  
<--  ErrorManagerImpl.java 
initial revision: 1.1 
done 
Checking in 
project/test/unit/src/org/netbeans/modules/apisupport/project/InputOutputProviderImpl.java; 
/cvs/apisupport/project/test/unit/src/org/netbeans/modules/apisupport/project/InputOutputProviderImpl.java,v  
<--  InputOutputProviderImpl.java 
new revision: 1.3; previous revision: 1.2 
done 
Checking in 
project/test/unit/src/org/netbeans/modules/apisupport/project/TestBase.java; 
/cvs/apisupport/project/test/unit/src/org/netbeans/modules/apisupport/project/TestBase.java,v  
<--  TestBase.java 
new revision: 1.22; previous revision: 1.21 
done 
Checking in 
project/test/unit/src/org/netbeans/modules/apisupport/project/jnlp/GenerateJNLPApplicationTest.java; 
/cvs/apisupport/project/test/unit/src/org/netbeans/modules/apisupport/project/jnlp/GenerateJNLPApplicationTest.java,v  
<--  GenerateJNLPApplicationTest.java 
new revision: 1.3; previous revision: 1.2 
 
 

Nope, still fails for me. Clean build on dev sources, JDK 1.4.

Created attachment 25336 [details]
Current failure log

Created attachment 25337 [details]
The detailed log file, now available in work dir (is this what you were looking for before? first time I've seen it)

...but sometimes passes - with a lot of printed errors (will attach).

Created attachment 25339 [details]
Test output (XTest mode, clean dev build, JDK 1.4)

*** Issue 66485 has been marked as a duplicate of this issue. ***

Created attachment 25896 [details]
Log from the failure, Jesse can you see what is wrong there?

The problem is that SuiteActions.promptForName gets null value when calling  
 
project.getEvaluator().getProperty("app.name") 
 
I guess there are some threading issues with the way project.getEvaluator 
works as the test correctly stores the value before it calls the "build-jnlp" 
action. 
 
Jesse, as you have much deeper insite into the threading of apisupport, can 
you fix or suggest a fix for the code or the test? 

Not failing consistently, just sometimes.

BTW I noticed this test even when it passes takes a ridiculously long time
(several minutes); looking at ps fauxwww and system monitor, seems that
jarsigner just sits there for a while doing apparently nothing.

Re. slow: move your mouse while the test is running, it can finish in 30s. 
Probably it needs a lot of random input for SecureRandom... 

Checking in GenerateJNLPApplicationTest.java;
/cvs/apisupport/project/test/unit/src/org/netbeans/modules/apisupport/project/jnlp/GenerateJNLPApplicationTest.java,v
 <--  GenerateJNLPApplicationTest.java
new revision: 1.5; previous revision: 1.4
done

Storing content to project.properties directly using FileObject *will* trigger a
change in the evaluator, but perhaps not synchronously. Best to use
APH.get/putProperties methods which are the project's internally loaded state.

passes for me ok now on SOL.