-
Notifications
You must be signed in to change notification settings - Fork 10.5k
build libdispatch by default in both linux build bot configurations #4203
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
build libdispatch by default in both linux build bot configurations #4203
Conversation
@swift-ci Please test Linux |
@swift-ci test |
@swift-ci please smoke test |
@swift-ci test linux |
@@ -722,6 +724,7 @@ llbuild | |||
swiftpm | |||
xctest | |||
foundation | |||
lbidispatch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I cannot help but feel this is a typo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep totally is, will have that fixed tomorrow when I am at a machine to be able to edit it.
Sent from my iPhone
On Aug 14, 2016, at 2:19 PM, Ryan Lovelett [email protected] wrote:
In utils/build-presets.ini:
@@ -722,6 +724,7 @@ llbuild
swiftpm
xctest
foundation
+lbidispatch
I cannot help but feel this is a typo.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
675263d
to
8d43142
Compare
Updated this to correctly spell |
@swift-ci Please test Linux platform |
@swift-ci Please smoke test OS X platform |
It looks like this finished despite not updating GitHub: OS X smoke passed, Linux failed. |
@swift-ci test linux |
Looks like the failure for linux was
does llbuild use libdispatch? |
@jrose-apple It looks like the previous failure of missing autoconf on the builders has been resolved. |
@swift-ci Please test Linux platform |
@swift-ci Please smoke test OS X platform |
yep that is totally a duplicate, I will defer to the other PR as long as we can get this done. |
@phausler I too want to see this concept get merged. Though I don't want to decide who is a duplicate of what. I just figured I would point it out since @shahmishal and @phausler are both "Apple member" contributors you might work for the same company. 😏 If I pointed it out then perhaps you could work it out amongst the group. |
@phausler sorry, I missed this PR. I will use this PR to verify all of the jobs have been setup correctly. |
@swift-ci please test Linux |
So further digging into the dispatch_io test failures:
dispatch_io_net
dispatch_select
|
@dgrove-oss, @das, @MadCoder can we just disable these tests for now and get this landed (and then perhaps revisit adding better support for these tests to have proper files to transact upon as part of the testing suite? |
Disabling the test for now makes sense to me. We can make a pass through the test suite soon and do a better job of dealing with expected input files not being present. |
dispatch PR swiftlang/swift-corelibs-libdispatch#151 I'll work on something less hacky (for example checking for /usr/share/dict/words in configure) and submit that later. |
@swift-ci Please test linux |
Build failed |
This is now failing again on autoreconf not being run again |
cc @seabaylea |
@swift-ci please test Linux |
Build failed |
@swift-ci Please test linux |
@swift-ci Please test Linux |
It looks like, for whatever reason, the previous build (before the debug) didn't pick up the reconfigure changes. FYI, those build fine for me locally. |
@swift-ci Please smoke test OS X platform |
It is green as of the latest build, going to remove the logging |
@swift-ci Please test linux |
@swift-ci please test |
Why is the OS X smoke test not running? |
This affects Linux only, so I'm merging it now. |
Linux CI builds are broken again. I plan to revert this soon. |
Mishal has just updated the build environments, which should fix the breakages. |
I don't think Mishal's changes fixed the timeout in libdispatch's tests. I think this build has the update but it's stuck and is probably going to fail in a few minutes. |
Yes - looks like it hung in the dispatch_cascade test for some reason:
That's not a failure that we'd had before. I'll quickly push a PR to disable the test for now. |
Ok - I've just disabled the test in libdispatch master. |
* Try installing specific Wasmer version * Add missing repositories to `update-checkout-config.json` * Pin Wasmer to 2.1.1 on Linux
What's in this pull request?
Foundation is prepared to handle building libdispatch by default for Linux targets. This should add libdispatch as a default argument to the build script for the build bots.