Open swift-ci opened 5 years ago
Thanks!
A few things:
1. Can you try doing this from the root directory? (i.e. not from within swift). I don't remember if this makes a difference, but generally people do that (just trying to reduce the delta).
Comment by Jonathan Leonard (JIRA)
[ec2-user@ip-172-16-179-22 swift]$ ./swift/utils/update-checkout --dump-hashes
{
"https-clone-pattern": "https://github.com/%s.git",
"ssh-clone-pattern": "git@github.com:%s.git",
"repos": {
"compiler-rt": {
"remote": {
"id": "apple/swift-compiler-rt"
}
},
"llvm": {
"remote": {
"id": "apple/swift-llvm"
}
},
"swift-xcode-playground-support": {
"remote": {
"id": "apple/swift-xcode-playground-support"
}
},
"swift-stress-tester": {
"remote": {
"id": "apple/swift-stress-tester"
}
},
"clang": {
"remote": {
"id": "apple/swift-clang"
}
},
"llbuild": {
"remote": {
"id": "apple/swift-llbuild"
}
},
"cmark": {
"remote": {
"id": "apple/swift-cmark"
}
},
"lldb": {
"remote": {
"id": "apple/swift-lldb"
}
},
"swift-syntax": {
"remote": {
"id": "apple/swift-syntax"
}
},
"swift-corelibs-xctest": {
"remote": {
"id": "apple/swift-corelibs-xctest"
}
},
"ninja": {
"remote": {
"id": "ninja-build/ninja"
}
},
"swift-corelibs-foundation": {
"remote": {
"id": "apple/swift-corelibs-foundation"
}
},
"swift-integration-tests": {
"remote": {
"id": "apple/swift-integration-tests"
}
},
"swiftpm": {
"remote": {
"id": "apple/swift-package-manager"
}
},
"swift": {
"remote": {
"id": "apple/swift"
}
},
"swift-corelibs-libdispatch": {
"remote": {
"id": "apple/swift-corelibs-libdispatch"
}
},
"icu": {
"platforms": [
"Linux"
],
"remote": {
"id": "unicode-org/icu"
}
}
},
"branch-schemes": {
"repro": {
"repos": {
"compiler-rt": "f41c0bcde48835740d6d66ae97e5d0420c8fc5e4",
"llvm": "dcb9eb74a749b1d0d9a93806c155c61b0f5a18ef",
"swift-xcode-playground-support": "6c112c2e8a4d9ecead1d37d7b6b835f5dc3d84dc",
"swift-corelibs-foundation": "c82398aa779dd820c0f664b17197d9ed78e7052d",
"clang": "95cdf7c9af0dc102a3fbda4ae1f6265026ff2e30",
"llbuild": "40c302a0b2ac12e99d1355986e4f16590d1fb03e",
"cmark": "b00c889eb66d38cb8f37847efef89aeca4e4b520",
"lldb": "ef92a319d68420a4065cdc991d0e350f6e9f4eb3",
"swift-syntax": "aa2489d6359d4ac971e815bd91b7bff875183436",
"swiftpm": "5b562d7e7380c46624446065bfa9b05a8b131393",
"swift-corelibs-xctest": "0d9d2909c1590aa598f96c6c33329a1bb97ac172",
"swift-stress-tester": "2fc093642df924f6adf9de9e4397c7c6fc8b5fc8",
"ninja": "253e94c1fa511704baeb61cf69995bbf09ba435e",
"swift-integration-tests": "b5f9eec316c0446e62bb3badde5d043c8bbd8cf9",
"swift": "e1e22edb164a50eb092f6b9716b0c46877325eb7",
"swift-corelibs-libdispatch": "5bcd598e5ce08327ad8b2988e62d9fdbbe96ae64",
"icu": "b3054b334d8cf84dcae12df7e1a4f1f5c0997445"
},
"aliases": [
"repro"
]
}
}
}
Comment by Jonathan Leonard (JIRA)
I tried `./swift/utils/build-script -R` from the root and got the same result. Do I need to do a clean build from there (previous attempts were all inside swift/ including the one that produced all the cached symbols/objects).
Is this a docker container? Can I reproduce this locally?
Comment by Jonathan Leonard (JIRA)
No, not docker. It’s one of the top two AMIs (Amazon Linux) when you are asked to pick a base image when spinning up a new EC2 instance on AWS. If you wanna try it, be sure to select a lot of memory and disk.
Comment by Jonathan Leonard (JIRA)
Actually looks like there are Docker images for this system. May not be bit for bit identical but it may still reproduce the problem:
Comment by Jonathan Leonard (JIRA)
I just tried the amazonlinux docker locally with:
docker run -it amazonlinux /bin/bash
and it behaved identically up through 83% of the llvm build (before unfortunately my host ran out of disk space). I'm 99% confident that you'd get the same result if you were to successfully complete the llvm build and then proceed with the swift one.
Also, I roughly followed this guide (which is a bit out of date):
https://gist.github.com/carsonmcdonald/8edeb5ac745a1e94699e
With the following modifications:
-. yum-config-manager isn't present in the docker image and apparently not required.
-. the clang install on line 32 has to be skipped as there's no package for it.
-. symlinks on lines 35 and 36 do not refer to any files that exist and no equivalent counterparts could be found so also skipped.
-. skipped lines 38 and 39 as it already has the triple underscore version.
-. skipped git clone'ing ninja as the update-checkout clone already does that.
-. skipped the patches from lines 55 to 122 (as these applied to the Swift codebase roughly 3 years ago).
And for the llvm build, I created a /build in the ROOT_DIR, did a
cmake -G "Unix Makefiles" ../llvm/
and then
make
That's it. And I opted for the:
./swift/utils/build-script -R
version of the build incantation.
Thanks! I'll take a look.
Environment
x86_64Additional Detail from JIRA
| | | |------------------|-----------------| |Votes | 0 | |Component/s | Project Infrastructure | |Labels | Bug | |Assignee | None | |Priority | Medium | md5: 04892248e0dae2f499d11420e1aa95e5Issue Description: