search

lipinggm / tlb

Automatically exported from code.google.com/p/tlb
0 stars 0 forks source link

Null Pointer exception while doing client side smoothing #68

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I saw this in the console log on one of the jobs while building. Need to 
investigate why this happens and fix this.

2011-03-15 11:29:14 FileUtil [INFO] checking for existance of directory 
/tmp/3690f5b2dfbb696d855bd16f7326d085 as tlb tmpdir
2011-03-15 11:29:14 FileUtil [INFO] directory 
/tmp/3690f5b2dfbb696d855bd16f7326d085 exists, creation not required
2011-03-15 11:29:14 FileUtil [INFO] unique file name old_test_times translated 
to /tmp/3690f5b2dfbb696d855bd16f7326d085/44dbf27b4ecc976bd27776371f7a95f3
2011-03-15 11:29:14 JobFamilyAwareSplitter [INFO] got total of 17 files to 
balance
2011-03-15 11:29:14 JobFamilyAwareSplitter [INFO] total jobs to distribute load 
[ 7 ]
2011-03-15 11:29:14 SmoothingServer [WARN] could not load test times for 
smoothing.: 'null'
java.lang.NullPointerException
    at java.lang.String.replace(String.java:2207)
    at tlb.utils.SystemEnvironment.substituteRefs(SystemEnvironment.java:51)
    at tlb.utils.SystemEnvironment.val(SystemEnvironment.java:42)
    at tlb.service.TlbServer.fetchLastRunTestTimes(TlbServer.java:45)
    at tlb.service.SmoothingServer.cacheOldSuiteTimeEntries(SmoothingServer.java:86)
    at tlb.service.SmoothingServer.getLastRunTestTimes(SmoothingServer.java:78)
    at tlb.splitter.TimeBasedTestSplitter.testFiles(TimeBasedTestSplitter.java:64)
    at tlb.splitter.TimeBasedTestSplitter.subset(TimeBasedTestSplitter.java:35)
    at tlb.splitter.JobFamilyAwareSplitter.filterSuites(JobFamilyAwareSplitter.java:47)
    at tlb.splitter.DefaultingTestSplitter.filterSuites(DefaultingTestSplitter.java:37)
    at tlb.ant.LoadBalancedFileSet.iterator(LoadBalancedFileSet.java:58)
    at org.apache.tools.ant.types.resources.Resources$MyCollection$MyIterator.hasNext(Resources.java:90)
    at org.apache.tools.ant.types.resources.FailFast.<init>(FailFast.java:86)
    at org.apache.tools.ant.types.resources.Resources.iterator(Resources.java:139)
    at org.apache.tools.ant.taskdefs.optional.junit.BatchTest.getFilenames(BatchTest.java:146)
    at org.apache.tools.ant.taskdefs.optional.junit.BatchTest.createAllJUnitTest(BatchTest.java:125)
    at org.apache.tools.ant.taskdefs.optional.junit.BatchTest.elements(BatchTest.java:101)
    at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.getIndividualTests(JUnitTask.java:1389)
    at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:785)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)

Original issue reported on code.google.com by itspa...@gmail.com on 15 Mar 2011 at 6:26

GoogleCodeExporter commented 9 years ago 
This is not actually a bug, we were using old version of jar.

Closing this.

Original comment by singh.janmejay on 16 Mar 2011 at 4:19