Skip to content

Conversation

@apoelstra
Copy link
Contributor

This test should fail by creating a task which allocates too
much stack space, but some recent change in Travis has caused
it to succeed. Jack up the memory by a million times or so and
see if that corrects it.

@lilyball
Copy link
Contributor

If a 64GB stack doesn't fail, I have to wonder if something else is going on.

@mneumann
Copy link
Contributor

virtual memory?

@apoelstra
Copy link
Contributor Author

Hmm, it is timing out now, so I dropped the increase to only 1000x...if this is a change to increase virtual memory, I'm a little concerned that we won't be able to allocate all of it in a reasonable amount of time.

This test should fail by creating a task which allocates too
much stack space, but some recent change in Travis has caused
it to succeed. Jack up the memory to 128Gb and see if that corrects
it.
@apoelstra
Copy link
Contributor Author

At 1Tb it times out, and 128Gb the allocation succeeds...rather than continuing to bisect my way toward the Fragilest Fix Award, I think I'll leave this to somebody more creative...

@apoelstra apoelstra closed this Jul 31, 2014
bors added a commit to rust-lang-ci/rust that referenced this pull request Jan 3, 2024
…barsky

internal: Add minimal support for the 2024 edition

CC rust-lang#16146
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.

3 participants