Repository navigation
[Validation only - do not merge] Combined API test stack - #12687
Draft
Prangshuman Das (t-prda) wants to merge 3 commits into
Draft
Prangshuman Das (t-prda) wants to merge 3 commits into
Prangshuman Das (t-prda) wants to merge 3 commits into
Conversation
This was referenced Oct 12, 2026
github-actions
Bot
added
Build: Automation
This was referenced Oct 12, 2026
github-actions
Bot
added
Ownership: Needs Review
Prangshuman Das (t-prda)
force-pushed
the
features/646383-api-stack-combined
branch
from
October 12, 2026 11:28
8de1569 to
fff5cd6
Compare
… tests Combined tree of the API test stack (web service key auth, Expense API re-enable, APIV1/APIV2 re-enable and area fixes) on top of main. AB#646383 AB#653393 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3952f078-a881-4da8-ad96-13b727e48a91
Prangshuman Das (t-prda)
force-pushed
the
features/646383-api-stack-combined
branch
from
October 12, 2026 16:45
fff5cd6 to
6a787b9
Compare
Reset-BcTestTenant removed the tenant database with the container's Remove-NavDatabase, which takes the database offline with ROLLBACK IMMEDIATE and no query timeout. Intermittently a leftover session kept tenant2 in use and the removal blocked for about 30 minutes (the server's SQL command timeout), stretching a test job by up to two hours. End the tenant's server sessions before dismounting, then drop the database with one bounded query (120 seconds, retried) that kills the remaining user sessions on it, switches to SINGLE_USER and drops it. Log the ended sessions and the drop time so any remaining stall is diagnosable. AB#646383 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3952f078-a881-4da8-ad96-13b727e48a91
Get-NAVServerSession also returns internal sessions with negative IDs, which Remove-NAVServerSession rejects. The first one aborted the loop, so tenant sessions were not ended on most refreshes in CI. Only end sessions with a non-negative ID and end each one independently. AB#646383 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3952f078-a881-4da8-ad96-13b727e48a91
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Validation only, do not merge: the same tree as D8, used for one-shot CI and the NAV uptake check.
Single commit equal to the D8 tip of the stack, for one-shot CI and NAV uptake validation.
Related: AB#646383, AB#653393
Stack (each PR shows only its own layer; merge bottom first)
main)Experiments (on D8, do not merge): #12685 E single tenant, #12686 F no clean execution. Combined validation (do not merge): #12687, same tree as D8.
Platform:
mainalready pins BCPlatform 30.0.56112.0, which includes the SQL connection-pool fix (AB#653457).Note for CI: AL-Go's new-warning check needs a CI/CD baseline from the base branch, and
features/*bases have none, so a PR build there fails with a 404. The current CI runs were triggered while these PRs targetedmain, so their results are valid for the cumulative change.