Em 17-07-2013 12:08, Fernando de Oliveira escreveu: ...
> ... disabled 8 tests at > > java/awt/FullScreen: > > java/awt/FullScreen/SetFSWindow/FSFrame.java > java/awt/FullScreen/TranslucentWindow/TranslucentWindow.java > java/awt/FullScreen/FullScreenInsets/FullScreenInsets.java > java/awt/FullScreen/MultimonFullscreenTest/MultimonFullscreenTest.java > java/awt/FullScreen/BufferStrategyExceptionTest/BufferStrategyExceptionTest.java > java/awt/FullScreen/NoResizeEventOnDMChangeTest/NoResizeEventOnDMChangeTest.java > java/awt/FullScreen/UninitializedDisplayModeChangeTest/UninitializedDisplayModeChangeTest.java > java/awt/FullScreen/UninitializedDisplayModeChangeTest/DisplayModeChanger.java > > Now, I can bisect ... And the winner is the first one: java/awt/FullScreen/SetFSWindow/FSFrame.java Disabling just this, tests are already ahead of the hung point. Now, have to add that line to the tests patch and produce and the diff for the book. Is that all right with you, Bruce? Later, I will leave the test running in the 64bit machine, with the new patch. The version is going to be 1.7.40-2.4.1 and OpenJDK and About Java will change. How do I write it in the xml? <!ENTITY icedtea-version "2.4.1"> <!ENTITY openjdk-version "1.7.0.40-&icedtea-version;"> Is that correct? ... > export DISPLAY=:20 && > Xvfb :20 -screen 0 1x1x24 -ac& > echo $!> Xvfb.pid && > #make jtregcheck -k && > time make -k jtregcheck && > kill -9 `cat Xvfb.pid` && > unset DISPLAY && > rm -f Xvfb.pid Shall a put this as is, too? Or let it to be done later? -- []s, Fernando -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
