Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
hi @bbockelm I was wondering if have any other traces from other occurrences of deadlocks, e.g. 3 or 4 more, and if you could also attach them. (I'm not asking you to collect them if you don't have them - but the reason is to answer some questions I'd been thinking over, e.g. whether the problem details are always very similar, and some of the details of the traces, but it seems simplest to attach the traces if you have some and I can try to answer my own questions from those!)
If there was a proposed solution I was wondering to what extent you might be able to test: i.e. you need a release (where we're presumably reasonably sure the problem is fixed) or if you might consider testing a patch (e.g. building a library, substituting on some hosts) on enough machines so that in a reasonable time you could say if the problem is likely fixed. I realise you may not be in a position to do that; there might be several people involved e.g. in building containers or in the Ops effort to run the service which probably don't include procedures to do that type of testing; but I ask since it could be a useful approach.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
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