June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-320) Fix failing UI automation tests

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-320?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-320. ---------------------------------- Resolution: Done https://github.com/Kiali-QE/kiali-qe-python/pull/57 > Fix failing UI automation tests > ------------------------------- > > Key: SWSQE-320 > URL: https://issues.jboss.org/browse/SWSQE-320 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-python-ui-te... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.

by Matthew Stevens (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ] Matthew Stevens commented on DROOLS-2656: ----------------------------------------- Yes, [~jomarko] that is just a UXD tracking spreadsheet. > PNGs for the toolbox icons for the different connector types. > ------------------------------------------------------------- > > Key: DROOLS-2656 > URL: https://issues.jboss.org/browse/DROOLS-2656 > Project: Drools > Issue Type: Sub-task > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: UX, UXTeam, VisualDesign > > PNGs for the toolbox icons for the different connector types. > Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2352) Executable model test coverage: run the optaplanner turtleTests with the executable model turned on and see if it survives the ordeal

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2352?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-2352: --------------------------------------- There are many new fixes. Tests retriggered. > Executable model test coverage: run the optaplanner turtleTests with the executable model turned on and see if it survives the ordeal > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2352 > URL: https://issues.jboss.org/browse/DROOLS-2352 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Geoffrey De Smet > Assignee: Tibor Zimányi > > For now, we're looking for a one time test. Later I presume the exe model will be come the default, so these tests would just run? > To run the optaplanner turtle tests, run all tests in optaplanner-examples with the VM parameter `-DrunTurtleTests=true`. They take 48 hours to run. You can also just run one, for example NurseRosteringSolveAllTurtleTest, but don't forget that VM parameter. > Mario Fusco says you can do this to turn on the executable model: > {code} > kieBuilder.buildAll( ExecutableModelProject.class ); > {code} > I presume you 'd need to hack that in `ScoreDirectorFactoryConfig.buildDroolsScoreDirectorFactory()`. > Note: I have no idea if this even make sense: those turtle tests use a drl file input and don't use the kie-maven-plugin. We're looking for a switch to just turn it on and see if they are all still green. Mario thinks it's possible, if I understand it correctly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10629) Server startup wrongly deploys all xml files and never stops

by Arnie Morein (JIRA)

[ https://issues.jboss.org/browse/WFLY-10629?page=com.atlassian.jira.plugin... ] Arnie Morein commented on WFLY-10629: ------------------------------------- I can't be sure, but I wonder if it could be Windows file system rights issue getting in the way? I am also seeing WFLYDS0005: Caught exception writing deployment marker file as well as others. > Server startup wrongly deploys all xml files and never stops > ------------------------------------------------------------ > > Key: WFLY-10629 > URL: https://issues.jboss.org/browse/WFLY-10629 > Project: WildFly > Issue Type: Bug > Affects Versions: 13.0.0.Final > Reporter: Arnie Morein > Assignee: Jason Greene > > I have downloaded WF 12 and 13, then imported each into Eclipse (Oxygen.3a Release (4.7.3a)), OS is Win 7/x64; then used add-user to set up admin user. Then from both the command line and from within Eclipse, when the software starts up all of the xml configuration files get deployed at the same time despite the fact that the --server-config=standalone.xml parameter is present in either environment. What's worse, it starts versioning them and re-deploying them over and over and over again. > {quote} > 15:45:42,229 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container > 15:45:42,319 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml") > 15:45:42,320 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-load-balancer.xml" (runtime-name : "standalone-load-balancer.xml") > 15:45:42,324 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-ha.xml" (runtime-name : "standalone-ha.xml") > 15:45:42,324 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-full.xml" (runtime-name : "standalone-full.xml") > 15:45:42,325 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-full-ha.xml" (runtime-name : "standalone-full-ha.xml") > 15:45:42,326 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "standalone-ee8.xml" (runtime-name : "standalone-ee8.xml") > 15:45:42,407 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server > 15:45:42,410 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 15:45:42,411 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 15:45:42,411 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) started in 6285ms - Started 549 of 746 services (326 se > rvices are lazy, passive or on-demand) > 15:45:42,575 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:45:42,578 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "standalone.boot.xml" (runtime-name: "standalone.boot.xml") > 15:45:42,581 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.initial.xml" (runtime-name: "standalone.initial.xml") > 15:45:42,724 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml") > 15:45:42,725 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.initial.xml" (runtime-name : "standalone.initial.xml") > 15:45:42,726 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.boot.xml" (runtime-name : "standalone.boot.xml") > 15:45:47,921 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 28ms > 15:45:47,928 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml") > 15:45:47,930 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "standalone.v1.xml" (runtime-name: "standalone.v1.xml") > 15:45:47,982 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 55ms > 15:45:47,984 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:45:48,059 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml" > 15:45:48,060 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml") > 15:45:48,060 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml" > 15:45:53,233 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 13ms > 15:45:53,236 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml") > 15:45:53,237 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml") > 15:45:53,249 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 15ms > 15:45:53,252 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml") > 15:45:53,340 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml" > 15:45:53,341 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml") > 15:45:53,342 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "standalone.xml" with deployment "standalone.xml"{quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-2656: ------------------------------------- I had a look on the spreadsheet, however not sure if I understand correctly, is that just for tracking what needs to be done? Am I right? > PNGs for the toolbox icons for the different connector types. > ------------------------------------------------------------- > > Key: DROOLS-2656 > URL: https://issues.jboss.org/browse/DROOLS-2656 > Project: Drools > Issue Type: Sub-task > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: UX, UXTeam, VisualDesign > > PNGs for the toolbox icons for the different connector types. > Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2253) FD_SOCK is not working in AWS environment

by Sibin Karnavar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2253?page=com.atlassian.jira.plugin.... ] Sibin Karnavar commented on JGRP-2253: -------------------------------------- <<I'm also not sure that termination on EC2/AWS closes the sockets of a process, or whether termination is more like a power-down / pull-the power-plug like behavior>> I am validating this part. Will update you soon on this. This is the only part suspicious now to check why terminating EC2 not triggering FD SOCK socket disconnects. > FD_SOCK is not working in AWS environment > ----------------------------------------- > > Key: JGRP-2253 > URL: https://issues.jboss.org/browse/JGRP-2253 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.0.10 > Environment: AWS - EC2 > Reporter: Sibin Karnavar > Assignee: Bela Ban > Fix For: 4.0.13 > > > We have our failure detection defined like below. > <FD_SOCK external_port="7804" /> > <FD timeout="3000" max_tries="3" /> > <VERIFY_SUSPECT timeout="3000" /> > Please note that we have used FD instead of FD_ALL in AWS. We will be changing it to FD_ALL later after detailed testing. > In my local, this is working perfect. As soon as I kill my node, I was able to see that view change was happening immediately with FD_SOCK. > We were not mentioning the external_port in the FD_SOCK but later I thought it may be an issue with the port and defined it as 7804 and added the same port to the security group that allows to access this port among all the nodes. So no issue with the port. > Can you please let us know if we need any additional configurations to make FD_SOCK works well in AWS. > Thanks, > Sibin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-319) Create foreman hostgroup for OCP provisioning on baremetal

by Filip Brychta (JIRA)

[ https://issues.jboss.org/browse/SWSQE-319?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-319. --------------------------------- Resolution: Done Documentation https://mojo.redhat.com/docs/DOC-1174646 > Create foreman hostgroup for OCP provisioning on baremetal > ---------------------------------------------------------- > > Key: SWSQE-319 > URL: https://issues.jboss.org/browse/SWSQE-319 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > > We have several OCP clusters running on baremetal. It would be nice to be able to provision OCP there via foreman. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2532: -------------------------------- Labels: Appformer ScenarioSimulation UX UXTeam (was: Appformer UX UXTeam) > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, ScenarioSimulation, UX, UXTeam > Attachments: RoundG2.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton resolved DROOLS-2532. --------------------------------- Release Notes Text: Reviewed with Daniele and marking as Done. Resolution: Done > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: RoundG2.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2532: ------------------------------------- [~tirelli] [~danielezonca] Adding final MVP doc references and closing out the jira, also attached a final PDF: * MVP ux related requirements: https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... * MVP wireframe click-thru: https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476068_Asset [~aglass] [~mstevens1] [~ron-murhammer] FYI ^^ > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: RoundG2.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 June 2018