Noam Preil: > I demonstrated one > of the problems with fossil by (attempting to) install Go, which crashes > the file system _every single time_.
This is a useful bit of evidence that needs following up. The go test suite (which begins by installing and completely rebuilding go) is running 24/7 on a cluster of Raspberry Pi machines in my front hall, using fossil from 9legacy source. If you look in the plan9 arm column on https://build.golang.org you can click on any 'ok' entry (and nearly any 'fail' entry) and you'll see a successful installation of go on fossil ... literally thousands of them if you follow the sequence of 'older' pages. If you get in touch with me off list, I'd really like to work with you to find out what is different between my environment and yours which leads to such different observations. My principal reason for running the go tests has been to try to shake out more bugs from Plan 9 and fossil. So any other replicatable data I can get is most welcome. > I have found multiple deadlocks over the last few years, and only > bothered fixing one of them. In a discussion on 9fans in April 2023, the fossil-deadlocks.diff patch on 9legacy.org was mentioned. Have you witnessed any more deadlocks since you applied that one? ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T6b867aa3be7bf660-Mfa75a342b512fd72b7c71720 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription