[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3945: Retry moody GitHub Actions steps

[Tahoe-LAFS]

#3945: Retry moody GitHub Actions steps
------------------------------------+-----------------------
     Reporter:  sajith              |      Owner:  sajith
         Type:  task                |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by sajith):

 Replying to [comment:3 meejah]:

 > That said, _is_ there a ticket to explore that particular "known"
 spurious failure? (It seems somewhat "well known" that test_system
 sometimes has problems...)

 A quick search for "flaky", "spurious", and
 "test_upload_and_download_convergent" here in Trac turned up #3413, #3412,
 #1768, #1084, and this milestone: [milestone:"Integration and Unit
 Testing"].

 There might be more tickets. I guess all those tickets ideally should
 belong to that milestone.

 Perhaps it might be worth collecting some data about these failures when
 testing `master` branch alone, since PR branches are likely add too much
 noise? https://github.com/tahoe-lafs/tahoe-
 lafs/actions?query=branch%3Amaster does not look ideal. However, since
 !GitHub doesn't keep test logs long enough for organizations on free
 plans, collecting that data is going to be rather challenging.

 Maybe fixing flaky tests is not worth the trouble, given the limited
 resources and the fact that this never has been annoying enough to become
 a priority. :-)

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3945#comment:4>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage