Skip to content

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

Merged
merged 4 commits into from
Aug 20, 2016

Conversation

phausler
Copy link
Contributor

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.


@phausler
Copy link
Contributor Author

@swift-ci Please test Linux

@tkremenek
Copy link
Member

@swift-ci test

@compnerd
Copy link
Member

@swift-ci please smoke test

@tkremenek
Copy link
Member

@swift-ci test linux

@@ -722,6 +724,7 @@ llbuild
swiftpm
xctest
foundation
lbidispatch
Copy link
Contributor

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.

Copy link
Contributor Author

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.

@phausler phausler force-pushed the build_libdispatch_by_default branch from 675263d to 8d43142 Compare August 15, 2016 16:03
@phausler
Copy link
Contributor Author

Updated this to correctly spell libdispatch per @RLovelett 's catch.

@jrose-apple
Copy link
Contributor

@swift-ci Please test Linux platform

@jrose-apple
Copy link
Contributor

@swift-ci Please smoke test OS X platform

@jrose-apple
Copy link
Contributor

jrose-apple commented Aug 15, 2016

It looks like this finished despite not updating GitHub: OS X smoke passed, Linux failed.

@tkremenek
Copy link
Member

@swift-ci test linux

@phausler
Copy link
Contributor Author

Looks like the failure for linux was

/home/buildnode/jenkins/workspace/swift-PR-Linux@2/branch-master/llbuild/tests/BuildSystem/Build/missing-inputs.llbuild:13:18: error: expected string not found in input

does llbuild use libdispatch?

@phausler
Copy link
Contributor Author

@jrose-apple It looks like the previous failure of missing autoconf on the builders has been resolved.

@jrose-apple
Copy link
Contributor

@swift-ci Please test Linux platform

@jrose-apple
Copy link
Contributor

@swift-ci Please smoke test OS X platform

@RLovelett
Copy link
Contributor

This might be a duplicate of #4315 (or it a duplicate of this). Just thought I'd point that out so that effort is not duplicated (as it is starting to look like it is).

Also, you might want to check out this comment. I think this will likely become a problem on this PR as well.

@phausler
Copy link
Contributor Author

yep that is totally a duplicate, I will defer to the other PR as long as we can get this done.

@RLovelett
Copy link
Contributor

RLovelett commented Aug 16, 2016

@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.

@shahmishal
Copy link
Member

@phausler sorry, I missed this PR. I will use this PR to verify all of the jobs have been setup correctly.

@shahmishal
Copy link
Member

@swift-ci please test Linux

@phausler
Copy link
Contributor Author

So further digging into the dispatch_io test failures:

[SKIP] Large file not found (dispatch_io.c:82)
[SKIP] Large file not found (dispatch_io.c:82)
[SKIP] Large file not found (dispatch_io.c:82)
[SKIP] Large file not found (dispatch_io.c:82)
[SKIP] Large file not found (dispatch_io.c:82)
[SKIP] Large file not found (dispatch_io.c:82)
...
[BEGIN] open
    Actual: 2   No such file or directory
    Expected: 0
[FAIL] open (dispatch_io.c:246)
    dispatch_io.c:246
[BEGIN] Leaks
    Actual: 256
    Expected: 0
[FAIL] Leaks (bsdtests.c:464)
    bsdtests.c:464

dispatch_io_net

[BEGIN] client-open
    Actual: 2   No such file or directory
    Expected: 0
[FAIL] client-open (dispatch_io_net.c:97)
    dispatch_io_net.c:97

[BEGIN] open
    Actual: 2   No such file or directory
    Expected: 0
[FAIL] open (dispatch_io_net.c:236)
    dispatch_io_net.c:236

[BEGIN] Leaks
    Actual: 256
    Expected: 0
[FAIL] Leaks (bsdtests.c:464)
    bsdtests.c:464

[BEGIN] Leaks
    Actual: 256
    Expected: 0
[FAIL] Leaks (bsdtests.c:464)
    bsdtests.c:464

dispatch_select

==================================================
[TEST] Dispatch select workaround test
[PID] 6576
==================================================


[BEGIN] main_q
    Actual: 0x607280
    Expected: 0x607280
[PASS] main_q

[BEGIN] select source
    Actual: 0x7f4d1c0008c0
    Expected: 0x7f4d1c0008c0
[PASS] select source

[BEGIN] kevent read 1
    Actual: 20.000000
    Expected: <=512001.000000
[PASS] kevent read 1

[BEGIN] close
    Actual: 0
    Expected: 0
[PASS] close
/usr/share/dict/words: No such file or directory

@RLovelett
Copy link
Contributor

@phausler
Copy link
Contributor Author

@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?

@dgrove-oss
Copy link
Contributor

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.

@dgrove-oss
Copy link
Contributor

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.

@phausler
Copy link
Contributor Author

@swift-ci Please test linux

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 8d43142
Test requested by - @phausler

@phausler
Copy link
Contributor Author

This is now failing again on autoreconf not being run again

@parkera
Copy link
Contributor

parkera commented Aug 19, 2016

cc @seabaylea

@phausler
Copy link
Contributor Author

@swift-ci please test Linux

@swift-ci
Copy link
Contributor

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 8d43142
Test requested by - @phausler

@phausler
Copy link
Contributor Author

@swift-ci Please test linux

@shahmishal
Copy link
Member

@swift-ci Please test Linux

@seabaylea
Copy link
Contributor

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.

@phausler
Copy link
Contributor Author

@swift-ci Please smoke test OS X platform

@phausler
Copy link
Contributor Author

It is green as of the latest build, going to remove the logging

@phausler
Copy link
Contributor Author

@swift-ci Please test linux

@phausler
Copy link
Contributor Author

@swift-ci please test

@phausler
Copy link
Contributor Author

Why is the OS X smoke test not running?

@parkera
Copy link
Contributor

parkera commented Aug 20, 2016

This affects Linux only, so I'm merging it now.

@parkera parkera merged commit 59a7c73 into swiftlang:master Aug 20, 2016
@gparker42
Copy link
Contributor

Linux CI builds are broken again. I plan to revert this soon.
https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/7448/

@seabaylea
Copy link
Contributor

seabaylea commented Aug 20, 2016

Mishal has just updated the build environments, which should fix the breakages.

@gparker42
Copy link
Contributor

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.
https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/7450/

@seabaylea
Copy link
Contributor

Yes - looks like it hung in the dispatch_cascade test for some reason:

==================================================
[TEST] Dispatch Cascade
[PID] 19223
==================================================


[BEGIN] Process exited
    Actual: 1
    Expected: 0
[FAIL] Process exited (bsdtestharness.c:132)
    bsdtestharness.c:132
[PERF]  wall time: 0.034725
[PERF]  user time: 0.056000
[PERF]  system time: 0.008000
[PERF]  max resident set size: 17660
[PERF]  page faults: 0
[PERF]  swaps: 0
[PERF]  voluntary context switches: 43
[PERF]  involuntary context switches: 10
FAIL dispatch_cascade (exit status: 1)

That's not a failure that we'd had before. I'll quickly push a PR to disable the test for now.

@seabaylea
Copy link
Contributor

Ok - I've just disabled the test in libdispatch master.

kateinoigakukun pushed a commit that referenced this pull request Aug 31, 2022
* Try installing specific Wasmer version

* Add missing repositories to `update-checkout-config.json`

* Pin Wasmer to 2.1.1 on Linux
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.