[wp-trac] [WordPress Trac] #61701: Rate limiting can occur when sending Slack notifications out through GitHub Actions

[WordPress Trac]

#61701: Rate limiting can occur when sending Slack notifications out through GitHub
Actions
------------------------------+---------------------
 Reporter:  desrosj           |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:  6.7
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+---------------------

Comment (by desrosj):

 In [changeset:"59209" 59209]:
 {{{
 #!CommitTicketReference repository="" revision="59209"
 Build/Test Tools: Temporarily ignore Slack failures.

 When many workflows are initiated at the same time, there are often
 instances where the requests to Slack providing updates are rate limited.
 This usually happens when the Test Old Branches workflow runs and
 initiates testing for all workflows in branches that could potentially
 receive a security update.

 Even though everything was successful in the workflow except the message,
 the workflow run is marked as failed. The next time the same workflow runs
 for that branch, a “fixed” message will be sent to `#core` in Slack. The
 result is a burst of messages that is quite noisy and unnecessary.

 This temporarily adds `continue-on-error` to the jobs responsible for
 sending the messages until a better solution can be decided on.

 See #61701.
 }}}

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/61701#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform