Community
Participate
Working Groups
The following automated tests in TextFlowWrapTest fail. They have been commented out for now. // General tests doTest2(" foobar", "abc", " foobarab", new String[] {"", NEWLINE, "foobar"}); doTest2("abd", "\u7325", "abd", new String[] {"abd", NEWLINE, "\u7325"}); // soft-wrapping doTest2("foofoo", "foo", "foo", new String[] {"foo", NEWLINE, "foo", NEWLINE, "foo", TERMINATE}); doTest2("foofo", "ofoo", "foo", new String[] {"foo", NEWLINE, "fo", SAMELINE, "o", NEWLINE, "foo", TERMINATE});
One of the tests in TextFlowWrapTest now fails on the build machine. Also commented out for now. doTest2("foo7-bar7", "mo", "foo7-ba", new String[] {"foo7-", NEWLINE, "bar7", SAMELINE, "mo", TERMINATE}); The test works fine on Windows but fails on Linux. There are also six other tests commented out not called out on this Bugzilla.
(In reply to comment #1) > One of the tests in TextFlowWrapTest now fails on the build machine. Given Ubuntu is not *officially* supported, you should perhaps enable these tests and try them on the other build server, which has FC5 on it. http://emft.eclipse.org/gef/downloads/?sortBy=date http://emft.eclipse.org/gef/build/ (contact me if you're a GEF developer & don't have the username/password for this page - see http://wiki.eclipse.org/User:Nickb) GEF N builds run on both machines every day, but I builds are published from the emf.toro server because of IES and CHKPII requirements. If you want to start publishing from the emft.eclipse server, you'll have to start updating the IES mapfile by hand. Anthony: Which is more useful? a) Running these tests w/ every build, publishing a FC-based build tht omits CHKPII testing and requires manually updating the IES mapfile? - or - b) Omitting them, running on Ubuntu, doing CHKPII testing (which almost never fails) and automatically updating the IES mapfile as part of a promote?
(In reply to comment #2) > b) Omitting them, running on Ubuntu, doing CHKPII testing (which almost never > fails) and automatically updating the IES mapfile as part of a promote? Keep the current build setup unless you want to change it (you are responsible for the IES mapfiles :-).
See bug 224660 and 224663. Might have a way around this one.
