[jbosstools-dev] Red Builds, Yellow Builds & Test Failures (getting ready for Code Freeze TOMORROW)

[Nick Boldt]

Agreed. I was simply pointing out that the information is available if 
you know where to look and are willing to explore the logs a little.

Since not everyone has access to Jenkins, these logs are ALSO copied 
into the staging/{JOB_NAME}/logs/ folders for each job.

For example, the latest log for the Base component build, from master 
branch, is here:

http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_master/logs/BUILDLOG.txt

You might also like this file, as it easily shows target platform 
versions used, git revisions, slave used & other Jenkins variables:

http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_master/logs/build.properties

On 04/03/2013 06:41 PM, Max Rydahl Andersen wrote:
> On Wed, Apr 03, 2013 at 02:34:32PM -0400, Nick Boldt wrote:
>> Should probably mention too that if you're not seeing these failures
>> locally, you should look to the console logs to see how Jenkins is
>> running your jobs's builds and tests.
>>
>> For example, looking at the Base build from master branch
>> (jbosstools-base_master) I see these two calls to mvn in the log [1]:
>
> These multiline flags doesn't help much since they are *very* jenkins
> specific.
>
> the important part is the TARGET_PLATFORM_VERSION, the rest should not
> affect us - if it does we got bigger problems.
>
> /max
>
>
>> [jbosstools-base_master] $ /qa/tools/opt/apache-maven-3.0.4/bin/mvn -f
>> /qa/services/hudson/hudson_workspace/workspace/jbosstools-base_master/sources/pom.xml
>>
>> -DTARGET_PLATFORM_VERSION=4.30.5.Alpha3-SNAPSHOT
>> -DTARGET_PLATFORM_VERSION_MAXIMUM=4.30.5.Alpha3-SNAPSHOT -DDISPLAY=:1
>> "-DMAVEN_FLAGS=-B -U -fae -e -P
>> hudson,pack200,jbosstools-nightly-staging-composite,unified.target"
>> -DskipRevisionCheckWhenPublishing=false
>> -Ddownload.cache.directory=/home/hudson/static_build_env/jbds/download-cache
>>
>> -Dmaven.test.skip=true -DBUILD_ID=2013-04-02_16-57-03
>> -DJOB_NAME=jbosstools-base_master -DskipPrivateRequirements=false
>> -DBUILD_NUMBER=215
>> -Dmaven.repo.local=/qa/services/hudson/hudson_workspace/workspace/jbosstools-base_master/.repository
>>
>> clean install -B -U -fae -e -P
>> hudson,pack200,jbosstools-nightly-staging-composite,unified.target -gs
>> /home/hudson/.m2/settings.xml -s
>> /qa/services/hudson/hudson_workspace/workspace/jbosstools-base_master/settings/hudson-settings.xml
>>
>> -DTARGET_PLATFORM_VERSION=4.30.5.Alpha3-SNAPSHOT
>>
>> and
>>
>> [jbosstools-base_master] $ /qa/tools/opt/apache-maven-3.0.4/bin/mvn -f
>> /qa/services/hudson/hudson_workspace/workspace/jbosstools-base_master/sources/all-tests/pom.xml
>>
>> -DTARGET_PLATFORM_VERSION=4.30.5.Alpha3-SNAPSHOT
>> -DTARGET_PLATFORM_VERSION_MAXIMUM=4.30.5.Alpha3-SNAPSHOT -DDISPLAY=:1
>> "-DMAVEN_FLAGS=-B -U -fae -e -P
>> hudson,pack200,jbosstools-nightly-staging-composite,unified.target"
>> -DskipRevisionCheckWhenPublishing=false
>> -Ddownload.cache.directory=/home/hudson/static_build_env/jbds/download-cache
>>
>> -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true
>> -DBUILD_ID=2013-04-02_16-57-03 -DJOB_NAME=jbosstools-base_master
>> -DskipPrivateRequirements=false -DBUILD_NUMBER=215
>> -Dmaven.repo.local=/qa/services/hudson/hudson_workspace/workspace/jbosstools-base_master/.repository
>>
>> verify -B -U -fae -e -P
>> hudson,pack200,jbosstools-nightly-staging-composite,unified.target -gs
>> /home/hudson/.m2/settings.xml -s
>> /qa/services/hudson/hudson_workspace/workspace/jbosstools-base_master/settings/hudson-settings.xml
>>
>> -DTARGET_PLATFORM_VERSION=4.30.5.Alpha3-SNAPSHOT
>>
>> [1]
>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-base_master/lastBuild/consoleText
>>
>>
>> You don't need to worry about JOB_NAME, BUILD_ID, and BUILD_NUMBER, but
>> the rest of the commandline arguments are useful. Using settings.xml is
>> not required either: it only allows Jenkins to build against local
>> mirrors of content otherwise located on download.jboss.org/jbosstools/
>>
>> On 04/03/2013 12:30 PM, Nick Boldt wrote:
>>>
>>> As code freeze is tomorrow, it's that time of the month where I have the
>>> pleasure of sending reminder note that if your job is red or yellow,
>>> *you need to fix your tests*.
>>>
>>> Here are today's failures. You'll note that they've all been failing for
>>> about a week.
>>>
>>> == RED ==
>>>
>>> Base: Failing tests since Mar 24
>>>
>>> Forge: 2 test failures, 8 skipped tests since Mar 24
>>>
>>> Hibernate: COMPILATION FAILURES since ??? (last good build on Feb 18)
>>>
>>> JavaEE: 7 test failures since Mar 31; 11 test failures since Mar 21
>>>
>>> == YELLOW ==
>>>
>>> Central: 1-2 test failures since Apr 1
>>>
>>> JST: 20+ test failures since Mar 28
>>>
>>> Web Services: 917 test failures since Mar 24
>>>
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>> http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com