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

[CHECK6 PROBE] nightly-windev failed on 08b1e918a1 #140

New Issue
Closed
opened 2026-08-10 08:08:04 -04:00 by gitea-actions · 1 comment
gitea-actions bot commented 2026-08-10 08:08:04 -04:00
Copy Link
Copy Source

The scheduled windev Worker + live-MXAccess run failed: https://gitea.dohertylan.com/dohertj2/mxaccessgw/actions/runs/677 . 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: https://gitea.dohertylan.com/dohertj2/mxaccessgw/actions/runs/677 . A red nightly may mean the Windows tier is down rather than the change — see docs/GatewayTesting.md (Continuous Integration).
dohertj2 commented 2026-08-10 08:08:41 -04:00
Owner
Copy Link
Copy Source

Deliberate acceptance-test artifact — not a real failure. Created by the TST-25 acceptance Check 6 probe (test/tst25-check6-nightly-issue, run 677), which reproduced the nightly-windev job shape with the live-MXAccess step replaced by exit 1 so the if: failure() Gitea-issue step could be exercised in a real workflow run.

Result: the step fired, the built-in Actions token was masked in the log and had issue-write permission, and this issue was created by gitea-actions. The probe also validated the fix for the one defect the exercise found — the issue body previously linked the runner-internal http://gitea:3000 origin (unreachable from a browser); this issue's body carries the public https://gitea.dohertylan.com link instead. Fix lives on fix/tst25-nightly-issue-path.

The probe branch and its temporary workflow have been deleted. Closing.

Deliberate acceptance-test artifact — not a real failure. Created by the TST-25 acceptance Check 6 probe (`test/tst25-check6-nightly-issue`, run 677), which reproduced the `nightly-windev` job shape with the live-MXAccess step replaced by `exit 1` so the `if: failure()` Gitea-issue step could be exercised in a real workflow run. Result: the step fired, the built-in Actions token was masked in the log and had issue-write permission, and this issue was created by `gitea-actions`. The probe also validated the fix for the one defect the exercise found — the issue body previously linked the runner-internal `http://gitea:3000` origin (unreachable from a browser); this issue's body carries the public `https://gitea.dohertylan.com` link instead. Fix lives on `fix/tst25-nightly-issue-path`. The probe branch and its temporary workflow have been deleted. Closing.
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#140
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?