trafodion-firefighters team mailing list archive

["Reynaga, Carlos" <carlos.reynaga@xxxxxx>]

Ok, I will send you a separate email to let you know when the build servers are offline and ready for you to access.  -Carlos

From: Subbiah, Suresh
Sent: Monday, June 30, 2014 3:28 PM
To: Varnau, Steve (Trafodion); Reynaga, Carlos; trafodion-firefighters@xxxxxxxxxxxxxxxxxxx
Cc: Bouaziz, Khaled; Narain, Arvind; Sundaresan, Sandhya
Subject: RE: Trafodion daily test results

Thank you Carlos.

There are no new problems here. All problems that we see are known and are being worked upon. However we will need access to the build machine for two of these problems I think

Here is what I know
Core/test002, test005, test038 & Seabase/test010 -> sqlci cored in the middle of our test. This is likely the core we have been seeing from JNI layer for several months now. No estimated time for fix
Hive -> Sandhya and Suresh looking at the problem. This has shown up 3-4 times now and we have a stack of the hang, though no clear solution yet. We will need access to the machine "slave10", as this problem does not show on EC machines or our workstations.
Seabase/test015 -> Khaled is working on this one. He may need access to "slave05".
Udr/test100, test101 -> Arvind is working on this one, no machine access likely needed.

Thanks
Suresh



From: Trafodion-firefighters [mailto:trafodion-firefighters-bounces+suresh.subbiah=hp.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Varnau, Steve (Trafodion)
Sent: Monday, June 30, 2014 5:20 PM
To: Reynaga, Carlos; trafodion-firefighters@xxxxxxxxxxxxxxxxxxx<mailto:trafodion-firefighters@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Trafodion-firefighters] Trafodion daily test results

The daily build publishing (last two jobs) did not post the builds due to a missing 'scp' configuration in jenkins. Should be fixed now.

-Steve

From: Trafodion-firefighters [mailto:trafodion-firefighters-bounces+steve.varnau=hp.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Reynaga, Carlos
Sent: Monday, June 30, 2014 15:17
To: trafodion-firefighters@xxxxxxxxxxxxxxxxxxx<mailto:trafodion-firefighters@xxxxxxxxxxxxxxxxxxx>
Subject: [Trafodion-firefighters] Trafodion daily test results

Hi,

These are the results from last night's build.

https://jenkins01.trafodion.org/job/traf-pub-release/2/


  *   core-regress-catman1 #2<http://jenkins01.trafodion.org/job/core-regress-catman1/2/>: SUCCESS
  *   core-regress-charsets #2<http://jenkins01.trafodion.org/job/core-regress-charsets/2/>: SUCCESS
  *   core-regress-compGeneral #2<http://jenkins01.trafodion.org/job/core-regress-compGeneral/2/>: SUCCESS
  *   core-regress-core #2<http://jenkins01.trafodion.org/job/core-regress-core/2/>: FAILURE - TEST002,TEST005,TEST038
  *   core-regress-executor #2<http://jenkins01.trafodion.org/job/core-regress-executor/2/>: SUCCESS
  *   core-regress-hive #2<http://jenkins01.trafodion.org/job/core-regress-hive/2/>: FAILURE - Timeout after 180 minutes
  *   core-regress-qat #2<http://jenkins01.trafodion.org/job/core-regress-qat/2/>: SUCCESS
  *   core-regress-seabase #2<http://jenkins01.trafodion.org/job/core-regress-seabase/2/>: FAILURE - TEST010,TEST015
  *   core-regress-udr #2<http://jenkins01.trafodion.org/job/core-regress-udr/2/>: FAILURE - TEST100,TEST101
  *   phoenix_test #2<http://jenkins01.trafodion.org/job/phoenix_test/2/>: SUCCESS
  *   pyodbc_test #2<http://jenkins01.trafodion.org/job/pyodbc_test/2/>: FAILURE - No test reports found...
  *   traf-pub-debug #2<http://jenkins01.trafodion.org/job/traf-pub-debug/2/>: UNSTABLE
  *   traf-pub-release #2<http://jenkins01.trafodion.org/job/traf-pub-release/2/>: UNSTABLE
-Carlos-