Blog: The Triage Rhyme

A fun little ditty to aid triagers in remembering one developer's take on some key aspects of the triage process. Signed-off-by: Adam Farley <[email protected]>
adoptium · Sep 18, 2023 · db4a114 · db4a114
1 parent 8b37c3b
commit db4a114
Show file tree

Hide file tree

Showing 8 changed files with 59 additions and 0 deletions.
diff --git a/content/blog/the_triage_rhyme/A.png b/content/blog/the_triage_rhyme/A.png
diff --git a/content/blog/the_triage_rhyme/E.png b/content/blog/the_triage_rhyme/E.png
diff --git a/content/blog/the_triage_rhyme/Full_Alphabet.png b/content/blog/the_triage_rhyme/Full_Alphabet.png
diff --git a/content/blog/the_triage_rhyme/G.png b/content/blog/the_triage_rhyme/G.png
diff --git a/content/blog/the_triage_rhyme/I.png b/content/blog/the_triage_rhyme/I.png
diff --git a/content/blog/the_triage_rhyme/R.png b/content/blog/the_triage_rhyme/R.png
diff --git a/content/blog/the_triage_rhyme/T.png b/content/blog/the_triage_rhyme/T.png
diff --git a/content/blog/the_triage_rhyme/index.md b/content/blog/the_triage_rhyme/index.md
@@ -0,0 +1,59 @@
+---
+title: The Triage Rhyme
+date: "2023-09-18T16:00:00+00:00"
+author: adamfarley
+description: A simple ditty to help triagers remember key information about the triage process.
+tags:
+  - adoptium
+---
+
+The build/test triage process can sometimes be difficult to remember at the end of a long day.
+
+This blog was created to help triagers remember some key aspects of triage, and to give hard-working community supporters a well-deserved chuckle.
+
+Note that this is not meant to be a substitute for the [existing triage documentation](https://github.com/adoptium/aqa-tests/blob/master/doc/Triage.md).
+
+And now, without further ado, I present:
+
+
+## The Triage Rhyme
+
+<details>
+<summary>![T](T.png) is for TReSS, so go take a gander. We're perusing a mess, of pipelines red/amber.</summary>
+- Identify failed pipelines via TRSS.
+- Red means a job has failed. Framework errors, build failures, etc.
+- Amber often means that a unit test failed, but the test framework completed.
+- Grey usually means a timeout.
+</details>
+<details>
+<summary>![R](R.png) means Results, a text file conniption! Search "Error: "! Search "FAILURE"! Search Donner and Blitzen!</summary>
+- Search failed job output for error keywords.
+- "Error:" is often associated with errors.
+- "FAILURE" usually means a subjob failed, like Smoke Tests after a build.
+- Donner and Blitzen are Santa's reindeer. They are a metaphor for "search for everything".
+</details>
+<details>
+<summary>![I](I.png) gets you Issues, or maybe gets none. Un problem, un issue; you only need one.</summary>
+- Search repositories for related issues. 
+- An existing issue means further triage is not needed.
+- Put a link to your failure in any existing issues, to keep the issue up-to-date.
+</details>
+<details>
+<summary>![A](A.png) checks the Archives, dig till you drop. You will find the cause, for this unforeseen stop.</summary>
+- Do some digging to find the general source of the issue. 
+- Frequent offenders are changesets and test/build framework updates.
+</details>
+<details>
+<summary>![G](G.png) will be Gather, with many a fact! Make an issue on git, help the bug fixer act.</summary>
+- Raise an issue in the relevant repository.
+- Be sure to add job links, log files, and a copy of the error message. 
+- Always start with a summary of the problem, to help bug fixers grasp the issue quickly.
+</details>
+<details>
+<summary>![E](E.png) brings an End, so go rest your eyes. Triage is a quest, with knowledge the prize.</summary>
+- Triage is about creating a knowledge base before task prioritization.
+- Always look for bigger fish before trying to solve anything. 
+- Work smarter, not harder. :)
+</details>
+
+## The End