[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-swt-dev] Bug 498208 - GTK3 build machine test errors for Shell.setAlpha()
|
The test has been fixed with
https://bugs.eclipse.org/bugs/show_bug.cgi?id=498208#c1 , see explanations
there.
Side note: It's a good use of the mailing list to call others' attention
on a bug. However, discussions about a bug are better kept in the bug
report, where everything is in one place and where the commit summary will
point to.
Markus
platform-swt-dev-bounces@xxxxxxxxxxx wrote on 2016-07-21 15:37:22:
> From: Leo Ufimtsev <lufimtse@xxxxxxxxxx>
> To: "Eclipse Platform SWT component developers list."
<platform-swt-dev@xxxxxxxxxxx>
> Date: 2016-07-21 15:37
> Subject: Re: [platform-swt-dev] Bug 498208 - GTK3 build machine test
errors for Shell.setAlpha()
> Sent by: platform-swt-dev-bounces@xxxxxxxxxxx
>
> Looking at the error log from the bug you submitted:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=498208
>
> It seems it's expected 128, but received 255.
> I wonder if this could be a 32/64 bit issue? Are the build servers
32bits?
>
> I also wonder about the valid ranges of alpha, is it always 255, or is
there some circumstance under which it is 128?
>
> fyi:
> Error log:
>
http://download.eclipse.org/eclipse/downloads/drops4/N20160719-2000/testresults/html/org.eclipse.swt.tests_ep47N-unit-lin64_linux.gtk.x86_64_8.0.html#AllNonBrowserTests
>
> Error expected:<128> but was:<255>
> java.lang.AssertionError: expected:<128> but was:<255>
> at
org.eclipse.swt.tests.junit.Test_org_eclipse_swt_widgets_Shell.test_setAlpha(Test_org_eclipse_swt_widgets_Shell.java:584)
> at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:743)
> at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:351)
> at
org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:36)
> at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:32)
> at
org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
> at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
> at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> at org.eclipse.core.launcher.Main.main(Main.java:34)
>
> On Wed, Jul 20, 2016 at 11:58 AM, Eric Williams <ericwill@xxxxxxxxxx>
wrote:
> Hello,
>
> As part of a fix for bug 497707, I wrote a test case for
Shell.setAlpha(). This creates a shell, tests the alpha, then sets it,
then tests again.
>
> For some reason this test is failing on the build machine but not on my
local machine. I've tested with all versions of GTK3 back to 3.6 as well
as GTK2.24 and it passes, no errors to be seen.
>
> Is there something specific to build machine that could be causing this?
Maybe a lack of a compositing manager running (or something similar)?
>
> Thanks,
> Eric
> _______________________________________________
> platform-swt-dev mailing list
> platform-swt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
>
>
> --
> Leo Ufimtsev | Associate Software Engineer @ Red
Hat_______________________________________________
> platform-swt-dev mailing list
> platform-swt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
