Right now, all packages use the #slack-r channel for reading/writing. That means, if two packages happen to run their tests simultaneously, they can collide and cause one another to fail.
Instead, each package that writes should have its own channel. The channels for read-only packages will need to be updated at least every 90 days (and ideally they should put up a message that causes those tests to wait or something during that update), but otherwise they shouldn't be touched.
I'm putting this issue in slackcalls, but really each package will eventually want its own copy of this issue.
yonicd
commented
1 year ago
Right now, all packages use the
#slack-rchannel for reading/writing. That means, if two packages happen to run their tests simultaneously, they can collide and cause one another to fail.Instead, each package that writes should have its own channel. The channels for read-only packages will need to be updated at least every 90 days (and ideally they should put up a message that causes those tests to wait or something during that update), but otherwise they shouldn't be touched.
I'm putting this issue in slackcalls, but really each package will eventually want its own copy of this issue.