February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1840) Guided decision table: Round-tripping: Export of Guided decision table as XLS

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-1840?page=com.atlassian.jira.plugi... ] Toni Rikkola closed DROOLS-1840. -------------------------------- Resolution: Duplicate Issue > Guided decision table: Round-tripping: Export of Guided decision table as XLS > ----------------------------------------------------------------------------- > > Key: DROOLS-1840 > URL: https://issues.jboss.org/browse/DROOLS-1840 > Project: Drools > Issue Type: Feature Request > Components: Guided Decision Table Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > > XLS Decision tables can be converted to Web Guided Decision Tables. We need to add the ability to export the resulting Web Guided Decision Table as XLS. Ideally the export should maintain the formatting of the original XLS decision table. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-599) Build Openshift 3.11 Cluster On B15

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-599?page=com.atlassian.jira.plugin.... ] Filip Brychta deleted SWSQE-599: -------------------------------- > Build Openshift 3.11 Cluster On B15 > ----------------------------------- > > Key: SWSQE-599 > URL: https://issues.jboss.org/browse/SWSQE-599 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matt Mahoney > Assignee: Michael Foley > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-619?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-619. --------------------------------- Resolution: Done Resolved by changing jenkins slave label for pr jobs to 'python' instead of 'kiali-ui-tests' which was configured for python3. Closed opened PR for publish-jenkins-console repo > 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 > Assignee: Filip Brychta > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11627) ExampleDS is requirement for applications that don't mandate it.

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11627?page=com.atlassian.jira.plugin... ] Bartosz Baranowski reassigned WFLY-11627: ----------------------------------------- Assignee: Sande Gilda (was: Bartosz Baranowski) > ExampleDS is requirement for applications that don't mandate it. > ---------------------------------------------------------------- > > Key: WFLY-11627 > URL: https://issues.jboss.org/browse/WFLY-11627 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Bartosz Baranowski > Assignee: Sande Gilda > Priority: Minor > Attachments: empty.war > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11627) ExampleDS is requirement for applications that don't mandate it.

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11627?page=com.atlassian.jira.plugin... ] Bartosz Baranowski updated WFLY-11627: -------------------------------------- Component/s: Documentation > ExampleDS is requirement for applications that don't mandate it. > ---------------------------------------------------------------- > > Key: WFLY-11627 > URL: https://issues.jboss.org/browse/WFLY-11627 > Project: WildFly > Issue Type: Bug > Components: Documentation > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Attachments: empty.war > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-619?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-619: ----------------------------------- Assignee: Filip Brychta (was: Matt Mahoney) > 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 > Assignee: Filip Brychta > 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, 4 months

1
0
0 / 0

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

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-619?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-619: ------------------------------------- This is caused by confusion between python2 and python3 on jenkins slave where the job is running. I will fix this. It happens for other PR jobs too. > 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 > Assignee: 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, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11779) [GSS](7.2.z) Unnecessary NoSuchMethodException during JSF app deployment

by Brad Maxwell (Jira)

Brad Maxwell created WFLY-11779: ----------------------------------- Summary: [GSS](7.2.z) Unnecessary NoSuchMethodException during JSF app deployment Key: WFLY-11779 URL: https://issues.jboss.org/browse/WFLY-11779 Project: WildFly Issue Type: Bug Components: JSF Affects Versions: 10.0.0.Final, 10.1.0.CR1 Environment: it's same at current master Reporter: Brad Maxwell Assignee: Farah Juma When you turn on TRACE logging for {{javax.enterprise.resource}} then you can notice following exception during JSF app deployment: {noformat} [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 69) java.lang.NoSuchMethodException: org.jboss.as.jsf.injection.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider): java.lang.NoSuchMethodException: org.jboss.as.jsf.injection.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider) at java.lang.Class.getConstructor0(Class.java:3082) at java.lang.Class.getDeclaredConstructor(Class.java:2178) at com.sun.faces.spi.ServiceFactoryUtils.getProviderFromEntry(ServiceFactory.java:83) at com.sun.faces.spi.AnnotationProviderFactory.createAnnotationProvider(AnnotationProviderFactory.java:70) at com.sun.faces.config.ConfigManager$AnnotationScanTask.<init>(ConfigManager.java:931) at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:385) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:227) at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187) at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:200) at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:171) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:234) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:100) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:320) {noformat} Problem is that {{org.jboss.as.jsf.injection.JandexAnnotationProvider}} doesn't have corresponding constructor (with two params - javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Amanda Han (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Amanda Han commented on DROOLS-3674: ------------------------------------ Hello [~danielezonca] there are two candidated plans for error reporting after run. The first one provides options"replace" or "keep" to go further steps to deal with error, or you can just have a look about the problem instruction and "cancel" to close the popover，“save” for operations。 !Error reporting after test run-different kinds.png|thumbnail! Another one is made for complicated problems that may need with more words to explain. We show the core bug in a short sentence, if users want to know the details, click "show more details" to know the detailed problem. !Error reporting after test run-different kinds2.png|thumbnail! WDYT??:D > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Amanda Han (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Amanda Han updated DROOLS-3674: ------------------------------- Attachment: Error reporting after test run-different kinds2.png > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

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