[JBoss JIRA] (JBIDE-24188) CDKv3 terminal output in IDE is ugly when using hyperv
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24188?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24188:
---------------------------------------
Once https://github.com/jbosstools/jbosstools-openshift/pull/1556 is merged we need to check if this helps with this issue or not.
> CDKv3 terminal output in IDE is ugly when using hyperv
> ------------------------------------------------------
>
> Key: JBIDE-24188
> URL: https://issues.jboss.org/browse/JBIDE-24188
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Environment: Windows 10, x86_64, hyper V.
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.5.1.AM2
>
> Attachments: Terminal-HyperV.png, cdk3-hyperv-terminal
>
>
> While starting/stopping CDKv3 server adapter, you can observe flashing window (coming from hyperV) in terminal tab. The output looks bit ugly, there is pretty much space. When starting/stoping minishift from windows command prompt, you can see such blue flashing/blinking window, too. When I tried cygwin terminal, this did not happen. I am not sure if we can do anything about it, it seems like upstream/system issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months
[JBoss JIRA] (JBIDE-24903) Sonar: report correct test coverage (by using a build that does not use pack2000)
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24903?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24903:
-----------------------------------------
for us it seems that the isseu comes from the fact that the jacoco files are not created and then searched at the exact right place:
{quote}00:15:21.026 [INFO] --- jacoco-maven-plugin:0.7.9:prepare-agent (default) @ core ---
00:15:21.027 [INFO] argLine set to -javaagent:/home/jenkins/workspace/jbosstools-fuse.sonar_master/.repository/org/jacoco/org.jacoco.agent/0.7.9/org.jacoco.agent-0.7.9-runtime.jar=destfile=/home/jenkins/workspace/jbosstools-fuse.sonar_master/target/jacoco.exec,append=true,includes=org.jboss.tools.*
00:15:21.028 [INFO]
00:15:21.028 [INFO] --- jacoco-maven-plugin:0.7.9:prepare-agent (agent-for-ut) @ core ---
00:15:21.029 [INFO] argLine set to -javaagent:/home/jenkins/workspace/jbosstools-fuse.sonar_master/.repository/org/jacoco/org.jacoco.agent/0.7.9/org.jacoco.agent-0.7.9-runtime.jar=destfile=/home/jenkins/workspace/target/jacoco.exec,append=true,includes=org.fusesource.ide.*:org.jboss.tools.fuse.*{quote}
{quote}
01:07:33.050 [INFO] Sensor JaCoCoSensor [java]
01:07:33.050 [INFO] Analysing /home/jenkins/workspace/jbosstools-fuse.sonar_master/sources/target/jacoco.exec
01:07:33.051 [INFO] Analysing /home/jenkins/workspace/jbosstools-fuse.sonar_master/sources/target/jacoco-it.exec{quote}
> Sonar: report correct test coverage (by using a build that does not use pack2000)
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-24903
> URL: https://issues.jboss.org/browse/JBIDE-24903
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Labels: build, sonar, test, test-coverage
> Fix For: 4.5.x
>
> Attachments: image-2017-08-29-14-07-45-069.png, image-2017-08-29-14-11-01-604.png
>
>
> Currently our [Sonar instance|https://sonarcloud.io/dashboard?id=org.jboss.tools%3Aopenshift] erroneously reports our test coverage with 0.8%
> !image-2017-08-29-14-07-45-069.png!
> According to [~lhein] this is caused by the fact that we build using pack200. In Fuse Tools they added a build in jenkins just for sonar, which is *NOT* using pack200 and their [sonar analysis|https://sonarcloud.io/dashboard?id=fusetools] therefore reports their test coverage more accurately at 29%
> !image-2017-08-29-14-11-01-604.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 2 months