February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-619) PR Job kiali-core-pr-e2e-test Error

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-619?page=com.atlassian.jira.plugin.... ] Matt Mahoney updated SWSQE-619: ------------------------------- Sprint: Kiali Sprint #19 > PR Job kiali-core-pr-e2e-test Error > ----------------------------------- > > Key: SWSQE-619 > URL: https://issues.jboss.org/browse/SWSQE-619 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Priority: Major > > Error in publish.sh > + git clone https://github.com/Kiali-QE/publish-jenkins-console publish_logs > Cloning into 'publish_logs'... > + chmod +x publish_logs/publish.sh > + ./publish_logs/publish.sh > Collecting jenkinsapi==0.3.6 (from -r requirements.txt (line 1)) > Downloading https://files.pythonhosted.org/packages/89/6a/b1f6a9fe4ba331b68013db1ec0a... (123kB) > Requirement already satisfied: requests>=2.3.0 in /usr/lib/python3.6/site-packages (from jenkinsapi==0.3.6->-r requirements.txt (line 1)) (2.21.0) > Requirement already satisfied: six>=1.10.0 in /usr/lib/python3.6/site-packages (from jenkinsapi==0.3.6->-r requirements.txt (line 1)) (1.12.0) > Collecting pytz>=2014.4 (from jenkinsapi==0.3.6->-r requirements.txt (line 1)) > Downloading https://files.pythonhosted.org/packages/61/28/1d3920e4d1d50b19bc5d24398a7... (510kB) > Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3.6/site-packages (from requests>=2.3.0->jenkinsapi==0.3.6->-r requirements.txt (line 1)) (2018.11.29) > Requirement already satisfied: idna<2.9,>=2.5 in /usr/lib/python3.6/site-packages (from requests>=2.3.0->jenkinsapi==0.3.6->-r requirements.txt (line 1)) (2.8) > Requirement already satisfied: urllib3<1.25,>=1.21.1 in /usr/lib/python3.6/site-packages (from requests>=2.3.0->jenkinsapi==0.3.6->-r requirements.txt (line 1)) (1.24.1) > Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/lib/python3.6/site-packages (from requests>=2.3.0->jenkinsapi==0.3.6->-r requirements.txt (line 1)) (3.0.4) > Installing collected packages: pytz, jenkinsapi > Successfully installed jenkinsapi-0.3.6 pytz-2018.9 > You are using pip version 19.0.1, however version 19.0.3 is available. > You should consider upgrading via the 'pip install --upgrade pip' command. > Traceback (most recent call last): > File "publish_jenkins_console.py", line 8, in <module> > import requests > ImportError: No module named requests > cat: /home/jenkins/workspace/kiali-core-pr-e2e-test/build_comment_log.md: No such file or directory > *** End of publish logs *** > ++ cat env.properties > ++ grep REMOVE_KIALI > ++ cut -d = -f 2 > + '[' false == false ']' > + echo -e '\n\n' > POST BUILD TASK : SUCCESS > END OF POST BUILD TASK : 0 > Setting status of 62d2e83f9a48e3736202fba231c1cf0d7ea70a1e to SUCCESS with url https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/kiali-core-pr-e... and message: 'Test PASSed. > ' > Using context: Jenkins-CI -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-619) PR Job kiali-core-pr-e2e-test Error

by Matt Mahoney (Jira)

Matt Mahoney created SWSQE-619: ---------------------------------- Summary: PR Job kiali-core-pr-e2e-test Error Key: SWSQE-619 URL: https://issues.jboss.org/browse/SWSQE-619 Project: Kiali QE Issue Type: Bug Reporter: Matt Mahoney Error in publish.sh + git clone https://github.com/Kiali-QE/publish-jenkins-console publish_logs Cloning into 'publish_logs'... + chmod +x publish_logs/publish.sh + ./publish_logs/publish.sh Collecting jenkinsapi==0.3.6 (from -r requirements.txt (line 1)) Downloading https://files.pythonhosted.org/packages/89/6a/b1f6a9fe4ba331b68013db1ec0a... (123kB) Requirement already satisfied: requests>=2.3.0 in /usr/lib/python3.6/site-packages (from jenkinsapi==0.3.6->-r requirements.txt (line 1)) (2.21.0) Requirement already satisfied: six>=1.10.0 in /usr/lib/python3.6/site-packages (from jenkinsapi==0.3.6->-r requirements.txt (line 1)) (1.12.0) Collecting pytz>=2014.4 (from jenkinsapi==0.3.6->-r requirements.txt (line 1)) Downloading https://files.pythonhosted.org/packages/61/28/1d3920e4d1d50b19bc5d24398a7... (510kB) Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3.6/site-packages (from requests>=2.3.0->jenkinsapi==0.3.6->-r requirements.txt (line 1)) (2018.11.29) Requirement already satisfied: idna<2.9,>=2.5 in /usr/lib/python3.6/site-packages (from requests>=2.3.0->jenkinsapi==0.3.6->-r requirements.txt (line 1)) (2.8) Requirement already satisfied: urllib3<1.25,>=1.21.1 in /usr/lib/python3.6/site-packages (from requests>=2.3.0->jenkinsapi==0.3.6->-r requirements.txt (line 1)) (1.24.1) Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/lib/python3.6/site-packages (from requests>=2.3.0->jenkinsapi==0.3.6->-r requirements.txt (line 1)) (3.0.4) Installing collected packages: pytz, jenkinsapi Successfully installed jenkinsapi-0.3.6 pytz-2018.9 You are using pip version 19.0.1, however version 19.0.3 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Traceback (most recent call last): File "publish_jenkins_console.py", line 8, in <module> import requests ImportError: No module named requests cat: /home/jenkins/workspace/kiali-core-pr-e2e-test/build_comment_log.md: No such file or directory *** End of publish logs *** ++ cat env.properties ++ grep REMOVE_KIALI ++ cut -d = -f 2 + '[' false == false ']' + echo -e '\n\n' POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Setting status of 62d2e83f9a48e3736202fba231c1cf0d7ea70a1e to SUCCESS with url https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/kiali-core-pr-e... and message: 'Test PASSed. ' Using context: Jenkins-CI -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3659: ------------------------------------- [~roger600] Doh, thanks for the correction. :) > DMN: UX for documentation reports > --------------------------------- > > Key: DROOLS-3659 > URL: https://issues.jboss.org/browse/DROOLS-3659 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > User stories: > * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file. > * As a user I need a means through the UI to input additional documentation, links and attachments to nodes. > Notes: > - Docs to help with docs formatting. > - Might be able to leverage Case View docs widget. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3701) Remove drlx-parser from repository list

by Luca Molteni (Jira)

Luca Molteni created DROOLS-3701: ------------------------------------ Summary: Remove drlx-parser from repository list Key: DROOLS-3701 URL: https://issues.jboss.org/browse/DROOLS-3701 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Luca Molteni https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/master/script... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3695) Prepare a full Drools+protean demo for Meeting

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3695?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3695: ----------------------------------- Story Points: 3 > Prepare a full Drools+protean demo for Meeting > ---------------------------------------------- > > Key: DROOLS-3695 > URL: https://issues.jboss.org/browse/DROOLS-3695 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > It would be nice to have a complete workflow, and possibly a Drools+jBPM demo -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3695) Prepare a full Drools+protean demo for Meeting

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3695?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-3695: ----------------------------------- Sprint: 2019 Week 08-10 > Prepare a full Drools+protean demo for Meeting > ---------------------------------------------- > > Key: DROOLS-3695 > URL: https://issues.jboss.org/browse/DROOLS-3695 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > It would be nice to have a complete workflow, and possibly a Drools+jBPM demo -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3693) Prepare a crash course on how to use JP for parsing and generating code

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3693?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-3693: --------------------------------- Sprint: 2019 Week 08-10 > Prepare a crash course on how to use JP for parsing and generating code > ----------------------------------------------------------------------- > > Key: DROOLS-3693 > URL: https://issues.jboss.org/browse/DROOLS-3693 > Project: Drools > Issue Type: Task > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3700) OSGify the constraint parser

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3700?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-3700: --------------------------------- Sprint: 2019 Week 08-10 > OSGify the constraint parser > ---------------------------- > > Key: DROOLS-3700 > URL: https://issues.jboss.org/browse/DROOLS-3700 > Project: Drools > Issue Type: Enhancement > Components: executable model > Affects Versions: 7.18.0.Final > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10466) Ignoring a failure, even when it occurs in a narrow context where the failure is not relatively unimportant

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-10466?page=com.atlassian.jira.plugin... ] Marek Kopecký updated WFLY-10466: --------------------------------- Affects Version/s: 16.0.0.Beta1 > Ignoring a failure, even when it occurs in a narrow context where the failure is not relatively unimportant > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-10466 > URL: https://issues.jboss.org/browse/WFLY-10466 > Project: WildFly > Issue Type: Bug > Components: Management, REST > Affects Versions: 16.0.0.Beta1 > Reporter: Marek Kopecký > Assignee: Jeff Mesnil > Priority: Major > > This bug is introduced by https://github.com/wildfly/wildfly/pull/11116 for REST component (WFLY-10222) > This bug is described in [~brian.stansberry]'s [comment|https://issues.jboss.org/browse/WFLY-10222?focusedCommentId=13566...] > Fix for this bug may be related with WFCORE-3754 feature request -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2331) Probe does not handle multiple protocols of the same class in the same stack

by Bela Ban (Jira)

Bela Ban created JGRP-2331: ------------------------------ Summary: Probe does not handle multiple protocols of the same class in the same stack Key: JGRP-2331 URL: https://issues.jboss.org/browse/JGRP-2331 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.0.19 When we have multiple protocols of the same type (e.g. FRAG2) in the same stack, probe.sh only dumps information about the first one found. E.g. in {noformat} <UDP/> <PING/> <FRAG2 id="350".../> ... <GMS/> <FRAG2.../> {noformat} , the FRAG2 protocol with id 350 would likely get skipped as the other one was found first in a query like {{probe.sh jmx=FRAG2}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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

jboss-jira February 2019