* Deduplicate hard delete and timer fail flaky tests better (#80817)
`Flaky test create_and_destroy: /obj/item/organ/internal/ears hard
deleted 1 times out of a total del count of 495`
->
`Flaky hard delete: /obj/item/organ/internal/ears`
`Flaky test monkey_business: Invalid timer: Timer: Timer: 2433
([0x2100859b]), TTR: 328041, wait:2 Flags: TIMER_CLIENT_TIME,
TIMER_STOPPABLE, callBack: [0x2105a831], callBack.object:
/datum/looping_sound/showering[0x210085b4](/datum/looping_sound/showering),
callBack.delegate:/datum/looping_sound/proc/start_sound_loop(), source:
code/datums/looping_sounds/_looping_sound.dm:220Prev: NULL, Next: NULL,
SPENT(328041), QDELETED, NO CALLBACK world.time: 942.5, head_offset:
600, practical_offset: 686, REALTIMEOFDAY: 328041`
->
`Flaky test monkey_business: Invalid timer:
/datum/looping_sound/proc/start_sound_loop() on
/datum/looping_sound/showering`
I will close every flaky test report with these patterns so that they
are repopulated with the new deduplicated names.
* Deduplicate hard delete and timer fail flaky tests better
---------
Co-authored-by: Mothblocks <35135081+Mothblocks@users.noreply.github.com>
* [TEST-MERGE FIRST] Allows all limbs to be dismembered and significantly refactors wounds
* ah fuck it
* test
* edaawdawd
* Revert "edaawdawd"
This reverts commit 47be710fe61a1f4ca79212b29b3e88bf05ec9a3a.
* nothing but sheer hatred
* freaawd
* dzfxg
* Fixing some diffs here while we are at it.
* These are deprecated and should be removed
---------
Co-authored-by: nikothedude <59709059+nikothedude@users.noreply.github.com>
Co-authored-by: nikothedude <simon.prouty@gmail.com>
Co-authored-by: Giz <13398309+vinylspiders@users.noreply.github.com>
Rerun flaky tests automatically, and create issue reports for them (#71519)
Adds a new workflow that will try to automatically detect and rerun
flaky tests, and create an issue report for them.
The detection mechanism is heuristic: if exactly ONE job fails in the CI
Suite, then it is assumed to be flaky, and will be rerun. If the next
run succeeds, then it will create an issue report for that flaky test if
one does not already exist. It will do its best to create a unique but
consistent identifier, aided by PRs like #71515. You can find an example
here: https://github.com/Mothblocks/ss13-workflow-testing/issues/20.
Maintainers can also rename the issue if they wish, it will still be
able to find it.
While there is a chance for this mechanism to go wrong and create bogus
issue reports, it IS possible to easily disable actions, I did it for
the stale one just a bit ago. Most likely, this mechanism going wrong is
going to be the result of randomness leaking in tests, like random human
names, so this can be solved in the tests themselves. I find it
extremely unlikely, but in the worst case scenario where this happens
often, we can add a way for maintainers to edit the issue report and
include a regex to match for runtimes. Just an idea.
Includes a few large-ish downloaded logs from past failures that are
interesting in unique ways. These are used for tests of the title
generator.
Co-authored-by: Mothblocks <35135081+Mothblocks@users.noreply.github.com>
