Repository navigation
v0.10.0
Added
-
Whole-plan timeout.
lanq run --plan --plan-timeout M, or a top-levelplan_timeout: Minlanq.yml(1 to
10080 minutes; the command line replaces the file's value;plan_timeout:is judged by--plan-timeout's own
parser). The clock starts after the command-line checks and the snapshot. It covers waiting for slots, the jobs and
the baseline reruns. When the time runs out lanq prints[lanq] plan_timeout: 60 min reached; stopping N started job(s), and then:- running jobs are stopped and cleaned up, and end
TimedOut(124); - jobs waiting for a slot end
TimedOut; - jobs not started yet are
Skipped("not started: plan_timeout reached"); - unfinished baselines are
inconclusive; jobs.jsonlrecords the stopped jobs asTimedOut, neverCancelled.
The plan is
TimedOut(124) unless aFailedorRejectedjob decides it, also when nothing was running (between
after:waves, or with every job waiting). A job's owntimeout:still applies, and Ctrl+C before the limit still
ends the planCancelled(130).--jsonadds the conditionalplanTimeoutMinutesandplanTimedOut: true
(whenever the limit came due before the plan finished its work, a--fail-fasthold included; not when it came
only during the last cleanup). The dry run shows the limit on aTimeout:line and warns when history's expected
critical path is longer.
--plan-timeoutwithout--planis refused (exit 2). Thefix_codestep says where to look and that raising
the limit is the developer's decision. It never suggests a command. - running jobs are stopped and cleaned up, and end
-
Narrowing a plan from the command line.
--on,--sizeand--min-sizenow work with--plan, where they
were refused before. They narrow every selected job and never widen one:- a job's own
on:is intersected with--on, or--onapplies alone when the job has none; - its size classes are intersected with the command line's.
The dry run prints each job's narrowed
lanq runline. An unknown--onname is refused before any network (exit
2). A job the narrowing leaves with no machine ends the plan before the snapshot, with nothing sent:NoCapacity
(75,retryable: false), for example "--on big-01 leaves job 'unit-windows' no machine (its on: [micro-01])". Its
nextStepsareask_developer, thenfix_command: the same command with--onlyset to the jobs that can still
run, leaving out every job that starts after a narrowed-out job (directly or not), so no job runs without its
prerequisite. That--onlyreplaces any--onlygiven, the narrowing is kept, and the step is not safe to run
unattended (its dry run is). Without these options a plan behaves
exactly as before. - a job's own
-
Plan fetch limits and folder.
lanq.ymlgainsfetch_maxandfetch_max_files, on a job or indefaults:
(where they apply to the jobs that fetch). They are--fetch-maxand--fetch-max-files, and may only lower the
200 MB / 500-file defaults: a larger value is refused (exit 2) with "lanq.yml may lower fetch limits (at most 200M /
500 files); a larger limit is the developer's choice: lanq run --plan --fetch-max 1G".fetch_diris not a
lanq.ymlkey: it is refused with a hint to--fetch-dir. With--plan, the developer's--fetch-dir,
--fetch-maxand--fetch-max-files(refused with--planbefore) apply to every selected job that fetches. They
replace the file's values, up to the 2 GB / 5,000-file ceiling, and are refused when no selected job fetches. There
is no plan-wide total: at worst a plan writes the fetching jobs times the per-job limit (6.4 GB for 32 jobs at the
defaults). -
lanq statsby plan job. Plan jobs injobs.jsonlnow carryplanFile, the plan file's full local path (v
stays 2).lanq statsgroups plan jobs by plan file and job name, with one run per plan run:- completed when all N shards were recorded and each one's last attempt completed (a shard that
--fail-fastor
Ctrl+C cancelled leaves no record, so such a run is other); - failed when any failed;
- other otherwise.
The wall time runs from the first start to the last end.
--jsonalways carriesplanJobs(planFile,job,
runs,completed,failed,other,medianSeconds,p90Seconds,lastRunUtc,lastShards). It is capped at
500 likecommands, with the conditionalplanJobsMore. The text adds a "Plan jobs" table. Records written before
0.10.0 group underplanFile: null. Clones of one repository in different folders count separately; on Windows a
path that differs only in case is the same plan file. Baseline reruns are left out. - completed when all N shards were recorded and each one's last attempt completed (a shard that
For coding agents
- An agent may narrow a plan with
--on/--size/--min-size. The suggestedfix_commandrerun after a narrowing
leaves jobs out, so it is neversafeToRunUnattended(only its dry run is): the agent asks the developer before
running it, and then reports the jobs it left out. It never editslanq.yml(on:,size:,min_size:) to widen
a job. - A plan with
planTimedOut: trueis reported with where it was slow. Raising--plan-timeoutorplan_timeout:is
the developer's decision, never a way to make a plan pass. - An agent never raises
--fetch-maxor--fetch-max-files, never addsfetch_maxtolanq.ymland never picks a
--fetch-dirthe developer did not name to get files through. It reportsfetchSkippedinstead.
Project
scripts/smoke-workers.ps1scenario 8 now runs on a 0.10 binary (an older one is N/A):--plan-timeout 1must end a planTimedOut(124), with its job cleaned up;--plan --onmust put every job on the machine named;- a narrowing that leaves a job no machine must be
NoCapacity(75,retryable: false) with a rerun--only.
Full changelog: https://github.com/jangolath/lanqueue/blob/main/CHANGELOG.md
Full Changelog: v0.9.2...v0.10.0