[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:
------------------------------------------
[~jeffmaury] I have no windows machine handy, can you confirm these failures?
> 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
> Labels: openshift_v3
> Fix For: 4.5.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)
8 years, 5 months
[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 updated JBIDE-25224:
-------------------------------------
Fix Version/s: 4.5.x
> 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
> Labels: openshift_v3
> Fix For: 4.5.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)
8 years, 5 months
[JBoss JIRA] (JBIDE-24972) DeleteResourceHandlerTest is failing for Windows
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24972?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24972:
-------------------------------------
Fix Version/s: 4.5.2.AM1
(was: 4.5.x)
> DeleteResourceHandlerTest is failing for Windows
> ------------------------------------------------
>
> Key: JBIDE-24972
> URL: https://issues.jboss.org/browse/JBIDE-24972
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Dmitrii Bocharov
> Assignee: Dmitrii Bocharov
> Labels: openshift_v3, unit_tests
> Fix For: 4.5.2.AM1
>
>
> https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/JBossTools/view...
> {code:java}
> java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
> no swt-win32-4757 in java.library.path
> no swt-win32 in java.library.path
> Can't load library: C:\Users\hudson\.swt\lib\win32\x86_64\swt-win32-4757.dll
> Can't load library: C:\Users\hudson\.swt\lib\win32\x86_64\swt-win32.dll
> at org.eclipse.swt.internal.Library.loadLibrary(Library.java:327)
> at org.eclipse.swt.internal.Library.loadLibrary(Library.java:236)
> at org.eclipse.swt.internal.C.<clinit>(C.java:16)
> at org.eclipse.swt.widgets.Widget.<clinit>(Widget.java:112)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at javassist.runtime.Desc.getClassObject(Desc.java:43)
> at javassist.runtime.Desc.getClassType(Desc.java:152)
> at javassist.runtime.Desc.getType(Desc.java:122)
> at javassist.runtime.Desc.getParams(Desc.java:70)
> at org.eclipse.jface.dialogs.MessageDialog.openConfirm(MessageDialog.java)
> at org.jboss.tools.openshift.test.internal.ui.handler.DeleteResourceHandlerTest.testStopWatchProject(DeleteResourceHandlerTest.java:51)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-24972) DeleteResourceHandlerTest is failing for Windows
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24972?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24972:
-------------------------------------
Labels: openshift_v3 unit_tests (was: )
> DeleteResourceHandlerTest is failing for Windows
> ------------------------------------------------
>
> Key: JBIDE-24972
> URL: https://issues.jboss.org/browse/JBIDE-24972
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Dmitrii Bocharov
> Assignee: Dmitrii Bocharov
> Labels: openshift_v3, unit_tests
> Fix For: 4.5.2.AM1
>
>
> https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/JBossTools/view...
> {code:java}
> java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
> no swt-win32-4757 in java.library.path
> no swt-win32 in java.library.path
> Can't load library: C:\Users\hudson\.swt\lib\win32\x86_64\swt-win32-4757.dll
> Can't load library: C:\Users\hudson\.swt\lib\win32\x86_64\swt-win32.dll
> at org.eclipse.swt.internal.Library.loadLibrary(Library.java:327)
> at org.eclipse.swt.internal.Library.loadLibrary(Library.java:236)
> at org.eclipse.swt.internal.C.<clinit>(C.java:16)
> at org.eclipse.swt.widgets.Widget.<clinit>(Widget.java:112)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at javassist.runtime.Desc.getClassObject(Desc.java:43)
> at javassist.runtime.Desc.getClassType(Desc.java:152)
> at javassist.runtime.Desc.getType(Desc.java:122)
> at javassist.runtime.Desc.getParams(Desc.java:70)
> at org.eclipse.jface.dialogs.MessageDialog.openConfirm(MessageDialog.java)
> at org.jboss.tools.openshift.test.internal.ui.handler.DeleteResourceHandlerTest.testStopWatchProject(DeleteResourceHandlerTest.java:51)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25350) CDK server editor's launch configuration should not offers to edit some fields
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25350?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-25350:
---------------------------------------
[~odockal], I can confirm that changing the adapter name in the server editor is not reflected in launch config.
I agree that these two fields should be read-only in launch config.
> CDK server editor's launch configuration should not offers to edit some fields
> ------------------------------------------------------------------------------
>
> Key: JBIDE-25350
> URL: https://issues.jboss.org/browse/JBIDE-25350
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.x
>
>
> I noticed some inconsistent behavior in launch configuration dialog.
> 1. Server name change in server's editor do not result in changing of text "Name:" in launch configuration (should be, possibly a bug) and vice versa.
> 2. Change of Minishift Binary in editor results in change of "Location" in launch config, but not vice versa. This is not a bug, it is just confusing the user.
> I believe that it should not be possible to edit those two fields in launch configuration. First reason for this is that we already have a place where we can edit server's name and location (in cdk server editor) and other reason will be that if we will allow to edit those values, we must put validation in place. WDYT [~mmalina] [~rob.stryker] ?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-25121) Connection wizard: Image Registry URL is not decorated when not valid (and validation seems weird)
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25121?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-25121.
---------------------------------
Closing:
Ad. 1. : Test result is ok now.
Ad. 2. : That URL is valid.(Discussion in PR)
Verified in:
Red Hat JBoss Developer Studio
Version: 11.2.0.AM1
Build id: AM1-v20171107-0704-B1532
Build date: 20171107-0704
> Connection wizard: Image Registry URL is not decorated when not valid (and validation seems weird)
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25121
> URL: https://issues.jboss.org/browse/JBIDE-25121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.5.2.AM1
>
> Attachments: image-2017-09-27-22-59-33-548.png
>
>
> steps 1:
> # ASSERT: have a connection the cdk
> # EXEC: edit the connection and move to "Image Registry URL" text field
> # EXEC: provide some bogus URL (ex. bookaroo-banzai)
> Result:
> the url is validated and an error appears in the title are, "Finish" is disabled. GOOD.
> But the text field is not decorated.
> !image-2017-09-27-22-59-33-548.png!
> steps 2:
> # EXEC: provide the following URL: http:/bookaroo-banzai
> Result:
> It thinks that it's valid, there's no error in the title area, "Finish" is enabled
> Expected result:
> http:/bookaroo-banzai doesnt look valid to me, it should error and disable "Finish"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-22965) CDK tools should work behind proxy
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22965?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22965:
-------------------------------------
Description:
Proxy support has been added in CDK vagrant box and in vagrant-registration plugin.
We should make sure our CDK tooling supports it too.
In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/...
Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982
+ to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25
Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]:
{noformat}
lalatenduM: we exepect customers workstation is configured to porixy server
that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work
lalatenduM: on a customer worksttaion
lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information
lalatenduM: vagrant-registration uses subscription manager for registraton
lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info
{noformat}
in a mail on the 26th of October 2017 "Re: [openshift-sme] CDK: Usage behind proxy":
{quote}
The CDK supports a number of methods to apply proxy configuration.
You can specify a few of these at startup using the “minishift start” command.
First, you can set the --http-proxy and/or --https-proxy to apply RHEL environment variables.
For Docker Pulls, you can specify environment variables that are applied to the Docker daemon using the --docker-env flag (HTTP_PROXY, HTTPS_PROXY, NO_PROXY).
There are additional considerations for builds as well that can be applied. Please see the following document on the proxy considerations:
https://docs.openshift.com/container-platform/3.6/install_config/http_pro...
- Andy
{quote}
was:
Proxy support has been added in CDK vagrant box and in vagrant-registration plugin.
We should make sure our CDK tooling supports it too.
In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/...
Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982
+ to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25
Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]:
{noformat}
lalatenduM: we exepect customers workstation is configured to porixy server
that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work
lalatenduM: on a customer worksttaion
lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information
lalatenduM: vagrant-registration uses subscription manager for registraton
lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info
{noformat}
> CDK tools should work behind proxy
> ----------------------------------
>
> Key: JBIDE-22965
> URL: https://issues.jboss.org/browse/JBIDE-22965
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.x
>
> Attachments: create_proxy-test_env.sh
>
>
> Proxy support has been added in CDK vagrant box and in vagrant-registration plugin.
> We should make sure our CDK tooling supports it too.
> In order to run CDK behind proxy, we need to set environment variables: https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/...
> Eclipse Proxy Testing link: https://mojo.redhat.com/docs/DOC-989982
> + to create a proxy test environment: https://gist.github.com/LalatenduMohanty/5062050ac78721eda9676bbc15ecfd25
> Standard unix proxy environmet variable $http_proxy has different purpose then $PROXY that CDK uses. Comments from [~lalatendum]:
> {noformat}
> lalatenduM: we exepect customers workstation is configured to porixy server
> that means when you ping subscription-rhn-redhat-com.edge.prod.ext.phx2.redhat.com it should work
> lalatenduM: on a customer worksttaion
> lalatenduM: now teh challenge is to make openshift , docker and subscription manager in CDK VM aware of proxy server information
> lalatenduM: vagrant-registration uses subscription manager for registraton
> lalatenduM: whenyou use https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/... it will make openshift, docker and vagrant-registration aware of proxy server info
> {noformat}
> in a mail on the 26th of October 2017 "Re: [openshift-sme] CDK: Usage behind proxy":
> {quote}
> The CDK supports a number of methods to apply proxy configuration.
> You can specify a few of these at startup using the “minishift start” command.
> First, you can set the --http-proxy and/or --https-proxy to apply RHEL environment variables.
> For Docker Pulls, you can specify environment variables that are applied to the Docker daemon using the --docker-env flag (HTTP_PROXY, HTTPS_PROXY, NO_PROXY).
> There are additional considerations for builds as well that can be applied. Please see the following document on the proxy considerations:
> https://docs.openshift.com/container-platform/3.6/install_config/http_pro...
> - Andy
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months