Conserving memory while verifying the plugin

IntelliJ Platform
1

We have a GitHub action that runs verifyPlugin on changes, and I found that these were failing due to out of memory errors because we are running verify for 3 versions of the IntelliJ platform. I tried to delete IDE downloads in between verifications, but this required some code to perform file deletion (that only partially works) and calling verifyPlugin on each version sequentially from a bash script. (More context in Reduce memory use of verify bot by deleting IDEs after verify by helin24 · Pull Request #8637 · flutter/flutter-intellij · GitHub)

I’m wondering if others have run into this problem and found more graceful ways to do this?

2

Given Reduce memory use of verify bot by deleting IDEs after verify by helin24 · Pull Request #8637 · flutter/flutter-intellij · GitHub, have you checked why your /dev/root is almost full? It could be due to your Gradle cache. Don’t cache it or perform some cleanup.
Also, by memory, do you mean RAM or storage space? The PR is a bit confusing.

3

We have seen a disk space issues in the IntelliJ SDK Docs repository which uses GitHub Actions for some preliminary checks including verifyPlugin.

The e15993201f3f927376 commit in the JetBrains/intellij-sdk-docs helps: it cleans the underlying Ubuntu Docker filesystem to provide more disk space.

4

Ah yes, by memory I’m referring to storage space; sorry for the confusion.

I’m not sure why /dev/root is almost full! That’s also a mystery to me. I suppose I could do some further printing of what’s in there and how much memory it’s taking. I can try out turning off caching. It sounds like there are multiple types of gradle caches though; do you know what kinds of things gradle caches that could be taking up storage space in this situation?

5

Thanks for this example - I may try this out as well!