 |
 |
I hope that @bbockelm has better behaviour (no deadlocks) in the instances with https://github.com/xrootd/xrootd/commit/eae57b46953bbb039db9514369ec45ae2b18987b. But I've seen that in tests I can still trigger a deadlock, where the trace seems very similar to this issue; so I suspect that could still be problems. I'll attach my test, instructions/some extra logging and trace of an observed deadlock shortly. I believe that a fix for #1934 (i.e. PR #1946) will address the situation that leads to the particular deadlock I saw, so I think we have a reasonable next approach to tackle this issue if necessary. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1979#issuecomment-1494281713 You are receiving this because you commented. Message ID: <[log in to unmask]> ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1