| Summary: | Draw2d TextFlowWrapTests fail after switching to latest 4.2-I build | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Alexander Nyßen <nyssen> |
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | eclipse.felipe, ericwill, gheorghe, psuzzi, remy.suen |
| Version: | 4.2 | Keywords: | triaged |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux-GTK | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 369570 | ||
|
Description
Alexander Nyßen
I validated that on my local machine (Mac OS X) everything is still working. Using the latest 3.8 i-build there are no test failures, as you can observe on hudson.eclipse.org (I changed gef-nightly-tycho #157 to build against 3.8), so its a regression as well as a compatibility problem. I don't think anything change in SWT between I20120127 to I20120207. Bogdan ? Can we get a SWT snippet that shows the regression ? Thank you (In reply to comment #3) > I don't think anything change in SWT between I20120127 to I20120207. Bogdan ? Well, I suppose it has to be some sort of regression. Up to gef-nightly-tycho build #153, everything worked fine. Beginning with build #154 it started to fail. Interestingly, the target that was used seemed to point to org.eclipse.sdk.ide version 4.2.0.I20120207-2200 in both cases (on http://download.eclipse.org/eclipse/updates/4.2-I-builds)? As such, I suppose the update site has changed in between and a newer target was picked for #154. However, I do not now which exactly. Interestingly, I could not reproduce the effect in my local Linux VM (Ubuntu 10.04 LTS) using x86-64, GTK version of I20120209-2200 as well as I20120210-1700. Interestingly, we had two builds in between (#181 and #185), where the tests succeeded, where there haven't been any changes. Seems to be kind of a sporadic issue. Could anybody already take a look into the details and has an idea what this could be caused by? Closing this due to age, please reopen this bug if the issue occurs on 4.9 with GTK3.22. |