Repository navigation
Lab: faster runs, RemoteHub Lab app on main, Notes / policy / banner cases - #57
Merged
Merged
Conversation
A page deleted before its section (or a section before its notebook) kept its own, earlier stamp but dropped out of Recently deleted once the parent was deleted, and Delete now on the parent purged it with the parent. Deleted() and PurgeDeleted() now join the parent with LEFT JOIN: the earlier item stays listed, restores into a live parent, and is purged only with its own Delete now. Found by lab case C-NOTE-09.
…cases Faster runs - Scheduler: the longest files start first (their median in the last runs); a file that uses another VM takes a free one of any lane; a file's time limit is twice the longest it took before (at least 20 min). Replaying the runs of 16 and 19 October: the Server VMs bound a full run, a third lane takes it from 8.3 to 5.6 h (6.1 to 4.0 h). - Start-LabRun.ps1 -Quick: the build check, device files on the W11 VMs only (files marked "LabQuick: every kind" on every kind) - 5.4 / 3.4 h with two lanes, 3.7 / 2.3 h with three. -FailFast: a block skips its other cases after its first failure, no more files start once 4 in a row passed nothing. Both reach the run in options.json, which also records the commit. - Each file run writes where its time went (<result>.timing.json); Get-LabTimings.ps1 sums a run up. RemoteHub Lab (lab\LabConsole, built into lab\RemoteHubLab.exe by build\build-lab-tool.ps1) - WPF like RemoteHub: per-case status pills, progress and time left, repeat until stopped, quick / fail fast, "Changed since full run" (git's changes since the last full run's commit, by area). - Works from its own checkout of origin/main (C:\rh-lab-main), brought up to date when it opens and before every run, with the newest agent build of any worktree. Cases - C-NOTE-01..12 (C-NOTES.Tests.ps1) next to UI-NOTE in section 10.8; POL-14 and POL-15 automated (POL-CLIENT); D-BAN-11 (D-MORE); case tags on D-SHELL and D-CADHIDE.
|
Pull requests start as drafts here. Mark this one Ready for review when it's done and all checks have passed. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Faster lab runs
Replaying the runs of 16 and 19 October through the old and the new scheduler (offline, from their
console.log) shows the Server VMs bound a full run: their own files plus the time Console files hold them. Reordering alone gains nothing; a third lane and the quick build check do:-QuickInvoke-LabTests.ps1,Select-LabNextRun): the longest files start first; a file that uses another VM (Get-LabDevice) takes a free one of any lane (RHLAB_DEVICES); a file's time limit is twice the longest it took before (at least 20 min, never above its own).Start-LabRun.ps1 -Quick: device files on the W11 VMs only; files with Server-only parts say# LabQuick: every kind(S-SHARE, S-SHARE2, J-JUMP, W-SETUP2).-FailFast: PesterSkipRemainingOnFailure = Block; no more files start once 4 in a row passed nothing.results\<run>\options.json(the queue passes only-Vm/-Tag, so the watcher needs no restart); it also records the commit, repeated inrun.json.pester-<file>.xml.timing.json(minutes in the module's slow helpers, outermost call only, and the file's own time);Get-LabTimings.ps1sums a run up – where to start making tests faster.RemoteHub Lab app
lab\LabConsole(WPF-UI, links RemoteHub'sAppChrome/AppIcon), built into one filelab\RemoteHubLab.exe(git-ignored) bybuild\build-lab-tool.ps1.C:\rh-lab-main) and brings it up to date when it opens and before every run; it copies the newest agent build of any worktree (and the one before it) into that checkout'sartifacts\, plus the git-ignoredlab.local.json/lab-signing.cerfrom the checkout it was started from.lab\LabConsole.Tests(catalog, change detection, run log, estimate, quick-run plan, changed areas).Cases
C-NOTES.Tests.ps1) in section 10.8 next to UI-NOTE; POL-14 / POL-15 automated inPOL-CLIENT; D-BAN-11 inD-MORE; case tags on D-SHELL and D-CADHIDE. New module helpersInvoke-LabInSessionJson,Invoke-LabClientSql.Deleted()/PurgeDeleted()nowLEFT JOINthe parent. Found by C-NOTE-09; unit test added.Tested
dotnet build RemoteHub.sln: 0 warnings; Notes unit tests 25/25;lab\LabConsole.Tests6/6.-Quick/-FailFastand the C-NOTE / POL-14 / POL-15 cases after their fixes (D-BAN-11 passed in run 20261019-190129).