tmp directory filled by yarn

[brian-gates]

Over time, builds have filled up /tmp/ with too many files, consuming available inodes and causing the deploy job to fail

root@adventure-bot:/var# df -i /
Filesystem       Inodes    IUsed IFree IUse% Mounted on
/dev/vda1      12902400 12902400     0  100% /

Quick fix was to cleanup /tmp/, but it seems this will arise again and a more permanent solution is needed.

root@adventure-bot:/# find /tmp/ -type f -exec rm -fv {} \;
removed '/tmp/yarn--1663260091847-0.21949611092576804/yarn'
removed '/tmp/yarn--1663260091847-0.21949611092576804/node'
removed '/tmp/yarn--1663260094893-0.8244575906711729/yarn'
removed '/tmp/yarn--1663260094893-0.8244575906711729/node'
removed '/tmp/yarn--1661835777897-0.9553691374749489/yarn'
removed '/tmp/yarn--1661835777897-0.9553691374749489/node'
<snip>

The cause is https://github.com/yarnpkg/yarn/issues/6685

A solution would be to run the following via github workflow periodically:

find /tmp/ -name "yarn*" -type d -mtime +1 -exec rm -rf {} \; > /dev/null

https://github.com/yarnpkg/yarn/issues/6685#issuecomment-503027422