[JBoss JIRA] (JBDS-4089) Skip unit/ui tests not related to current platform/arch
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4089?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4089.
-----------------------------
True that.
> Skip unit/ui tests not related to current platform/arch
> -------------------------------------------------------
>
> Key: JBDS-4089
> URL: https://issues.jboss.org/browse/JBDS-4089
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.GA
>
>
> Current UI tests are specific for windows. When installer supports Mac OS X there will be failures when UI tests are running on Mac. For example verification for Drive in selected path is valid only on Windows.
> this.skip() call does not work for protractor tests, because it still considered as a failure. Second option would be do not run tests that are not valid for current platform at all. That could be done ether by direct check in tests like
> {code}
> if(process.platform === 'win32') {
> it('test desctription', function(){
> // test instructions
> });
> }
> {code}
> or we can move platform specific tests in files with platform specific suffix and include them using process.platform and process.arch values at gulp execution time.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBTIS-996) Fuse: Fix bug in tests - handling Open Perspective dialog in project creation
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-996?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-996.
-----------------------------------
pushed to master
> Fuse: Fix bug in tests - handling Open Perspective dialog in project creation
> -----------------------------------------------------------------------------
>
> Key: JBTIS-996
> URL: https://issues.jboss.org/browse/JBTIS-996
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE, QE
> Affects Versions: 4.4.0.Final
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Priority: Critical
> Fix For: 4.4.0.Final
>
> Attachments: Screenshot from 2016-11-28 10-49-57.png
>
> Original Estimate: 1 hour
> Time Spent: 30 minutes
> Remaining Estimate: 30 minutes
>
> I hit an issue with _ConfigurationsEditorDataFormatsTest_. Project creation in before test fails with
> {code}
> org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 900 s.: shell with title matching Matcher matching widget which text matches: "New Fuse Integration Project" is available
> at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:183)
> at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:136)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:101)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:71)
> at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:56)
> at org.jboss.reddeer.common.wait.WaitWhile.<init>(WaitWhile.java:45)
> at org.jboss.reddeer.jface.wizard.WizardDialog.finish(WizardDialog.java:69)
> at org.jboss.tools.fuse.ui.bot.test.utils.ProjectFactory.create(ProjectFactory.java:79)
> at org.jboss.tools.fuse.ui.bot.test.ConfigurationsEditorDataFormatsTest.setupData(ConfigurationsEditorDataFormatsTest.java:115)
> {code}
> (also see attached screenshot)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-470) Unable to list image tags on DockerHub [EBZ#508282]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-470:
---------------------------------------
Summary: Unable to list image tags on DockerHub [EBZ#508282]
Key: ERT-470
URL: https://issues.jboss.org/browse/ERT-470
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.2 (4.6)
It seems like the '/v1/' endpoint has been removed, resulting in an empty list of tags in the "Search Images" wizard.
But there's hope. The Docker Hub registry now runs on the '/v2' endpoint but requires authentication:
curl https://index.docker.io/v2/jboss/wildfly/tags/list -v
* Trying 54.85.12.131...
* Connected to index.docker.io (54.85.12.131) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.docker.io
* Server certificate: RapidSSL SHA256 CA - G3
* Server certificate: GeoTrust Global CA
> GET /v2/jboss/wildfly/tags/list HTTP/1.1
> Host: index.docker.io
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 401 Unauthorized
< Content-Type: application/json; charset=utf-8
< Docker-Distribution-Api-Version: registry/2.0
< Www-Authenticate: Bearer realm="https://auth.docker.io/token",service="registry.docker.io",scope="repository:jboss/wildfly:pull"
< Date: Mon, 28 Nov 2016 10:29:37 GMT
< Content-Length: 145
< Strict-Transport-Security: max-age=31536000
<
{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Name":"jboss/wildfly","Action":"pull"}]}]}
The request above failed because not auth token was provided, but the registry returned a special 'Www.Authenticate' response header which points to the authentication service to call, along with the parameters to provide:
curl -v https://auth.docker.io/token\?service\=registry.docker.io\&scope\=reposit...
* Trying 52.72.61.89...
* Connected to auth.docker.io (52.72.61.89) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.docker.io
* Server certificate: RapidSSL SHA256 CA - G3
* Server certificate: GeoTrust Global CA
> GET /token?service=registry.docker.io&scope=repository:jboss/wildfly:pull HTTP/1.1
> Host: auth.docker.io
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Mon, 28 Nov 2016 10:29:58 GMT
< Content-Length: 1442
< Strict-Transport-Security: max-age=31536000
<
{"token":"eyJ...Rg"}
Once the token has be retrieved, the first request can be run again, this time with the token:
curl https://index.docker.io/v2/jboss/wildfly/tags/list -v -H "Authorization: Bearer eyJ...Rg"
* Trying 52.207.178.113...
* Connected to index.docker.io (52.207.178.113) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.docker.io
* Server certificate: RapidSSL SHA256 CA - G3
* Server certificate: GeoTrust Global CA
> GET /v2/jboss/wildfly/tags/list HTTP/1.1
> Host: index.docker.io
> User-Agent: curl/7.43.0
> Accept: */*
> Authorization: Bearer eyJ...Rg
>
< HTTP/1.1 200 OK
< Content-Type: application/json; charset=utf-8
< Docker-Distribution-Api-Version: registry/2.0
< Date: Mon, 28 Nov 2016 10:30:13 GMT
< Content-Length: 157
< Strict-Transport-Security: max-age=31536000
<
{"name":"jboss/wildfly","tags":["10.0.0.Final","10.1.0.Final","8.1.0.Final","8.2.0.Final","8.2.1.Final","9.0.0.Final","9.0.1.Final","9.0.2.Final","latest"]}
See https://docs.docker.com/registry/spec/api/#/listing-image-tags
and https://docs.docker.com/registry/spec/auth/token/#/requesting-a-token
The logic to retrieve the list of tags for a given image should check if the registry is a 'v2' and if it needs authentication as described above.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-470) Unable to list image tags on DockerHub [EBZ#508282]
by Friendly Jira Robot (JIRA)
[ https://issues.jboss.org/browse/ERT-470?page=com.atlassian.jira.plugin.sy... ]
Friendly Jira Robot resolved ERT-470.
-------------------------------------
Resolution: Done
> Unable to list image tags on DockerHub [EBZ#508282]
> ---------------------------------------------------
>
> Key: ERT-470
> URL: https://issues.jboss.org/browse/ERT-470
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> It seems like the '/v1/' endpoint has been removed, resulting in an empty list of tags in the "Search Images" wizard.
> But there's hope. The Docker Hub registry now runs on the '/v2' endpoint but requires authentication:
> curl https://index.docker.io/v2/jboss/wildfly/tags/list -v
> * Trying 54.85.12.131...
> * Connected to index.docker.io (54.85.12.131) port 443 (#0)
> * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> * Server certificate: *.docker.io
> * Server certificate: RapidSSL SHA256 CA - G3
> * Server certificate: GeoTrust Global CA
> > GET /v2/jboss/wildfly/tags/list HTTP/1.1
> > Host: index.docker.io
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 401 Unauthorized
> < Content-Type: application/json; charset=utf-8
> < Docker-Distribution-Api-Version: registry/2.0
> < Www-Authenticate: Bearer realm="https://auth.docker.io/token",service="registry.docker.io",scope="repository:jboss/wildfly:pull"
> < Date: Mon, 28 Nov 2016 10:29:37 GMT
> < Content-Length: 145
> < Strict-Transport-Security: max-age=31536000
> <
> {"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":[{"Type":"repository","Name":"jboss/wildfly","Action":"pull"}]}]}
> The request above failed because not auth token was provided, but the registry returned a special 'Www.Authenticate' response header which points to the authentication service to call, along with the parameters to provide:
> curl -v https://auth.docker.io/token\?service\=registry.docker.io\&scope\=reposit...
> * Trying 52.72.61.89...
> * Connected to auth.docker.io (52.72.61.89) port 443 (#0)
> * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> * Server certificate: *.docker.io
> * Server certificate: RapidSSL SHA256 CA - G3
> * Server certificate: GeoTrust Global CA
> > GET /token?service=registry.docker.io&scope=repository:jboss/wildfly:pull HTTP/1.1
> > Host: auth.docker.io
> > User-Agent: curl/7.43.0
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Content-Type: application/json
> < Date: Mon, 28 Nov 2016 10:29:58 GMT
> < Content-Length: 1442
> < Strict-Transport-Security: max-age=31536000
> <
> {"token":"eyJ...Rg"}
> Once the token has be retrieved, the first request can be run again, this time with the token:
> curl https://index.docker.io/v2/jboss/wildfly/tags/list -v -H "Authorization: Bearer eyJ...Rg"
> * Trying 52.207.178.113...
> * Connected to index.docker.io (52.207.178.113) port 443 (#0)
> * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
> * Server certificate: *.docker.io
> * Server certificate: RapidSSL SHA256 CA - G3
> * Server certificate: GeoTrust Global CA
> > GET /v2/jboss/wildfly/tags/list HTTP/1.1
> > Host: index.docker.io
> > User-Agent: curl/7.43.0
> > Accept: */*
> > Authorization: Bearer eyJ...Rg
> >
> < HTTP/1.1 200 OK
> < Content-Type: application/json; charset=utf-8
> < Docker-Distribution-Api-Version: registry/2.0
> < Date: Mon, 28 Nov 2016 10:30:13 GMT
> < Content-Length: 157
> < Strict-Transport-Security: max-age=31536000
> <
> {"name":"jboss/wildfly","tags":["10.0.0.Final","10.1.0.Final","8.1.0.Final","8.2.0.Final","8.2.1.Final","9.0.0.Final","9.0.1.Final","9.0.2.Final","latest"]}
> See https://docs.docker.com/registry/spec/api/#/listing-image-tags
> and https://docs.docker.com/registry/spec/auth/token/#/requesting-a-token
> The logic to retrieve the list of tags for a given image should check if the registry is a 'v2' and if it needs authentication as described above.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-469) ClassCastException in BaseResourceAwareLaunchShortcut.launch [EBZ#508027]
by Friendly Jira Robot (JIRA)
[ https://issues.jboss.org/browse/ERT-469?page=com.atlassian.jira.plugin.sy... ]
Friendly Jira Robot resolved ERT-469.
-------------------------------------
Resolution: Done
> ClassCastException in BaseResourceAwareLaunchShortcut.launch [EBZ#508027]
> -------------------------------------------------------------------------
>
> Key: ERT-469
> URL: https://issues.jboss.org/browse/ERT-469
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> java.lang.ClassCastException: org.python.pydev.navigator.elements.PythonFile cannot be cast to org.eclipse.core.resources.IResource
> at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.launch(BaseResourceAwareLaunchShortcut.java:39)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:431)
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:74)
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:123)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> Bundles:
> | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5827b... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-469) ClassCastException in BaseResourceAwareLaunchShortcut.launch [EBZ#508027]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-469:
---------------------------------------
Summary: ClassCastException in BaseResourceAwareLaunchShortcut.launch [EBZ#508027]
Key: ERT-469
URL: https://issues.jboss.org/browse/ERT-469
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.2 (4.6)
The following problem was reported via the automated error reporting:
Message: Unhandled event loop exception
java.lang.ClassCastException: org.python.pydev.navigator.elements.PythonFile cannot be cast to org.eclipse.core.resources.IResource
at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.launch(BaseResourceAwareLaunchShortcut.java:39)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:431)
at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:74)
at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:123)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
Bundles:
| org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
| org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
| org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
| org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
Operating Systems:
| Windows | 10.0.0 | 10.0.0 |
The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/5827b... for the latest data.
Thank you for your assistance.
Your friendly error-reports-inbox.
Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (ERT-468) AssertionFailedException below ImageBuildDialog.createDialogArea (thrown in StructuredViewer.assertElementsNotNull) [EBZ#508026]
by Friendly Jira Robot (JIRA)
[ https://issues.jboss.org/browse/ERT-468?page=com.atlassian.jira.plugin.sy... ]
Friendly Jira Robot resolved ERT-468.
-------------------------------------
Resolution: Done
> AssertionFailedException below ImageBuildDialog.createDialogArea (thrown in StructuredViewer.assertElementsNotNull) [EBZ#508026]
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: ERT-468
> URL: https://issues.jboss.org/browse/ERT-468
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Unhandled event loop exception
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:586)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1002)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:907)
> at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:1084)
> at org.eclipse.jface.viewers.AbstractListViewer.inputChanged(AbstractListViewer.java:318)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:286)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1696)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageBuildDialog.createDialogArea(ImageBuildDialog.java:118)
> at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:767)
> at org.eclipse.jface.window.Window.create(Window.java:426)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1095)
> at org.eclipse.jface.window.Window.open(Window.java:783)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.createConfiguration(BuildDockerImageShortcut.java:109)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.findLaunchConfiguration(BaseResourceAwareLaunchShortcut.java:84)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BuildDockerImageShortcut.launch(BuildDockerImageShortcut.java:61)
> at org.eclipse.linuxtools.internal.docker.ui.launch.BaseResourceAwareLaunchShortcut.launch(BaseResourceAwareLaunchShortcut.java:41)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension.launch(LaunchShortcutExtension.java:431)
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.run(LaunchShortcutAction.java:74)
> at org.eclipse.debug.internal.ui.actions.LaunchShortcutAction.runWithEvent(LaunchShortcutAction.java:123)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> Bundles:
> | org.eclipse.debug.ui | 3.11.200.v20160518-1858 | 3.11.200.v20160518-1858 |
> | org.eclipse.jface | 3.12.0.v20160518-1929 | 3.12.0.v20160518-1929 |
> | org.eclipse.linuxtools.docker.ui | 2.1.0.201609141916 | 2.1.0.201609141916 |
> | org.eclipse.swt | 3.105.0.v20160603-0902 | 3.105.0.v20160603-0902 |
> Operating Systems:
> | Windows | 10.0.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/580dd... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
> Created on behalf of xcoulon(a)xxxxxx.xxx
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months