October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25275) intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25275?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25275: ------------------------------- Priority: Critical (was: Major) > intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25275 > URL: https://issues.jboss.org/browse/JBIDE-25275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.1.Final > > Attachments: intermittent-test-failures-central.png > > > intermittent test failures since Oct 3, when the last commit was pushed. > !intermittent-test-failures-central.png|thumbnail! > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Should we disable this test? or fix it? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25275) intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25275?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25275: ------------------------------- Description: intermittent test failures since Oct 3, when the last commit was pushed. !intermittent-test-failures-central.png|thumbnail! https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Should we disable this test? or fix it? was: intermittent test failures since Oct 3, when the last commit was pushed. Seems to be every other build: !intermittent-test-failures-central.png|thumbnail! > intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25275 > URL: https://issues.jboss.org/browse/JBIDE-25275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Fix For: 4.5.1.Final > > Attachments: intermittent-test-failures-central.png > > > intermittent test failures since Oct 3, when the last commit was pushed. > !intermittent-test-failures-central.png|thumbnail! > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Should we disable this test? or fix it? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25275) intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25275?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25275: ------------------------------- Summary: intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support (was: intermittent test failures in central) > intermittent test failures in central in org.jboss.tools.maven.configurators.tests.EndorsedLibConfiguratorTest.testJBIDE11738_quote_hack_support > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25275 > URL: https://issues.jboss.org/browse/JBIDE-25275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Fix For: 4.5.1.Final > > Attachments: intermittent-test-failures-central.png > > > intermittent test failures since Oct 3, when the last commit was pushed. Seems to be every other build: > !intermittent-test-failures-central.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25275) intermittent test failures in central

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25275: ---------------------------------- Summary: intermittent test failures in central Key: JBIDE-25275 URL: https://issues.jboss.org/browse/JBIDE-25275 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.5.1.Final Reporter: Nick Boldt Attachments: intermittent-test-failures-central.png intermittent test failures since Oct 3, when the last commit was pushed. Seems to be every other build: -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25275) intermittent test failures in central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25275?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25275: ------------------------------- Fix Version/s: 4.5.1.Final > intermittent test failures in central > ------------------------------------- > > Key: JBIDE-25275 > URL: https://issues.jboss.org/browse/JBIDE-25275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Fix For: 4.5.1.Final > > Attachments: intermittent-test-failures-central.png > > > intermittent test failures since Oct 3, when the last commit was pushed. Seems to be every other build: -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25275) intermittent test failures in central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25275?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25275: ------------------------------- Attachment: intermittent-test-failures-central.png > intermittent test failures in central > ------------------------------------- > > Key: JBIDE-25275 > URL: https://issues.jboss.org/browse/JBIDE-25275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Fix For: 4.5.1.Final > > Attachments: intermittent-test-failures-central.png > > > intermittent test failures since Oct 3, when the last commit was pushed. Seems to be every other build: -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25275) intermittent test failures in central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25275?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25275: ------------------------------- Description: intermittent test failures since Oct 3, when the last commit was pushed. Seems to be every other build: !intermittent-test-failures-central.png|thumbnail! was: intermittent test failures since Oct 3, when the last commit was pushed. Seems to be every other build: > intermittent test failures in central > ------------------------------------- > > Key: JBIDE-25275 > URL: https://issues.jboss.org/browse/JBIDE-25275 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Fix For: 4.5.1.Final > > Attachments: intermittent-test-failures-central.png > > > intermittent test failures since Oct 3, when the last commit was pushed. Seems to be every other build: > !intermittent-test-failures-central.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25091) Edit resource limits wizard: setting memory resource limits errors if you use the 2 duplicate MiB entries

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25091?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25091: ------------------------------------- Summary: Edit resource limits wizard: setting memory resource limits errors if you use the 2 duplicate MiB entries (was: Edit resource limits wizard: setting memory resource limits (using duplicate MiB entries) errors) > Edit resource limits wizard: setting memory resource limits errors if you use the 2 duplicate MiB entries > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25091 > URL: https://issues.jboss.org/browse/JBIDE-25091 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: edit-resource-limits.png, error-limit-must-be-equal-or-greater-than-request.png, image-2017-09-22-13-02-35-216.png, memory-limit-limit.png, memory-request-limit.png, request-resource-limit-combo.png, resource-limits-web-console.png > > > When editing memory settings in dialog "Edit resource limits", there is a duplicate value MiB in the Combos for Memory > "Request" and Memory > "Limit": > !edit-resource-limits.png! > You can have setting the limits error inexplicably in the following way: > # ASSERT: make sure that you have an application with a service, replication controller/deployment config running in OpenShift (ex. create one using the nodejs-mongo-persistent template) > # EXEC: in OpenShift explorer: select the service for your application and pick "Edit resource limit" in the context menu for it > # ASSERT: "Edit resource limit" dialog shows up > # EXEC: set Memory > Request to 128 and pick the 1st MiB entry in the combo > !memory-request-limit.png! > # EXEC: set Memory > Limit to 512 and pick the 2nd MiB entry in the combo > !memory-limit-limit.png! > # EXEC: "Finish" the wizard > Result: > The wizard errors telling you that the limit must be equal or greater than the request: > !error-limit-must-be-equal-or-greater-than-request.png! > In the Eclipse log you find the following: > {code} > com.openshift.restclient.OpenShiftException: Exception trying to PUT https://192.168.64.12:8443/oapi/v1/namespaces/nodejs/deploymentconfigs/no... response code: 422 DeploymentConfig "nodejs-mongo-persistent" is invalid: spec.template.spec.containers[0].resources.limits: Invalid value: "512": must be greater than or equal to memory request > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:258) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:210) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:316) > at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) > at org.jboss.tools.openshift.internal.ui.wizard.common.EditResourceLimitsHandler$EditResourceLimitsWizard$1.run(EditResourceLimitsHandler.java:117) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25273: ------------------------------------------ This issue is invalid since I was updating the rc but saw the dc in the wizard. Closing. > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: dc-rcs.png, edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25273: ------------------------------------- Sprint: (was: devex #140 November 2017) > Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes" > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-25273 > URL: https://issues.jboss.org/browse/JBIDE-25273 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: edit_resource_limits_wizard, openshift_v3 > Fix For: 4.5.1.Final > > Attachments: dc-rcs.png, edit-resource-limits-memory-limit-units.png > > > steps: > # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template) > # ASSERT: make sure that your memory request limit is in bytes: > # EXEC: in OpenShift explorer, select your project > # EXEC: in "Properties" view, select "Deployments" tab and select the last entry > # EXEC: pick "Edit" in the context menu to it > # ASSERT: replication controller is opened in the editor > # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit > {code} > "resources" : { > "limits" : {"memory" : "512"}, > }, > {code} > # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu > # ASSERT: Edit resource limits wizard shows up > Result: > Memory > Limits show *MiB* as unit > !edit-resource-limits-memory-limit-units.png! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 October 2017