January 2018 - jbosstools-issues - Jboss List Archives

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25224?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25224: ---------------------------------- Assignee: Jeff MAURY > 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.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25166) Resource wizard: using (formally valid) URL to non-existing/erroneous json does not show error message

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25166?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25166: ------------------------------- Fix Version/s: 4.5.2.Final (was: 4.5.x) > Resource wizard: using (formally valid) URL to non-existing/erroneous json does not show error message > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25166 > URL: https://issues.jboss.org/browse/JBIDE-25166 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Josef Kopriva > Labels: openshift_v3, resource_wizard > Fix For: 4.5.2.Final > > Attachments: image-2017-10-27-15-12-22-841.png, valid-url-no-errors.png > > > Steps to reproduce: > 1. ASSERT: Have project in OpenShift connection in OpenShift Explorer > 2. EXEC: Right click on project -> New -> Resource... > 3. EXEC: Enter URL to non-existing template/json (ex. https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/...) > 4. EXEC: hit Finish > Result: > no error is shown -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25166) Resource wizard: using (formally valid) URL to non-existing/erroneous json does not show error message

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25166?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25166: ---------------------------------- Assignee: Jeff MAURY > Resource wizard: using (formally valid) URL to non-existing/erroneous json does not show error message > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25166 > URL: https://issues.jboss.org/browse/JBIDE-25166 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: openshift_v3, resource_wizard > Fix For: 4.5.2.Final > > Attachments: image-2017-10-27-15-12-22-841.png, valid-url-no-errors.png > > > Steps to reproduce: > 1. ASSERT: Have project in OpenShift connection in OpenShift Explorer > 2. EXEC: Right click on project -> New -> Resource... > 3. EXEC: Enter URL to non-existing template/json (ex. https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/...) > 4. EXEC: hit Finish > Result: > no error is shown -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25166) Resource wizard: using (formally valid) URL to non-existing/erroneous json does not show error message

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25166?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25166: ------------------------------- Sprint: devex #143 January 2018 > Resource wizard: using (formally valid) URL to non-existing/erroneous json does not show error message > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25166 > URL: https://issues.jboss.org/browse/JBIDE-25166 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: openshift_v3, resource_wizard > Fix For: 4.5.2.Final > > Attachments: image-2017-10-27-15-12-22-841.png, valid-url-no-errors.png > > > Steps to reproduce: > 1. ASSERT: Have project in OpenShift connection in OpenShift Explorer > 2. EXEC: Right click on project -> New -> Resource... > 3. EXEC: Enter URL to non-existing template/json (ex. https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/...) > 4. EXEC: hit Finish > Result: > no error is shown -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25544) Upgrade to Forge 3.8.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25544?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-25544: ------------------------------------ Labels: new_and_noteworthy (was: ) > Upgrade to Forge 3.8.1.Final > ---------------------------- > > Key: JBIDE-25544 > URL: https://issues.jboss.org/browse/JBIDE-25544 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.5.2.AM2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.5.2.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25544) Upgrade to Forge 3.8.1.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-25544: --------------------------------------- Summary: Upgrade to Forge 3.8.1.Final Key: JBIDE-25544 URL: https://issues.jboss.org/browse/JBIDE-25544 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Affects Versions: 4.5.2.AM2 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.5.2.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25503) Automate test of update JBT from previous milestone

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25503?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-25503: --------------------------------- Fix Version/s: 4.5.2.Final (was: 4.5.2.AM3) > Automate test of update JBT from previous milestone > --------------------------------------------------- > > Key: JBIDE-25503 > URL: https://issues.jboss.org/browse/JBIDE-25503 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.5.2.AM3 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.2.Final > > > It will be nice to have this time consuming test automated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25297) Improve CDK itests so that user do not need to have all CDK versions downloaded himself

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25297?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-25297: ------------------------------- Sprint: devex #143 January 2018 (was: devex #142 December 2017) > Improve CDK itests so that user do not need to have all CDK versions downloaded himself > --------------------------------------------------------------------------------------- > > Key: JBIDE-25297 > URL: https://issues.jboss.org/browse/JBIDE-25297 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk > Fix For: 4.5.2.Final > > > Add mock files that would substitute CDK 2.x Vagrantfile and CDK 3.1.1 binary for purposes of testing UI. These files will be placed in project path in resources/cdk-files. > Let user to pass his vagrant file and cdk-3.1.1 binary path via agrument -Dvagrantfile and -Dminishift in cases where he needs to do so. This argument's values will have priority over files from resources folder. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25515) GetJBDSInstallerLink.groovy scripts has no permissions to use some features of Jenkins API

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25515?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-25515: --------------------------------- Fix Version/s: 4.5.2.Final (was: 4.5.2.AM3) > GetJBDSInstallerLink.groovy scripts has no permissions to use some features of Jenkins API > ------------------------------------------------------------------------------------------ > > Key: JBIDE-25515 > URL: https://issues.jboss.org/browse/JBIDE-25515 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.2.AM3 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.2.Final > > > A lot of installer tests are failing because after last update of Jenkins script \[1\] GetJBDSInstallerLink.groovy hasn't permission to use some features of Jenkins API. > \[1\] https://github.com/jbdevstudio/jbdevstudio-qa/blob/master/jenkins-script/... > There is this error message in the log: > {code} > ERROR: Build step failed with exception > org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.HashMap > {code} > The rights were limited for a security reason so I need to findout a workaround. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25067) jsf itests job is failing

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25067?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-25067: ------------------------------- Sprint: devex #143 January 2018 (was: devex #142 December 2017) > jsf itests job is failing > ------------------------- > > Key: JBIDE-25067 > URL: https://issues.jboss.org/browse/JBIDE-25067 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, jsf > Reporter: Pavol Srna > Assignee: Ondrej Dockal > Fix For: 4.5.2.Final > > > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2018