Bug 415121 - SeparateVMTests.testPropertySubstitution failed in M-build
Summary: SeparateVMTests.testPropertySubstitution failed in M-build
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 4.3   Edit
Hardware: PC Linux-GTK
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: test
Depends on:
Blocks:
 
Reported: 2013-08-15 03:24 EDT by Dani Megert CLA
Modified: 2019-11-27 07:30 EST (History)
1 user (show)

See Also:

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 Dani Megert CLA 2013-08-15 03:24:17 EDT 
M20130814-0800.

http://download.eclipse.org/eclipse/downloads/drops4/M20130814-0800/testresults/html/org.eclipse.ant.tests.ui_linux.gtk.x86_6.0.html


Program did not suspend, and unable to terminate launch.

junit.framework.AssertionFailedError: Program did not suspend, and unable to terminate launch.
at org.eclipse.ant.tests.ui.testplugin.AbstractAntUITest.launchAndWait(AbstractAntUITest.java:468)
at org.eclipse.ant.tests.ui.testplugin.AbstractAntUITest.launchAndTerminate(AbstractAntUITest.java:442)
at org.eclipse.ant.tests.ui.separateVM.SeparateVMTests.testPropertySubstitution(SeparateVMTests.java:180)
at org.eclipse.ant.tests.ui.AbstractAntUIBuildTest.access$0(AbstractAntUIBuildTest.java:1)
at org.eclipse.ant.tests.ui.AbstractAntUIBuildTest$1.run(AbstractAntUIBuildTest.java:44)
at java.lang.Thread.run(Thread.java:662)
Comment 1 Dani Megert CLA 2013-08-15 03:25:04 EDT 
See also bug 414851 for a slightly different failure of the same test.
Comment 2 Dani Megert CLA 2013-08-19 04:38:26 EDT 
Note that it is a different failure than reported in bug 414851.
Comment 3 Dani Megert CLA 2013-08-28 07:00:52 EDT 
Moving out of 4.3.1. We can still backport to 4.3.2 if the fix turns out to be safe.
Comment 4 Lars Vogel CLA 2019-11-27 07:30:51 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.