This might be related to SR-5061.

@aciidb0mb3r, is this something you've seen before? Or is it just almost certainly a compiler problem?

I haven't seen this before let me try investigating it.

@swift-ci create

I can reproduce this locally. Looks like this is due to the sandboxing. @jpsim As a workaround for now you can pass `--disable-sandbox` to swift build. I ran into linking problems after passing that flag but that seems unrelated to this bug.

It appears the workaround also avoids the assertion failure I reported in SR-5061. The two issues likely share the same root cause IMO.

It looks like the compiler is trying to create these directories, so we'll need to allow that in the sandbox.

(allow file-write-create (path "/private/var/folders/98/0fcj8gms75z3x7_01g5v_m0h0000gn/T/sources-a9889d"))
(allow file-write-create (path "/private/var/folders/98/0fcj8gms75z3x7_01g5v_m0h0000gn/T/inputs-5c6452"))

@belkadan Is this a new change? Are there more pattern that we should we aware of? These are the patterns we currently allow: https://github.com/apple/swift-package-manager/blob/master/Sources/Commands/SwiftTool.swift#L546

Let's consolidate.