You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would argue that since this is created with cloudml using --job-dir, it should be cloudml the one cleaning it. That said, in a few narrow cases, the original package is useful for troubleshooting failed runs.
On Tue, Dec 12, 2017 at 6:55 PM Javier Luraschi ***@***.***> wrote:
I would argue that since this is created with cloudml using --job-dir, it
should be cloudml the one cleaning it. That said, in a few narrow cases,
the original package is useful for troubleshooting failed runs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#63 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAGXx1F8naypyWf68i_IFRIPbBMHB2Vkks5s_xJhgaJpZM4Q_E4K>
.
I noticed that we leave a bunch of our staging packages in the staging bucket:
Should these be removed after the job completes?
The text was updated successfully, but these errors were encountered: