May 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25224) OpenShift maven build fails on Windows - EGit tests failures

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25224?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25224: ------------------------------------------ [~jkopriva] this happens to me on my mac and in jenkins from time to time, but it's rare. Can you still experience this? How frequent is it? > OpenShift maven build fails on Windows - EGit tests failures > ------------------------------------------------------------ > > Key: JBIDE-25224 > URL: https://issues.jboss.org/browse/JBIDE-25224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.Final > Environment: Windows 10 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: openshift_v3 > Fix For: 4.6.x > > > Command *mvn clean install* fails in jbosstools-openshift repo: > {code:java} > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Tests run: 38, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 26.824 sec <<< FAILURE! - in org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest > shouldReturnLatestCommitInRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 2.006 sec > shouldFetchAndHaveRemoteRef(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.672 sec > canGetFromSeveralRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.594 sec > shouldReturnHostFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.656 sec > shouldReturnThatCloneIsAheadOfRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 1.032 sec > canGetSingleRemoteConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.687 sec > pushFailsOnNonFastForward(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.719 sec > shouldReturnThatCloneIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.719 sec > canGetRepoForFile(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.734 sec > newUntrackedFilesAreCounted(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.672 sec > shouldReturnUserFromFullGitUrl(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.64 sec > canAddRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.579 sec > removedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.625 sec > canCommitFileInProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.656 sec > shouldReturnRepositoryDoesntExists(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.547 sec > shouldConsiderSSHGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.687 sec > shouldCheckoutBranch(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.735 sec > shouldUserFetchSpecInConfig(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.625 sec > shouldReturnLatestCommitInLocalRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.64 sec > modifiedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.706 sec > canCheckIfHasRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.611 sec > originShouldBeDefaultRemoteRepo(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.581 sec > shouldReturnThatRemoteIsAhead(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.766 sec > forcedPushRemovesFileInRemote(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.703 sec <<< ERROR! > org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources. > at org.eclipse.core.internal.resources.Resource.delete(Resource.java:773) > at org.eclipse.core.internal.resources.Project.delete(Project.java:318) > at org.jboss.tools.openshift.egit.internal.test.util.TestProject.dispose(TestProject.java:84) > at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.tearDown(EGitUtilsTest.java:116) > untrackedWhileIncludeUntrackedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.781 sec > shouldNotBeAheadAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.782 sec > canGetRepoForProject(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.578 sec > fileAddedToCloneIsInOriginAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.672 sec > newUntrackedFileIsNotCountedIfIgnoreUntracked(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.515 sec > shouldConsiderSCPGitUrlValid(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.594 sec > getRemoteHttpRepos(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.797 sec > addedButNotCommittedIsDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.597 sec > untrackedWhileDontIncludeUntrackedIsNotDirty(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.575 sec > shouldReturnHEADAsIs(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.718 sec > shouldReturnRepositoryExists(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.625 sec > shouldReturnRemoteBranchName(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.657 sec > shouldReturnLocalBranchName(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.578 sec > fileAddedToCloneIsInRemoteAfterPush(org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest) Time elapsed: 0.687 sec > Running org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest > Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.578 sec - in org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest > canAddEntries(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0 sec > writingDoesNotAlterOrdering(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.125 sec > canParseExistingEntries(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.125 sec > newEntriesAreAddedToTheEnd(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.11 sec > addingExistingEntryDoesNotMoveItToTheEnd(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.125 sec > entryIsNotAddedTwice(org.jboss.tools.openshift.egit.internal.test.GitIgnoreTest) Time elapsed: 0.093 sec > Results : > Tests in error: > EGitUtilsTest.tearDown:116 ╗ Resource Problems encountered while deleting reso... > Tests run: 44, Failures: 0, Errors: 1, Skipped: 0 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] jbosstools-openshift ............................... SUCCESS [ 0.891 s] > [INFO] openshift.plugins .................................. SUCCESS [ 0.062 s] > [INFO] org.jboss.tools.openshift.egit.core ................ SUCCESS [ 21.017 s] > [INFO] org.jboss.tools.openshift.egit.ui .................. SUCCESS [ 3.453 s] > [INFO] org.jboss.tools.openshift.express.client ........... SUCCESS [ 7.301 s] > [INFO] org.jboss.tools.openshift.common.core .............. SUCCESS [ 5.125 s] > [INFO] org.jboss.tools.openshift.express.core ............. SUCCESS [ 5.039 s] > [INFO] org.jboss.tools.openshift.common.ui ................ SUCCESS [ 7.430 s] > [INFO] org.jboss.tools.openshift.express.ui ............... SUCCESS [ 13.594 s] > [INFO] org.jboss.tools.openshift.client ................... SUCCESS [ 1.328 s] > [INFO] org.jboss.tools.openshift.core ..................... SUCCESS [ 3.105 s] > [INFO] org.jboss.tools.openshift.ui ....................... SUCCESS [ 15.898 s] > [INFO] org.jboss.tools.openshift.cdk.server ............... SUCCESS [ 3.188 s] > [INFO] org.jboss.tools.openshift.js ....................... SUCCESS [ 4.179 s] > [INFO] org.jboss.tools.openshift.io.core .................. SUCCESS [ 4.453 s] > [INFO] org.jboss.tools.openshift.io.ui .................... SUCCESS [ 3.375 s] > [INFO] openshift.itests ................................... SUCCESS [ 0.047 s] > [INFO] openshift.test-framework ........................... SUCCESS [ 0.047 s] > [INFO] org.jboss.tools.openshift.reddeer .................. SUCCESS [ 2.535 s] > [INFO] org.jboss.tools.openshift.ui.bot.test .............. SUCCESS [ 2.766 s] > [INFO] openshift.tests .................................... SUCCESS [ 0.063 s] > [INFO] org.jboss.tools.openshift.egit.test ................ FAILURE [ 42.365 s] > [INFO] org.jboss.tools.openshift.express.test ............. SKIPPED > [INFO] org.jboss.tools.openshift.test ..................... SKIPPED > [INFO] org.jboss.tools.openshift.cdk.server.test .......... SKIPPED > [INFO] org.jboss.tools.openshift.io.test .................. SKIPPED > [INFO] org.jboss.tools.cdk.reddeer ........................ SKIPPED > [INFO] openshift.features ................................. SKIPPED > [INFO] org.jboss.tools.openshift.feature .................. SKIPPED > [INFO] org.jboss.tools.openshift.test.feature ............. SKIPPED > [INFO] org.jboss.tools.openshift.egit.integration.feature . SKIPPED > [INFO] org.jboss.tools.openshift.egit.integration.test.feature SKIPPED > [INFO] org.jboss.tools.openshift.express.feature .......... SKIPPED > [INFO] org.jboss.tools.openshift.express.test.feature ..... SKIPPED > [INFO] org.jboss.tools.openshift.cdk.feature .............. SKIPPED > [INFO] org.jboss.tools.openshift.cdk.test.feature ......... SKIPPED > [INFO] org.jboss.tools.openshift.integration.tests.feature SKIPPED > [INFO] org.jboss.tools.openshift.js.feature ............... SKIPPED > [INFO] org.jboss.tools.openshift.io.feature ............... SKIPPED > [INFO] org.jboss.tools.openshift.io.test.feature .......... SKIPPED > [INFO] openshift.site ..................................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 03:31 min > [INFO] Finished at: 2017-10-12T10:41:22+02:00 > [INFO] Final Memory: 216M/1534M > [INFO] ------------------------------------------------------------------------ > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25683) OpenShift New Connection: Automatic copying of token does not work on Fedora

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25683?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25683: ------------------------------------- Labels: connection_wizard upstream (was: ) > OpenShift New Connection: Automatic copying of token does not work on Fedora > ---------------------------------------------------------------------------- > > Key: JBIDE-25683 > URL: https://issues.jboss.org/browse/JBIDE-25683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM1 > Environment: F27 > Red Hat JBoss Developer Studio > Version: 11.3.0.AM1 > Build id: AM1-v20180201-0838-B1971 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: connection_wizard, upstream > Fix For: 4.6.x > > > Automac copying of token does not work on Fedora, but it does on Win10. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25683) [WATCHER] OpenShift New Connection: Automatic copying of token does not work on Fedora

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25683?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25683: ------------------------------------- Summary: [WATCHER] OpenShift New Connection: Automatic copying of token does not work on Fedora (was: OpenShift New Connection: Automatic copying of token does not work on Fedora) > [WATCHER] OpenShift New Connection: Automatic copying of token does not work on Fedora > -------------------------------------------------------------------------------------- > > Key: JBIDE-25683 > URL: https://issues.jboss.org/browse/JBIDE-25683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM1 > Environment: F27 > Red Hat JBoss Developer Studio > Version: 11.3.0.AM1 > Build id: AM1-v20180201-0838-B1971 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: connection_wizard, upstream > Fix For: 4.6.x > > > Automac copying of token does not work on Fedora, but it does on Win10. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25683) OpenShift New Connection: Automatic copying of token does not work on Fedora

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25683?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25683: ------------------------------------------ [~jeffmaury] upstream Eclipse bugzilla was resolved july 2017. Can we still experience this? > OpenShift New Connection: Automatic copying of token does not work on Fedora > ---------------------------------------------------------------------------- > > Key: JBIDE-25683 > URL: https://issues.jboss.org/browse/JBIDE-25683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM1 > Environment: F27 > Red Hat JBoss Developer Studio > Version: 11.3.0.AM1 > Build id: AM1-v20180201-0838-B1971 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Fix For: 4.6.x > > > Automac copying of token does not work on Fedora, but it does on Win10. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26067) OpenShift Adaptor is more difficult to use than it needs to be - consult with the UX team and find areas of improvement.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26067?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26067: ------------------------------------------ [~rpdavis] the area of concern is the Server Adapter, that does the syncing btw a local project and an OpenShift pod, is it? > OpenShift Adaptor is more difficult to use than it needs to be - consult with the UX team and find areas of improvement. > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26067 > URL: https://issues.jboss.org/browse/JBIDE-26067 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.5.3.Final > Reporter: Bob Davis > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26067) OpenShift Adaptor is more difficult to use than it needs to be - consult with the UX team and find areas of improvement.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26067?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26067: ------------------------------- Fix Version/s: 4.6.x > OpenShift Adaptor is more difficult to use than it needs to be - consult with the UX team and find areas of improvement. > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26067 > URL: https://issues.jboss.org/browse/JBIDE-26067 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.5.3.Final > Reporter: Bob Davis > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26067) OpenShift Adaptor is more difficult to use than it needs to be - consult with the UX team and find areas of improvement.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26067?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26067: ------------------------------- Affects Version/s: 4.5.3.Final > OpenShift Adaptor is more difficult to use than it needs to be - consult with the UX team and find areas of improvement. > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26067 > URL: https://issues.jboss.org/browse/JBIDE-26067 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.5.3.Final > Reporter: Bob Davis > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26067) OpenShift Adaptor is more difficult to use than it needs to be - consult with the UX team and find areas of improvement.

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26067?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26067: ---------------------------------- Component/s: openshift > OpenShift Adaptor is more difficult to use than it needs to be - consult with the UX team and find areas of improvement. > ------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26067 > URL: https://issues.jboss.org/browse/JBIDE-26067 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Reporter: Bob Davis > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25897) New Project validation uses wrong name space when there are two connections in OpenShift Explorer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25897?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-25897. --------------------------------- > New Project validation uses wrong name space when there are two connections in OpenShift Explorer > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25897 > URL: https://issues.jboss.org/browse/JBIDE-25897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM3 > Environment: Windows 10 Pro, CDK 3.4.0-alpha.1 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Labels: explorer, new_project_wizard > Fix For: 4.6.0.AM3 > > Attachments: project-already-exists.png, pyproject-error.gif > > > !pyproject-error.gif! > Prerequisites to reproduce the issue: > 1. Start CDK/Minishift > 2. Create second connection with different user name 'developer3' for example > 3. Click hyper link in explorer to create new Project > 4. Use name 'myproject' > 5. ERROR: > {code}Could not create project "myproject": project.project.openshift.io "myproject" already exists > Exception trying to POST https://192.168.99.100:8443/oapi/v1/projectrequests response code: 409 project.project.openshift.io "myproject" already exists{code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26070) [SSP] Client Managed workflow

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26070?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-26070: ----------------------------------- Assignee: Rob Stryker > [SSP] Client Managed workflow > ----------------------------- > > Key: JBIDE-26070 > URL: https://issues.jboss.org/browse/JBIDE-26070 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.6.0.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > > aged flow > @startuml > Client -> Adaptor : findservers > Client <- Adaptor : serverlist > Client -> Adaptor : create server > Client <- Adaptor : serverAdded (id) > Client -> Adaptor : getLaunchProperties() > Adapter -> Client : here’s a list > Client -> Adaptor : getLaunchCommand(String serverId, String mode, Map<String,String> properties) > Client <- Adaptor : launch string (id) > Client -> Adaptor : server started > Client -> Adaptor : server stopped > Client -> Adaptor : publish > @enduml -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2018