-
Bug
-
Resolution: Won't Fix
-
P5
-
None
-
8u40, 9
-
windows
The set of smoke tests that are run by default with "gradle test" should finish in less than 5 minutes on a typical machine. The fxpackager Windows bundler tests on Windows platforms take longer than that by themselves. I think it would be best to exclude these tests from the default test run and only run them as part of the full test run: "gradle -PFULL_TEST=true test".
Here is the data from my system from a recent build of 9-dev:
WinExeBundlerTest 15 0 4m22.88s
WinMsiBundlerTest 16 0 3m14.08s
WinServiceBundlerTest 7 0 1m26.48s
WinAppBundlerTest 8 0 9.873s
for a total of 9:13. On my Mac (admittedly a somewhat faster machine), the entire set of tests in com.oracle.tools.packager.mac takes just under 2 minutes, which is about the limit of what I would like the default set of tests to take for fxpackager (the web module is the second longest at just over 1 minute on my mac).
Here is the data from my system from a recent build of 9-dev:
WinExeBundlerTest 15 0 4m22.88s
WinMsiBundlerTest 16 0 3m14.08s
WinServiceBundlerTest 7 0 1m26.48s
WinAppBundlerTest 8 0 9.873s
for a total of 9:13. On my Mac (admittedly a somewhat faster machine), the entire set of tests in com.oracle.tools.packager.mac takes just under 2 minutes, which is about the limit of what I would like the default set of tests to take for fxpackager (the web module is the second longest at just over 1 minute on my mac).
- relates to
-
JDK-8151635 [packager] Get Unit Tests Running
- Closed