[wp-trac] [WordPress Trac] #62221: GitHub Actions updates and improvements for 6.8

[WordPress Trac]

#62221: GitHub Actions updates and improvements for 6.8
--------------------------------------+---------------------
 Reporter:  desrosj                   |       Owner:  (none)
     Type:  task (blessed)            |      Status:  new
 Priority:  normal                    |   Milestone:  6.8
Component:  Build/Test Tools          |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-patch has-unit-tests  |     Focuses:
--------------------------------------+---------------------

Comment (by desrosj):

 Replying to [comment:75 flixos90]:
 > Again, as long as this was a once-off hiccup due to something particular
 with this change, it's not an issue, but it would be great to know why it
 happened, to rule out that there's an actual problem. Like for instance,
 did one of us rerun one of the workflows that sends the data for that
 commit, and it actually sent the data both times?

 After [59679], every workflow that ran as a result failed because of a bug
 in the Slack workflow. After it was fixed in [59681], I reran all of them.
 So seems we don't handle reruns properly (or we do and just don't account
 for two records)? Not sure what the preferred behavior is. But because the
 very last step responsible for sending the Slack message failed and not
 the testing job, each run submitted a report.

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