Skip to content

[PkgConfig] Add checks for circular dependencies #184

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 6 commits into from
Feb 10, 2021

Conversation

Dadoum
Copy link
Contributor

@Dadoum Dadoum commented Jan 16, 2021

Some libraries form dependency cycles such as freetype and harfbuzz on Arch Linux. This PR tries to avoid cycles by tracking pkg-config packages dependencies and detecting two occurences of a same library in the same branch.

@tomerd
Copy link
Contributor

tomerd commented Jan 20, 2021

@swift-ci please test

@tomerd tomerd assigned abertelrud and neonichu and unassigned abertelrud Jan 20, 2021
@neonichu
Copy link
Contributor

Could we add a test for this?

@Dadoum
Copy link
Contributor Author

Dadoum commented Jan 23, 2021

I should be able add a test, but it seems that the tests are made for macOS, and tests are making my swift-test crashing on my Linux.

@neonichu
Copy link
Contributor

I should be able add a test, but it seems that the tests are made for macOS, and tests are making my swift-test crashing on my Linux.

That's a bit surprising, could you share some more information about the crash you're seeing? CI runs tests on both macOS and Ubuntu Linux at least.

@Dadoum
Copy link
Contributor Author

Dadoum commented Jan 28, 2021

on arch the process get killed and there is no crash log or whatever. Can't get anything with lldb

Test Case 'ProcessSetTests.testSigInt' started at 2021-01-28 12:19:26.285
Exited with signal code 4

and then swift-test stops

@abertelrud
Copy link
Contributor

on arch the process get killed and there is no crash log or whatever. Can't get anything with lldb

Test Case 'ProcessSetTests.testSigInt' started at 2021-01-28 12:19:26.285
Exited with signal code 4

and then swift-test stops

I'm not familiar with this test, but it looks as if it's specifically designed to test signals. That should be investigated, but could you locally mark that test as skipped while developing the unit test for this PR, just to make progress? If you have time, it would be great filing the unit test failure on bugs.swift.org with any additional information you have.

@neonichu
Copy link
Contributor

neonichu commented Feb 4, 2021

@swift-ci please test

@abertelrud
Copy link
Contributor

@swift-ci please test

@abertelrud abertelrud self-requested a review February 5, 2021 20:04
Copy link
Contributor

@abertelrud abertelrud left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@abertelrud
Copy link
Contributor

@swift-ci please test

@Dadoum
Copy link
Contributor Author

Dadoum commented Feb 8, 2021

can you relaunch test please ? @abertelrud

@abertelrud
Copy link
Contributor

@swift-ci please test

@abertelrud
Copy link
Contributor

The linux error looks like an intermitted failure.
<unknown>:0: error: module file '/home/buildnode/jenkins/workspace/pr-swift-tools-support-core-linux/branch-main/build/buildbot_incremental/foundation-linux-x86_64/module-cache/AF2QS0LIXQHC/SwiftShims-239NVYTZY614A.pcm' is out of date and needs to be rebuilt: signature mismatch

Rerunning test.

@abertelrud
Copy link
Contributor

@swift-ci please test linux

@neonichu
Copy link
Contributor

Looks like the tests have passed now, thanks for your contribution @Dadoum

@neonichu neonichu merged commit 2954e55 into swiftlang:main Feb 10, 2021
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.

5 participants