December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1028) Use correct OCP installer version when destroying cluster

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1028: ------------------------------------ Summary: Use correct OCP installer version when destroying cluster Key: SWSQE-1028 URL: https://issues.jboss.org/browse/SWSQE-1028 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta Destroy jobs always uses the latest OCP 4.2 installer which might be problem for OCP 4.3 clusters. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4835) Raise the timeout for generated tests - backport only this changes to 7.6

by Daniel Rosa (Jira)

[ https://issues.jboss.org/browse/DROOLS-4835?page=com.atlassian.jira.plugi... ] Daniel Rosa updated DROOLS-4835: -------------------------------- Git Pull Request: (was: https://github.com/kiegroup/drools/pull/2658) > Raise the timeout for generated tests - backport only this changes to 7.6 > ------------------------------------------------------------------------- > > Key: DROOLS-4835 > URL: https://issues.jboss.org/browse/DROOLS-4835 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > On Jenkins the generated tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4835) Raise the timeout for generated tests - backport only this changes to 7

by Daniel Rosa (Jira)

Daniel Rosa created DROOLS-4835: ----------------------------------- Summary: Raise the timeout for generated tests - backport only this changes to 7 Key: DROOLS-4835 URL: https://issues.jboss.org/browse/DROOLS-4835 Project: Drools Issue Type: Bug Reporter: Daniel Rosa Assignee: Daniel Rosa On Jenkins the generated tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4835) Raise the timeout for generated tests - backport only this changes to 7.6

by Daniel Rosa (Jira)

[ https://issues.jboss.org/browse/DROOLS-4835?page=com.atlassian.jira.plugi... ] Daniel Rosa updated DROOLS-4835: -------------------------------- Summary: Raise the timeout for generated tests - backport only this changes to 7.6 (was: Raise the timeout for generated tests - backport only this changes to 7) > Raise the timeout for generated tests - backport only this changes to 7.6 > ------------------------------------------------------------------------- > > Key: DROOLS-4835 > URL: https://issues.jboss.org/browse/DROOLS-4835 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > On Jenkins the generated tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1027) Overview Config Status Automate

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1027: ------------------------------------- Summary: Overview Config Status Automate Key: SWSQE-1027 URL: https://issues.jboss.org/browse/SWSQE-1027 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4834) Raise the timeout for concurrency tests

by Daniel Rosa (Jira)

[ https://issues.jboss.org/browse/DROOLS-4834?page=com.atlassian.jira.plugi... ] Daniel Rosa updated DROOLS-4834: -------------------------------- Sprint: 2019 Week 47-49 (from Nov 18) > Raise the timeout for concurrency tests > ---------------------------------------- > > Key: DROOLS-4834 > URL: https://issues.jboss.org/browse/DROOLS-4834 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > On Jenkins the tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1022) Overview page links

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-1022?page=com.atlassian.jira.plugin... ] Hayk Hovsepyan updated SWSQE-1022: ---------------------------------- Sprint: Kiali Sprint #30 > Overview page links > ------------------- > > Key: SWSQE-1022 > URL: https://issues.jboss.org/browse/SWSQE-1022 > 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)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1022) Overview page links

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-1022?page=com.atlassian.jira.plugin... ] Hayk Hovsepyan reassigned SWSQE-1022: ------------------------------------- Assignee: Hayk Hovsepyan > Overview page links > ------------------- > > Key: SWSQE-1022 > URL: https://issues.jboss.org/browse/SWSQE-1022 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1021) Verify View in Grafana link

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-1021?page=com.atlassian.jira.plugin... ] Hayk Hovsepyan commented on SWSQE-1021: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/221 > Verify View in Grafana link > --------------------------- > > Key: SWSQE-1021 > URL: https://issues.jboss.org/browse/SWSQE-1021 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4724) [DMN Designer] Do not default to a LiteralExpression when no expression is defined

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4724?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-4724: ------------------------------------- [~manstis] I think the jira title is misleading now, as we generate LE on some places, right? Furthermore my question what expression types should be affected by this, because for example if user add an invocation expression, with parameters, no LE is generated for parameters/arguments and there are validation errors after saving and reopening the dmn model. So my question is, is the goal of this jira to have zero validation errors after save and reopen, even if user haven't explicitly filled all cells, speaking about all expression types? Or do we speak just about context expression type (as one of those mostly used) and we do not handle invocations and functions ? I do not mention relation and decision tables, as there we already generate Literal Expressions. > [DMN Designer] Do not default to a LiteralExpression when no expression is defined > ---------------------------------------------------------------------------------- > > Key: DROOLS-4724 > URL: https://issues.jboss.org/browse/DROOLS-4724 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-11-29 12-04-18.png, error.log, image-2019-11-04-19-39-01-113.png, image-2019-11-04-19-40-27-201.png, m.dmn, save-context.webm, screenshot-1.png, screenshot-2.png > > > Currently, the DMN Editor will default to a blank LiteralExpression on Save if the user did not provide an expression for an element. > However Error message is reported anyway to the user: > !image-2019-11-04-19-39-01-113.png|thumbnail! > This also as the (imho undesired) side-effect that if the user was to re-open later that file, instead of a empty element, it would be a blank LiteralExpression > !image-2019-11-04-19-40-27-201.png|thumbnail! > so the current behavior is not consistent across re-open of the editor. > Let's revert this default. > The DMN Editor on save should +not+ default to a blank LiteralExpression if the user did not provide an expression for the element. > Once this change is applied from the f/e side, I am happy to be involved in order to assess which of the messages reported by the Validator or the Compiler are causing issue to the WB (if any). > Currently, the DMN Compiler will throw 1 Warning. > Currently, the DMN Validator will throw 1 Error (I can align this to be a Warn too). > Currently, the DMN Validator schema check is not reporting any XSD violation. > h2. Manual acceptance test > Try to save default / empty > h3. Business Central > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation > h3. Kogito > - Decision node > - BKM node > - Cleared Function > - Context entry > - Invocation -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2019