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

test3026 fails on i686 (and probably on other 32-bit platforms as well) #9172

Closed
ericonr opened this issue Jul 17, 2022 · 3 comments
Closed
Labels

Comments

@ericonr
Copy link
Contributor

@ericonr ericonr commented Jul 17, 2022

I did this

I ran the testsuite in a i686 chroot and test 3026 fails with the following:

URL: none
lib3026.c:67 Couldn't create thread, errno 11

I think making thread creation failures in the test non fatal might be enough, but I don't know if that's desired.

I expected the following

The testsuite should complete without failure.

curl/libcurl version

7.84.0

operating system

Linux $hostname 5.16.20_1 #1 SMP PREEMPT Thu Apr 14 17:43:53 UTC 2022 x86_64 GNU/Linux (this was run in an i686 chroot)

@bagder bagder added the tests label Jul 17, 2022
@bagder
Copy link
Member

@bagder bagder commented Jul 17, 2022

But why does this fail specifically on i686 and how do you know it is i686-specific?

@bagder
Copy link
Member

@bagder bagder commented Jul 17, 2022

Does #9173 make it work?

@ericonr
Copy link
Contributor Author

@ericonr ericonr commented Jul 18, 2022

But why does this fail specifically on i686 and how do you know it is i686-specific?

It ran to completion on x86_64. And glibc default thread stack size should be 8MB, so it makes sense that they can't fit 1000 of those in the 4GB (or 3GB, I never remember how the split goes exactly) of address space available.

I will test!

@bagder bagder closed this as completed in 0484127 Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants