dohertj2/mxaccessgw
1
0
Fork 0
Code Issues 7 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

nightly-windev failed on 47c0b646a9 #133

New Issue
Closed
opened 2026-07-29 02:01:06 -04:00 by gitea-actions · 1 comment
gitea-actions bot commented 2026-07-29 02:01:06 -04:00
Copy Link
Copy Source

The scheduled windev Worker + live-MXAccess run failed: http://gitea:3000/dohertj2/mxaccessgw/actions/runs/570 . A red nightly may mean the Windows tier is down rather than the change — see docs/GatewayTesting.md (Continuous Integration).

The scheduled windev Worker + live-MXAccess run failed: http://gitea:3000/dohertj2/mxaccessgw/actions/runs/570 . A red nightly may mean the Windows tier is down rather than the change — see docs/GatewayTesting.md (Continuous Integration).
dohertj2 commented 2026-10-13 08:53:50 -04:00
Owner
Copy Link
Copy Source

Subsequent current-tree scheduled run934 (2026-10-13, f40409a688) passed Worker529/11skipped, Gateway1193/0skipped, live integration8/0skipped and SUCCESS mode=live. This is recovery on the current tree, not an exact-old-SHA root-cause proof. Closing this recovered nightly incident report. Historical intermittent test, checkout and host-resource causes are not all proven fixed; they remain actionable in #150 with individual incident links and named failures. Current portable Rust failure is tracked separately in #149. Evidence: https://gitea.dohertylan.com/dohertj2/mxaccessgw/actions/runs/934 ; https://gitea.dohertylan.com/dohertj2/mxaccessgw/actions/runs/898 . No workflow reruns, host configuration changes or remote execution were performed.

Subsequent current-tree scheduled run934 (2026-10-13, f40409a688e2fe58323a9ea8a7c7291979f3bd80) passed Worker529/11skipped, Gateway1193/0skipped, live integration8/0skipped and SUCCESS mode=live. This is recovery on the current tree, not an exact-old-SHA root-cause proof. Closing this recovered nightly incident report. Historical intermittent test, checkout and host-resource causes are not all proven fixed; they remain actionable in #150 with individual incident links and named failures. Current portable Rust failure is tracked separately in #149. Evidence: https://gitea.dohertylan.com/dohertj2/mxaccessgw/actions/runs/934 ; https://gitea.dohertylan.com/dohertj2/mxaccessgw/actions/runs/898 . No workflow reruns, host configuration changes or remote execution were performed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area:auth
Authentication and authorization
 area:client-dotnet
.NET client library
 area:client-go
Go client library
 area:client-java
Java client library
 area:client-python
Python client library
 area:client-rust
Rust client library
 area:contracts
Protocol and generated contract work
 area:dashboard
Blazor dashboard work
 area:docs
Documentation
 area:gateway
Gateway server work
 area:tests
Automated and live tests
 area:worker
MXAccess worker process work
 blocked
Blocked by dependency
 priority:p0
Must-have / blocking
 priority:p1
High priority
 priority:p2
Normal priority
 type:docs
Documentation work
 type:feature
Feature implementation
 type:infra
Infrastructure and scaffolding
 type:test
Test work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/mxaccessgw#133
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?