Skip to content
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

Backout "Add tests for absolute positioning of children with padding in the parent" #1438

Closed
wants to merge 1 commit into from

Conversation

joevilches
Copy link
Contributor

Summary:
Backing out D50670457
Github PR is: 4f98bfe

That PR started failing our workflows due to a build error in gtest. It seems unlikely that it is due to that change but backing it out to see if it fixes that issue.

https://github.com/facebook/yoga/actions/runs/6657567207/job/18095847672

Differential Revision: D50708256

…in the parent"

Summary:
Backing out D50670457
Github PR is: facebook@4f98bfe

That PR started failing our workflows due to a build error in gtest. It seems unlikely that it is due to that change but backing it out to see if it fixes that issue.

https://github.com/facebook/yoga/actions/runs/6657567207/job/18095847672

Differential Revision: D50708256
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D50708256

@NickGerleman
Copy link
Contributor

@joevilches I think this is likely due to a change in the ubuntu-latest image.

The error is happening in headers for GCC stdlibc++. The clang build should instead be using LLVM libc++.

I think we could try to follow the solution in https://stackoverflow.com/questions/76859275/error-compiling-a-cpp-containing-stdchrono-errorstatic-constexpr-unsigned-fra in project-defaults.cmake, conditionally when compiling with Clang.

@NickGerleman
Copy link
Contributor

Here’s some information I found about the stdlib included by default. https://stackoverflow.com/questions/19774778/when-is-it-necessary-to-use-the-flag-stdlib-libstdc

@NickGerleman
Copy link
Contributor

Looks tentatively like #1440 should fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants