 |
 |
There may be more memory leaks lurking. With John's patch (and others) the testQDisp unit test is still not valgrind clean. I'm not sure yet if that's solely because the mocks don't approximate xrootd faithfully enough, or if there is also something else going on. I will get back to you on the IN2P3 cluster logs later tonight. > On May 7, 2015, at 9:09 PM, Jacek Becla <[log in to unmask]> wrote: > > So I believe the memory leak and what we thought was the timing issue is now fixed. We need to understand why Fabrice is seeing the problems > with full table scan. > > I still don't have access to the cluster, so whoever does, are you > able to get to the log files? > > I think this is our next top priority. > > > > Jacek > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the QSERV-L list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1