Display a special message if the published logs don't contain any WSL traces (#11374)
* Display a special message if the published logs don't contain any WSL traces * Mark wsl-client-logs as oneshot * Update to 1.0.3
Blue committed
Mar 26, 2024 at 18:37 UTC
57783aabf2a814437762d706d8334ec4315e0d55
2 files changed
+20
-1
.github/actions/triage/action.yml
+1
-1
@@ -39,6 +39,6 @@ runs:
39
$maybe_comment = @("--comment", "${{ inputs.comment }}")
40
}
41
42
- curl.exe -L https://github.com/OneBlue/wti/releases/download/v0.1.1/wti.exe -o triage/wti.exe
42
+ curl.exe -L https://github.com/OneBlue/wti/releases/download/v0.1.3/wti.exe -o triage/wti.exe
43
44
cd triage && echo -n $message | .\wti.exe --issue ${{ inputs.issue }} --config config.yml --github-token "${{ inputs.token }}" --ignore-tags @maybe_message @maybe_comment
\ No newline at end of file
triage/config.yml
+19
@@ -138,6 +138,17 @@ rules:
138
name: ext4-error
139
capture:
140
field1: error
141
+
142
+ - logline:
143
+ provider: Microsoft.Windows.Lxss.Manager
144
+ set: wsl-service-logs
145
+ oneshot: true
146
+
147
+ - logline:
148
+ provider: Microsoft.Windows.Subsystem.Lxss
149
+ set: wsl-client-logs
150
+ oneshot: true
151
+
152
actions:
153
- foreach:
154
var: user-visible-error
@@ -190,4 +201,12 @@ actions:
201
condition: 'ext4-error'
202
user_message: 'The logs shows that a disk mount error occured. Try to [follow these repair instructions](https://learn.microsoft.com/en-us/windows/wsl/disk-space#how-to-repair-a-vhd-mounting-error) and see if that solves the issue.'
203
debug_message: 'Found evidence of ext4 error: $error'
204
+ tag: 'needs-author-feedback'
205
+
206
+ - when:
207
+ condition:
208
+ not:
209
+ or: ['wsl-client-logs', 'wsl-service-logs']
210
+ user_message: "The log file doesn't contain any WSL traces. Please make sure **that you reproduced the issue while the log collection was running.**"
211
+ debug_message: 'Found no WSL traces in the logs'
212
tag: 'needs-author-feedback'
\ No newline at end of file