January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1053) Automate Weight < 100 https://github.com/kiali/kiali/pull/2108

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1053?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1053: ---------------------------------- Sprint: Kiali Sprint #32 > Automate Weight < 100 https://github.com/kiali/kiali/pull/2108 > -------------------------------------------------------------- > > Key: SWSQE-1053 > URL: https://issues.redhat.com/browse/SWSQE-1053 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1047) Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1047?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1047. ----------------------------------- Resolution: Done Manual task is done, issue is opened: https://github.com/kiali/kiali/issues/2127 Automation is done. > Kiali Validations sync-up > ------------------------- > > Key: SWSQE-1047 > URL: https://issues.redhat.com/browse/SWSQE-1047 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Check all actual validations in https://kiali.io/documentation/validations/ > Sync up in Polarion testcases. > UI Automations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1048: ------------------------------------- Assignee: Hayk Hovsepyan (was: Sunil Kondkar) > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1048. ----------------------------------- Resolution: Done > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1048) Testcases - Kiali Validations sync-up

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1048?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1048: --------------------------------------- Thanks [~skondkar]. All described issues are logged in https://github.com/kiali/kiali/issues/2127 > Testcases - Kiali Validations sync-up > ------------------------------------- > > Key: SWSQE-1048 > URL: https://issues.redhat.com/browse/SWSQE-1048 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Sunil Kondkar > Priority: Major > > Sync up all validations from https://kiali.io/documentation/validations/ with Polarion estcases. > Make sure all validations have up-to-date testcases in Polarion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4950) Different behavior of collection unary checks

by Daniele Zonca (Jira)

[ https://issues.redhat.com/browse/DROOLS-4950?page=com.atlassian.jira.plug... ] Daniele Zonca commented on DROOLS-4950: --------------------------------------- [~jomarko] I think we should/could highlight better that expression and graphical editor are two completely different things: using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom. Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?" > Different behavior of collection unary checks > --------------------------------------------- > > Key: DROOLS-4950 > URL: https://issues.redhat.com/browse/DROOLS-4950 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Critical > Labels: drools-tools > Attachments: MySpace_simplenumbers.zip, Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Issue was spotted during DROOLS-4698 review. However it can be handled separately. > There is issue that user can define collection unary test with UI editor [1] but also as plain text [2]. The problem is the result is different. > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3447) Remove "DMN Asset" dependency from TitledAttachmentFileWidget

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-3447?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-3447: ------------------------------- Issue Type: Enhancement (was: Bug) > Remove "DMN Asset" dependency from TitledAttachmentFileWidget > ------------------------------------------------------------- > > Key: DROOLS-3447 > URL: https://issues.redhat.com/browse/DROOLS-3447 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > > Currently, TitledAttachmentFileWidget use ProjectAssetsQuery to retrieve the "dmn" files. > Implicitly, this means that *if* (for whatever reason) dmn editor is disabled, the dmn file are not retrieved. Wording differently, this creates an implicit dependency between scenariosimulation and dmn editor. > Fix it so that TitledAttachmentFileWidget could find dmn files regardless of dmn editor. > Look at left dock that shows all the files of the project. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12927) wildfly 8.2 huge memory allocation during and after deployement

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12927?page=com.atlassian.jira.plugi... ] Bartosz Baranowski commented on WFLY-12927: ------------------------------------------- Is there a reason to use container that has been released almost 5 years ago? Anyway WFLY does not have product support, can you please check if WFLY 19 behaves in the same way? > wildfly 8.2 huge memory allocation during and after deployement > --------------------------------------------------------------- > > Key: WFLY-12927 > URL: https://issues.redhat.com/browse/WFLY-12927 > Project: WildFly > Issue Type: Bug > Reporter: sandev sandev > Assignee: Bartosz Baranowski > Priority: Major > Attachments: threads.png > > > I am using wildfly 8.2.1 final to deploy java ee 7 maven web application wars about 30 war with dependence between them using rmi remote ejb. I found that the server consumes a lot of memory special on startup of the server to 8 g my java opt are -xms 8g -xmx 8g -metaspacesize 1g .so I use java "visualvm" to understand what is happening. I found that the most consumed memory is for 2 types of threads at deploy: MSC service thread and after deploy finish: DeployementScanner-threads in additional that no user use the server or the deployed application this server was just for test > my question is why wildfly starts with about 3g and after some time the memory growth to ~= 8g without any action on the server its idle any help to solve this problem please -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12927) wildfly 8.2 huge memory allocation during and after deployement

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12927?page=com.atlassian.jira.plugi... ] Bartosz Baranowski reassigned WFLY-12927: ----------------------------------------- Assignee: Bartosz Baranowski (was: Brian Stansberry) > wildfly 8.2 huge memory allocation during and after deployement > --------------------------------------------------------------- > > Key: WFLY-12927 > URL: https://issues.redhat.com/browse/WFLY-12927 > Project: WildFly > Issue Type: Bug > Reporter: sandev sandev > Assignee: Bartosz Baranowski > Priority: Major > Attachments: threads.png > > > I am using wildfly 8.2.1 final to deploy java ee 7 maven web application wars about 30 war with dependence between them using rmi remote ejb. I found that the server consumes a lot of memory special on startup of the server to 8 g my java opt are -xms 8g -xmx 8g -metaspacesize 1g .so I use java "visualvm" to understand what is happening. I found that the most consumed memory is for 2 types of threads at deploy: MSC service thread and after deploy finish: DeployementScanner-threads in additional that no user use the server or the deployed application this server was just for test > my question is why wildfly starts with about 3g and after some time the memory growth to ~= 8g without any action on the server its idle any help to solve this problem please -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4957) Adapt ScenarioSimulation Wrapper for Kogito project

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4957?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4957: ------------------------------- Component/s: Scenario Simulation and Testing Labels: drools-tools (was: ) > Adapt ScenarioSimulation Wrapper for Kogito project > --------------------------------------------------- > > Key: DROOLS-4957 > URL: https://issues.redhat.com/browse/DROOLS-4957 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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

jboss-jira January 2020