New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile manifests instead of interpreting them #2518
Conversation
@swift-ci smoke test |
0f5247e
to
d9958ba
Compare
@swift-ci smoke test |
d9958ba
to
7add6a2
Compare
@swift-ci smoke test |
@aciidb0mb3r Do you have an idea what is causing the failures on Linux? I haven't been able to reproduce them in Docker. |
@swift-ci smoke test Linux |
For linux, can you try reproducing by installing the toolchain in some other directory instead of system's /usr? I think it's somehow looking for the swift runtime object at the default path instead of the toolchain 🤔 |
But that wouldn't be causing the exact same issue for Linux self hosted? |
7add6a2
to
e8db9f4
Compare
@swift-ci smoke test |
e8db9f4
to
2cf7cc7
Compare
@swift-ci smoke test self hosted |
2cf7cc7
to
76a03ae
Compare
@swift-ci smoke test self hosted |
<rdar://problem/58028627>
76a03ae
to
186e424
Compare
@swift-ci smoke test |
Hi, I could not find the reason behind this change - is it a question of performance or is there something else? |
It’s a question of portability. The interpreter is usually much less stable on other platforms than the compiler.
… On 7 Feb 2020, at 08:07, Marek Fořt ***@***.***> wrote:
Hi, I could not find the reason behind this change - is it a question of performance or is there something else?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Manifest loading has been sandboxed on macOS for a while, but the change in apple#2518 broke it for 5.3. https://bugs.swift.org/browse/SR-13346 rdar://problem/66586184
* Reinstate manifest sandboxing Manifest loading has been sandboxed on macOS for a while, but the change in #2518 broke it for 5.3. https://bugs.swift.org/browse/SR-13346 rdar://problem/66586184 * Test manifest sandboxing This adds tests for manifest sandboxing. Since we made the sandbox more restrictive in 5.3, there are two tests: - in 5.2 we check if we can make a network request - in 5.3 we check if we can launch a process * Fix 5.3 sandbox profile * Use 127.0.0.1 for the attempted network request It doesn't actually matter whether or not the request would succeed since the test assumes it will always be blocked.
Manifest loading has been sandboxed on macOS for a while, but the change in apple#2518 broke it for 5.3. https://bugs.swift.org/browse/SR-13346 rdar://problem/66586184 (cherry picked from commit 4d720d6)
Manifest loading has been sandboxed on macOS for a while, but the change in #2518 broke it for 5.3. https://bugs.swift.org/browse/SR-13346 rdar://problem/66586184 (cherry picked from commit 4d720d6)
Notice that this change requires modifications to
bootstrap
andManifestLoader
to make sure the compiled manifest can find the dynamicPackageDescription
runtime library.