If the failures are:
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running
org.eclipse.wst.jsdt.core.tests.compiler.JSDTCompilerTests
Tests run: 873, Failures: 11, Errors: 0, Skipped: 0, Time
elapsed: 48.702 sec <<< FAILURE!
Results :
Failed tests:
test02(org.eclipse.wst.jsdt.core.tests.compiler.parser.DualParseSyntaxErrorTest):
Invalid syntax error diagnosis<test2>.
test04(org.eclipse.wst.jsdt.core.tests.compiler.parser.DualParseSyntaxErrorTest):
Invalid syntax error diagnosis<test4>.
test05(org.eclipse.wst.jsdt.core.tests.compiler.parser.DualParseSyntaxErrorTest):
Invalid syntax error diagnosis<test5>.
test06(org.eclipse.wst.jsdt.core.tests.compiler.parser.DualParseSyntaxErrorTest):
Invalid syntax error diagnosis<test6>.
test07(org.eclipse.wst.jsdt.core.tests.compiler.parser.DualParseSyntaxErrorTest):
Invalid syntax error diagnosis<test7>.
test08(org.eclipse.wst.jsdt.core.tests.compiler.parser.DualParseSyntaxErrorTest):
Invalid syntax error diagnosis<test8>.
test09(org.eclipse.wst.jsdt.core.tests.compiler.parser.DualParseSyntaxErrorTest):
Invalid syntax error diagnosis<test9>.
test10(org.eclipse.wst.jsdt.core.tests.compiler.parser.DualParseSyntaxErrorTest):
Invalid syntax error diagnosis<test10>.
test01(org.eclipse.wst.jsdt.core.tests.compiler.parser.SyntaxErrorTest):
Invalid syntax error diagnosis<parenthesis mismatch>.
test02(org.eclipse.wst.jsdt.core.tests.compiler.parser.SyntaxErrorTest):
Invalid syntax error diagnosis<brace mismatch>.
testWI106610(org.eclipse.wst.jsdt.core.tests.compiler.parser.SyntaxErrorTest):
Invalid syntax error diagnosis<test>.
then the reason is the combination of the following issues:
-
https://bugs.eclipse.org/bugs/show_bug.cgi?id=420333
(Remove JSDT semantic validation) - for these certain tests the
semantic validation should be turned on before the test starts;
-
https://bugs.eclipse.org/bugs/show_bug.cgi?id=424131
(
JSDT Parser doesn't respect
"Enable Semantic Validation" preference value) - probably
the fix I've proposed is not correct and hides
more error statuses than it should.
Anyway, these test failures IMHO are not a show-stoppers. They
are indicating that some errors/warnings aren't shown to a user
when JSDT Semantic Validation is turned off (while this is a new
default value for this preference).
I can (and I will) look more detailed / fix these errors after
January 8. If somebody can do it earlier - welcome - and please
review the fix done for #424131 first. May be I've made
something wrong there.
Thanks in advance,
Victor Rubezhny
On 01/04/2014 01:07 AM, Thanh Ha wrote:
