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

Re-enable Client GC tests #4960

Merged
merged 4 commits into from
Dec 6, 2018
Merged

Re-enable Client GC tests #4960

merged 4 commits into from
Dec 6, 2018

Conversation

endocrimes
Copy link
Contributor

@endocrimes endocrimes commented Dec 4, 2018

This PR renables the client garbage collection tests that were disabled
during the allocrunner refactor.

It also introduces a similar to the deprecated alloctestrunner interface
for debugging use. I'm planning on cleaning this up a bit more tomorrow
and probably renaming it, depending on if anything else is dependent.

The previous MaxAllocs test was actually an integration test that now
has some strange behaviour that I'm still working on resolving as part
of my work on GC performance. To unblock that work, I'm rming it for
now, and replacing the underlying MaxAllocs behaviour test with a
unit test.

client/gc_test.go Outdated Show resolved Hide resolved
client/gc_test.go Outdated Show resolved Hide resolved
client/gc_test.go Outdated Show resolved Hide resolved
The previous integration test was broken during the client refactor, and
it seems to be some sort of race with state updating.

I'm going to try and construct a replacement test as part of work on
performance, but for now, the underlying behaviour is still being
tested.
@endocrimes
Copy link
Contributor Author

@dadgar I ended up fixing the integration test - ptal

client/gc_test.go Outdated Show resolved Hide resolved
@endocrimes endocrimes merged commit e668e55 into master Dec 6, 2018
@endocrimes endocrimes deleted the dani/b-gc-tests branch December 6, 2018 22:18
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants