-
Notifications
You must be signed in to change notification settings - Fork 44
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
fix: Increase system's open file limit in integration tests #627
Conversation
Benchmark ResultsSummary
✅ See Better Results...
❌ See Worse Results...
✨ See Unchanged Results...
🐋 See Full Results...
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Happy so long as we are sure this will not run in production (might be worth checking that if unsure by adding a panic on the first line and then spinning up a server with go install
and defra start
)
@shahzadlone if you could replicate the issue you reported and confirm this solves it, that'd be useful to know! |
I confirm that it doesn't crash when doing that. The tests are not imported by defradb |
Of course it doesn't - I was being an idiot and forgot each dir gets compiled separately in go (and tests are not exceptions). Sorry for your time, and feel free to call me an idiot next time I say something like this :) |
I'm happy to do quick checks like that as it "turns the logic into intuition", at least once. Agreed that it's good to help teammates to spend efforts towards most important/useful activities. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can confirm that the file limit error disappears (did 3 runs to test).
Thanks Orpheee!
Relevant issue(s)
Resolves #623
Description
Backports code from Go 1.19 in the integration test initialization to increase open file limit to fix related error when running the tests on systems that are configured (for legacy reasons) to have very low file limit.
Draft PR as experimental and potentially controversial?
Tasks
How has this been tested?
Local
Specify the platform(s) on which this was tested: