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

Flame tests are too brittle #2681

Open
charleskawczynski opened this issue Feb 14, 2024 · 4 comments
Open

Flame tests are too brittle #2681

charleskawczynski opened this issue Feb 14, 2024 · 4 comments

Comments

@charleskawczynski
Copy link
Member

It seems that very minor changes can result in our flame allocation tests to break. I suspect that this is due to inference failures, and we should probably fix this. A quick patch for now, to at least alleviate some of the headache is to use a buffer, like we do for the threaded tests (which are inherently flakey).

Thoughts @Sbozzolo?

@charleskawczynski
Copy link
Member Author

I think they're even flakey, which is worse. I updated the allocation limits in #2673, and re-running still resulted in failure. This is another indicator that the issue is related to inference.

@charleskawczynski
Copy link
Member Author

#2673 is going to change buffer = occursin("threaded", job_id) ? 1.4 : 1 to buffer = occursin("threaded", job_id) ? 1.4 : 1.1 so that we have a bit of a buffer.

@charleskawczynski
Copy link
Member Author

But we should revert this and fix the issue.

@Sbozzolo
Copy link
Member

Sbozzolo commented Feb 14, 2024

I had precisely the same thought and I would have proposed the same solution.

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

No branches or pull requests

2 participants