@pocmatos can you fix the scan-build docker container? https://github.com/racket/racket/runs/3354259562

@samth let me take a look at it now.

oh - how did this happen?

Might be related to the release debian release.

yes, that looks likely

@mflatt do you know what’s going wrong here: https://github.com/racket/racket/runs/3354259713#step:6:10746 ?

Looks like there’s still a problem with the raco setup change.

I bet it’s specific to a compile-any build.

No… I haven’t been able to replicate the problem on my machine, yet. My current guess is that it’s a filesystem race (but that’s still just another guess).

@samth it seems the scan-build workflow is now working again: https://github.com/racket/racket/runs/3355497054?check_suite_focus=true

Given I updated the Z3 and LLVM versions, we might have new bugs founds due to the improvements in the last year for the clang analyzer.

Looks like the installer problem is related to using “localhost” as a client, which is good news compared to my previous guess.

I’ve pushed a change to distro-build aimed at fixing the installer problem. There are some issues with using the same directory for the server and client when building both BC and CS clients; that wasn’t an issue in the original implementation. But things tend to line up well enough, anyway, and hopefully that will go back to being the case here.