You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
XCTest appears to build Swift files during its tests without specifying a -module-cache-path argument. This causes it to use a default module cache path in the global /tmp directory. Default module cache paths include a random identifier, but in practice, we've found that these identifiers often collide when Swift CI is running several jobs at once version identifier, but it can't always distinguish between compilers built by different jobs, causing transient failures. Here's a recent example from a Swift CI bot.
It would be better for XCTest to provide an explicit -module-cache-path to a directory inside its own workspace. We've noticed this issue in XCTest's lit configuration, but you may want to look at your build scripts as well. SwiftPM recently made similar changes.
The text was updated successfully, but these errors were encountered:
Default module cache paths actually deliberately don't contain a random identifier; it's a hash of information identifying the compiler version. That includes the revisions being used, but not necessarily the configuration you built with.
Additional Detail from JIRA
md5: d265b5ee13637473454d1b04440413c8
Issue Description:
XCTest appears to build Swift files during its tests without specifying a
-module-cache-path
argument. This causes it to use a default module cache path in the global /tmp directory. Default module cache paths include arandom identifier, but in practice, we've found that these identifiers often collide when Swift CI is running several jobs at onceversion identifier, but it can't always distinguish between compilers built by different jobs, causing transient failures. Here's a recent example from a Swift CI bot.It would be better for XCTest to provide an explicit
-module-cache-path
to a directory inside its own workspace. We've noticed this issue in XCTest's lit configuration, but you may want to look at your build scripts as well. SwiftPM recently made similar changes.The text was updated successfully, but these errors were encountered: