Fix various issues with WTI (#11391)
Blue committed
Mar 27, 2024 at 20:54 UTC
0e7458e294bc0a147e66572eb38d6dd6b0f74e7e
2 files changed
+17
-4
.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.3/wti.exe -o triage/wti.exe
42
+ curl.exe -L https://github.com/OneBlue/wti/releases/download/v0.1.4/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
+16
-3
@@ -153,10 +153,13 @@ actions:
153
- foreach:
154
var: user-visible-error
155
debug_message: 'Detected user visible error: $error'
156
+ skip_similar_issues: false
157
+
158
159
- when:
160
condition: 'kernel-panic'
161
debug_message: 'Found evidence of kernel panic: $kmsg'
162
+ skip_similar_issues: false
163
164
- when:
165
condition:
@@ -164,44 +167,53 @@ actions:
167
user_message: 'The logs show that WSL2 ran out of memory. Try increasing wsl2.memory in .wslconfig and see if that solves the issue.'
168
debug_message: 'Found evidence of OOM kill: $oom-error'
169
tag: needs-author-feedback
170
+ skip_similar_issues: true
171
172
- when:
173
condition:
174
and: ['vm-failed-to-start', 'hyperv-firmware-expired']
175
user_message: 'The logs show that your Hyper-V firmware is expired. Please update your Windows build and see if that solves the issue'
176
tag: needs-author-feedback
177
+ skip_similar_issues: true
178
+
179
180
- when:
181
condition:
182
and: ['vm-failed-to-start', 'corrupted-initramfs']
183
user_message: 'Your WSL installation seems corrupted. Please try to download and install the [latest WSL release](https://github.com/microsoft/WSL/releases/latest)'
184
tag: needs-author-feedback
185
+ skip_similar_issues: true
186
187
- when:
188
condition:
189
and: [{not: 'service-running'}, 'service-disabled-error']
190
user_message: 'The logs show that wslservice is disabled. Try to run (elevated command prompt): `sc.exe config wslservice start= demand` and see if that solves the issue'
191
tag: needs-author-feedback
185
-
192
+ skip_similar_issues: true
193
+
194
- when:
195
condition:
196
and: ['vm-failed-to-start', 'hns-fatal-error']
197
user_message: 'An HNS error seems to be causing WSL2 to fail to start. Adding network tag'
198
debug_message: 'Found HNS error: $error'
199
tag: 'network'
192
-
200
+
201
- when:
202
condition:
203
and: ['vm-failed-to-start', 'vmswitch-known-issue']
204
user_message: 'Known vmswitch issue found (error: $error). Adding network tag'
205
debug_message: 'Found evidence of vmswitch error: $error'
206
tag: 'network'
207
+ skip_similar_issues: true
208
+
209
210
- when:
211
condition: 'ext4-error'
212
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.'
213
debug_message: 'Found evidence of ext4 error: $error'
214
tag: 'needs-author-feedback'
215
+ skip_similar_issues: true
216
+
217
218
- when:
219
condition:
@@ -209,4 +221,5 @@ actions:
221
or: ['wsl-client-logs', 'wsl-service-logs']
222
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.**"
223
debug_message: 'Found no WSL traces in the logs'
212
- tag: 'needs-author-feedback'
\ No newline at end of file
224
+ tag: 'needs-author-feedback'
225
+ skip_similar_issues: false