Skip to content

Stabilize our CI build #3030

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

Merged
merged 4 commits into from
Nov 19, 2021
Merged

Stabilize our CI build #3030

merged 4 commits into from
Nov 19, 2021

Conversation

qwwdfsad
Copy link
Member

No description provided.

@qwwdfsad qwwdfsad marked this pull request as ready for review November 17, 2021 21:31
Otherwise, multiple pairs of install + uninstall may leave multiple cleanup threads in the state when the map is already cleaned up, but its size is not

Fixes #3028
@qwwdfsad qwwdfsad changed the title Try to trim memory usage of Dokka and Lincheck Stabilize our CI build Nov 17, 2021
Copy link
Collaborator

@dkhalanskyjb dkhalanskyjb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A change that will have my computer rejoice, but the build still failed.

@qwwdfsad qwwdfsad merged commit 9d1be50 into develop Nov 19, 2021
@qwwdfsad qwwdfsad deleted the trim-memory-usage branch November 19, 2021 11:13
yorickhenning pushed a commit to yorickhenning/kotlinx.coroutines that referenced this pull request Jan 28, 2022
* Try to trim memory usage of Dokka and Lincheck
* Disable failing test
* Do avoid concurrent-unsafe Collections.toList for working with ConcurrentWeakMap.keySet
* Do join weakRefCleanerThread in DebugProbes.uninstall

Otherwise, multiple pairs of install + uninstall may leave multiple cleanup threads in the state when the map is already cleaned up, but its size is not

Fixes Kotlin#3028
pablobaxter pushed a commit to pablobaxter/kotlinx.coroutines that referenced this pull request Sep 14, 2022
* Try to trim memory usage of Dokka and Lincheck
* Disable failing test
* Do avoid concurrent-unsafe Collections.toList for working with ConcurrentWeakMap.keySet
* Do join weakRefCleanerThread in DebugProbes.uninstall

Otherwise, multiple pairs of install + uninstall may leave multiple cleanup threads in the state when the map is already cleaned up, but its size is not

Fixes Kotlin#3028
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.

2 participants