Summary: | [1.5][compiler] Multiple auto-build failures when using generics | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Kory Markevich <vulcannis> |
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | mlists |
Version: | 3.1 | ||
Target Milestone: | 3.1 RC2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: | |||
Attachments: |
Description
Kory Markevich
2005-05-01 19:01:30 EDT
Created attachment 20572 [details]
Project for bug
A ZIP file of the project for this bug entry.
Just to note, I listed the bugs in my idea of severity. In my full project the first bug manifests most commonly. Making a change to just about any file will cause it to occur, which means that I have to turn auto-build off to get anything done. I realize that these may be separate bugs and thus warrant separate entries; if so, would I attach the project to each one or just point back to the first entry...? Maxime - pls try to reproduce in latest Could reproduce all bugs on I20050426-1700. As of 3.1 RC1 (I20050527-1300): - Bug 1 and Bug 4 type bugs cannot be reproduced; the latter might be masked by Bug 2 type bugs; - Bug 2 type bugs (that is, auto build raises undue errors, clean build gets rid of them) are observed on files: ClientGame.java Game.java HostGame.java Participant.java Phase.java StateManager.java StateStore.java (most frequent error message is 'Bound mismatch...', but others occur as well); - Bug 5 still there. I would suggest that Bug 5 be separated in a distinct bug, since it behaves the same in auto build and clean build, hence should be observable from a batch compiler point of view. Segregated bug 5 into a new bug, https://bugs.eclipse.org/bugs/show_bug.cgi?id=97494. Created attachment 22053 [details]
Batch compiler test case that shows one of the errors
Fixing this error may or may not be sufficient to fix the bug.
_test30 must be renamed to test30 to be executed.
Note that getting rid of the third type parameter on X (and applying needed
cascaded changes) suppresses the faulty behavior.
Created attachment 22128 [details]
Batch compiler test case that covers more of the original
This is still simplified a bit compared to the original test case, but more
errors are raised than with 22053. Added for the sake of better coverage.
Created attachment 22412 [details] Batch compiler test cases upgraded for HEAD These tests run OK with build N20050603-0010. The same build runs OK against the test case provided in comment #1, except that no extra investigation has been made for bug 5, tracked separately. I would suggest that this bug be considered as fixed. Olivier - pls integrate Maxime tests, and tag as fixed. Fixed and released in HEAD. Regression tests added in org.eclipse.jdt.core.tests.compiler.regression.BatchCompilerTest.test030/test032 Verified for 3.1RC2 using build N20050607-0010 + JDT/COre HEAD Verified for 3.1 RC2 using build I20050610-0010 |