@open-tomato/rafa 0.52.1 → 0.53.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -32,7 +32,7 @@ step left for you. Read them there; do not run the checks again.
32
32
  | Check | Line | What is wrong |
33
33
  |---|---|---|
34
34
  | Effort | the `Effort:` line of the item's closing output | cost per task drifting up against the baseline, not explained by the item's size |
35
- | Bugs | the `Bugs:`, `Filed since` and `Recheck` lines of the item's closing output | the open count rising, a bug filed during this loop that repeats an open one (a `Recheck` line that says `reproduces`) |
35
+ | Bugs | the `Bugs:`, `Filed since`, `Filed by` and `Recheck` lines of the item's closing output | the open count rising, a bug the item's loop filed (the `Filed by this item's loop` group) that repeats an open one (its `Recheck` line says `reproduces`) |
36
36
  | Delivery | `rafa loop status`, `rafa pr list` | the run is done with no pull request, or its pull request did not merge |
37
37
  | Conflicts | `rafa pr show <pr>` | the pull request conflicts with the integration branch |
38
38
  | CI | the `CI:` line of the item's closing output (`rafa ci status --branch=stretch/<n>` gives the same verdict) | the run failed (use `gh run view <id> --log-failed` to see why), or is still running |
@@ -48,11 +48,17 @@ The readings in the closing output decide nothing; you do. The shapes:
48
48
  it reads `against no baseline`. `Effort: <stub>: no task sessions stored.`
49
49
  is a plan with no task sessions in the store. `Effort: not read (<reason>).`
50
50
  is a reading that failed.
51
- - `Bugs: <n> open.`, then `Filed since <time>: <n>.` with one indented line
52
- per bug filed after the last item, `#<n> <title>: <first line>`. `none` is
53
- a reading, not a failure. `Filed since the last item: not read: <reason>`
54
- is one that failed.
55
- - One `Recheck #<n>: <verdict>` line per bug in that list, judged as
51
+ - `Bugs: <n> open.`, then `Filed since <time>: <n>.` and the bugs filed
52
+ after the last item in two groups, each a count line and one indented
53
+ line per bug, `#<n> <title>: <first line>`.
54
+ `Filed by this item's loop (<stub>): <n>.` comes first: the bugs whose
55
+ `## Plan` section names the item's plan, the only ones you read as the
56
+ item's filings. `Filed by other sessions: <n>.` comes second: bugs that
57
+ name another plan or none, filed by other sessions on the same account.
58
+ They are board weather and say nothing about the item. `none` is a reading,
59
+ not a failure. `Filed since the last item: not read: <reason>` is one
60
+ that failed.
61
+ - One `Recheck #<n>: <verdict>` line per bug in both groups, judged as
56
62
  `rafa bug recheck` judges it, with no comment posted. The verdict is
57
63
  `reproduces`, `gone`, `flaky` (with its failed runs), `stale` or `skipped`
58
64
  (each with its reason), or `manual`. A `manual` line is followed by the
@@ -62,8 +68,8 @@ The readings in the closing output decide nothing; you do. The shapes:
62
68
 
63
69
  A line that says `not read` is the only time you type a command by hand:
64
70
  `rafa effort dashboard` for an `Effort: not read` line, and
65
- `rafa bug recheck <n>` for each bug in the `Filed since` list when the
66
- `Recheck` lines say `not read`. Read the bugs with
71
+ `rafa bug recheck <n>` for each bug in the `Filed by this item's loop`
72
+ group when the `Recheck` lines say `not read`. Read the bugs with
67
73
  `rafa issue list --type=bug --limit=200` when a bug reading is not read
68
74
  and no recheck can be run.
69
75
 
@@ -34,8 +34,10 @@ rafa effort report --trend
34
34
  ```
35
35
 
36
36
  `rafa bug recheck --all` reruns each open bug's test and prints one
37
- verdict per bug. A `gone` bug is closed by the sweep as fixed; a `flaky`
38
- one is grouped as a bug of its own, never read as fixed.
37
+ verdict per bug. A `gone` bug is closed by the sweep as fixed; a
38
+ `gone (trigger removed?)` bug stays open, since its rerun passes only
39
+ because what set it off was removed; a `flaky` one is grouped as a bug
40
+ of its own, never read as fixed.
39
41
 
40
42
  Read the roadmap's "now" epics first: their members are where the
41
43
  project already said the work is.