@@ -28,4 +28,27 @@ template that uses GitHub as a repository will automatically have CI enabled.
2828
2929The ``.github/workflows/smoke-test.yml `` file configures the scheduled smoke test.
3030It uses standard cron notation to start the job at 0645 every day. This time was
31- selected to be a little far away from an hour break, when most tests would likely run.
31+ selected to be a little far away from an hour break, when most tests would likely run.
32+
33+ Version culprit
34+ -------------------------------------------------------------------------------
35+
36+ If you want some help tracking down your failures, looking for upstream package
37+ updates is a good place to start. The smoke test has a "List dependencies" stage
38+ that will print out all packages installed through pip and their installed versions.
39+
40+ 1. Find the last successful run of the smoke test
41+ 1. github repo -> Actions
42+ 2. "Unit test smoke test"
43+ 3. Scroll until you find a green check
44+ 4. Pick a python versioned build
45+ 5. Expand "List dependencies"
46+ 6. Cut'n'paste the list to a file, e.g. "pass.txt"
47+ 2. Find a failed run.
48+ 1. From the "Unit test smoke test" page, find the first red check
49+ 2. Pick a python versioned build
50+ 3. Expand "List dependencies"
51+ 4. Cut'n'paste the list to a file, e.g. "fail.txt"
52+ 3. Diff those lists
53+ 1. e.g. ``diff pass.txt fail.txt ``
54+ 2. Or use an online diff tool like https://www.diffchecker.com/
0 commit comments