| Summary: | Running platform Debug tests logs spurious entries in console | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Michael Rennie <Michael_Rennie> |
| Component: | Debug | Assignee: | Pawel Piech <pawel.1.piech> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | pawel.1.piech |
| Version: | 3.7 | Flags: | Michael_Rennie:
review+
|
| Target Milestone: | 3.7 M6 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Michael Rennie
Hi Mike, Could you run the test with tracing turned on for debug/viewers/contentProvider, deubg/viewers/updateSequence, debug/viewers/delta? The trace will be pretty long so please attach it. Thanks, Pawel I tried to take a tracing of the exception, but when I enabled tracing the exception did not occur. I should also note that the exception is present in the latest I-build console logs for Linux as well. http://download.eclipse.org/eclipse/downloads/drops/I20110222-0800/testresults/linux.gtk.x86_6.0/org.eclipse.debug.tests.AutomatedSuite.txt I can't reproduce the problem locally, so it seems I have no choice but to throw stuff at the wall as see what sticks. I committed one change in the LazyTests to try to avoid the error, we'll see if it cures the nightly test woes. I tracked this problem down to incorrect assumptions about label updated by the tests. Specifically, the label provider can issue multiple sequences of label udpates, even during a single sequence of content updates. I fixed the tests not to assume a single label update sequence. Mike, please try the updated tests. Running the test suite 4 times today I did not see the exceptions. verified. |