Repository navigation
fix(migtd): report rebinding status accurately - #1100
Conversation
679dbe9 to
5fde09f
Compare
5fde09f to
46664e0
Compare
|
CI status note: the current failed checks are infrastructure failures, not patch failures.
Neither job reached compilation or tests. The remaining checks are still progressing. |
|
CI status update: |
|
CI status update: two more matrix jobs failed because the hosted runner lost communication during
Neither reached compilation or tests; these are additional infrastructure failures. |
46664e0 to
089eed8
Compare
|
CI status update for the fresh run: |
|
CI status update: the final check, |
089eed8 to
d8f5921
Compare
|
CI status update for the fresh run: |
|
CI status update: |
|
CI status update: this attempt completed 61 checks successfully. Both failed matrix jobs lost hosted-runner communication during |
d8f5921 to
f39943f
Compare
|
CI status update: |
ReportStatus can fail after a rebinding operation completes, but the current path logs completion unconditionally. Capture and log the actual status-report result so diagnostics distinguish successful notification from a reporting failure. Signed-off-by: Haitao Huang <haitaohuang@microsoft.com> Assisted-by: GitHub Copilot CLI:GPT-5.6 Sol
f39943f to
deb3233
Compare
|
CI status update: the final job, |
Summary
ReportStatusafter rebindingTesting
Previously validated during branch preparation:
cargo fmt --checkcargo xtask lib-test --crates migtd