Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Attention needed for M3 based builds

I'm a little unsure as to what action is required here. The compile error count >0 in the summary page, but then the list of plugins with errors contains none that have a compile error count >0. None of the jsf plugins that are listed show warnings indicating either pre-req range warnings (we don't presently use pre-req ranges on plugin pre-reqs) nor are there any implying internal use warnings.

The one I'm looking at is: http://download.eclipse.org/webtools/committers/drops/R2.0/I-I200610311621-200610311621/testResults.php

Is there somewhere else I need to look?


--Cam

David M Williams wrote:


There's two issues with us moving up to M3.

1. Many Plugins need pre-req range fixed <https://bugs.eclipse.org/bugs/show_bug.cgi?id=162842>

I fixed these up in a minimal way, but see bug 162842 for other actions you may need to make.

2. Some of our "internal use" is back to haunt us. Some changes with "search internals" will cause compile errors. This is a good time for you to put in permanent fixes ... Craig. :)
Please check compile logs >= 10/31.

Also,
The massive failures in JUnit plugins are being investigated by the experts (i.e. Naci) It seems to be only the "UI tests" that are failing ... so, I suspect, something's changed with our Xvfb server
on our build machine.

------------------------------------------------------------------------

_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev



Back to the top