March 2007 - jbosscache-dev - Jboss List Archives

jboss-cache-testsuite-jdk14 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

17 years, 2 months

1
0
0 / 0

by Manik Surtani

cc'ing jbc dev list. There was a known issue with the plain cache tutorial and demo being broken in 2.0.0.BETA1, fixed in BETA2 http://jira.jboss.com/jira/browse/JBCACHE-998 but this wasn't a compilation issue - it was to do with the bean shell scripts not being updated with new package names/imports for certain classes. Will take a look at BETA2 (currently with QA to release) as well. Regarding recompilation, I presume you downloaded the binary distro? Cheers, Manik On 28 Mar 2007, at 12:03, Bela Ban wrote: > I discovered some issues with both JBossCache 2.0 and PojoCache 2.0 > (BETA1): > - Download and unzip both distros > - ./build.sh run.pojocache.demo > > We get compile errors ! > > Now, what is beyond me, is why we even need to compile 375 files to > run a demo ! > Can we create a JIRA issue to > (1) prevent this unneeded compilation ? I understand we need to use > annonc and aopc for the PojoCache demo, but not 375 files ! > (2) fix the compilation error ? Well, I guess fixing (1) makes (2) > obsolete > -- Bela Ban Lead JGroups / JBoss Clustering team JBoss - a division > of Red Hat -- Manik Surtani Lead, JBoss Cache JBoss, a division of Red Hat Email: manik(a)jboss.org Telephone: +44 7786 702 706 MSN: manik(a)surtani.org Yahoo/AIM/Skype: maniksurtani

17 years, 2 months

1
0
0 / 0

jboss-cache-testsuite Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

17 years, 2 months

1
0
0 / 0

JBoss Retro pitfalls

by Manik Surtani

Guys, I'm documenting some of the library translation shortcomings with JBoss Retro 1.0.4.GA (which is in JBC HEAD) as I discover issues. Until these are fixed in future versions of JBoss Retro, please make sure you use alternate techniques in your code. http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossRetroPitfalls Cheers, -- Manik Surtani Lead, JBoss Cache JBoss, a division of Red Hat Email: manik(a)jboss.org Telephone: +44 7786 702 706 MSN: manik(a)surtani.org Yahoo/AIM/Skype: maniksurtani

17 years, 2 months

2
1
0 / 0

jboss-cache build.1006 Build Successful

by jboss-qa-internal＠redhat.com

17 years, 2 months

1
0
0 / 0

jboss-cache-testsuite Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

17 years, 2 months

1
0
0 / 0

jboss-cache-testsuite-jdk16 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

17 years, 2 months

1
0
0 / 0

jboss-cache-testsuite-jdk14 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

17 years, 2 months

1
0
0 / 0

JBossCache 2.0 Beta2 test code coverage analysis

by Hany Mesha

Hi all, I have run clover once again. This time against the head branch. I did 2 data points. One was against right before 2.0 Beta1 and the newer one was done yesterday just before 2.0 Beta2. I used the ant target in the build all-functionaltests to instrument and capture the code. The first data point was done on the test suite where the second data point was performed on the test suite and the source code to be able to see how much of the source code is actually exercised by the test suite. The first data point resulted in 91.8% code coverage where as the second data point resulted in 79.4%. I also did a gap analysis on the second data point to identify what test cases and what source files need to be exercised better to improve the overall coverage. I'm targeting a jump from 79.4 to 90 % before 2.0GA. I invite you to take a look at the following 2 wiki pages for both data points and see what classes and test cases need to provide more coverage: Data point 1 (pre beta1) : http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHeadCodeCoverageAnalysis Data Point 2 (pre beta2) : http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCache20Beta2CodeCoverageAna... On the wiki pages, you'll see the log of my command line test run (worth noting that I had 14 test cases reported one or more failure or error). Also, you'll only see the overall summary graph presented. If you'd like to see the graph details, you can download the detailed HTML report attached to the wiki page (*_html.zip) and unzip to drill down to a line level of the test cases or classes. Finally, I have worked a nice ant build targets for clover that I'd like to add to the build script if everyone is OK with that. Those build targets provide clover instrumentation and various reporting formats. They require adding clover.jar and clover.license to ant-dist directory. If you don't prefer adding the files for legal reason, I can just add the targets and they're manual targets anyway and should not interfere with the automated build but they will be there for future data coverage reporting. Please let me know you comments and thoughts. Cheers, Hany Hany M. Mesha Sr. Software Engineer, Consultant Novell Identity Management Engineering Toronto, Canada hmesha(a)novell.com Mobile: 416-456-6945 skype: hanymesha Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux

17 years, 2 months

3
3
0 / 0

jboss-cache-testsuite-140 build.4 Build Fixed

by jboss-qa-internal＠redhat.com

17 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosscache-dev March 2007