conductor

CI task system
git clone git://git.finwo.net/app/conductor
Log | Files | Refs | README | LICENSE

commit 150b37b08fc94a0c6b6ef6d3b71a528c551783fd
parent feec749d57ea35ee0a322d1d5a2a8ad09967bdd5
Author: finwo <finwo@pm.me>
Date:   Sun, 20 Sep 2026 04:17:48 +0200

Repair comments the rename left saying job where they meant run

Diffstat:
Mtest/only.test.js | 2+-
Mtest/self-pipeline.test.js | 14+++++++-------
Mtest/syntax.test.js | 4++--
3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/test/only.test.js b/test/only.test.js @@ -60,7 +60,7 @@ test('a restricted task is left out of jobs for other refs', () => { test('it is left out rather than recorded as skipped', () => { // The scheduler reads a skipped task as a reason to fail the job, so a - // publish step that was never meant to job here must not appear at all. + // publish step that was never meant to run here must not appear at all. const { tasks } = compilePipeline(PIPELINE, { ref: 'refs/heads/feature' }); assert.ok(!tasks.some((j) => j.name === 'publish')); }); diff --git a/test/self-pipeline.test.js b/test/self-pipeline.test.js @@ -2,7 +2,7 @@ // // .conductor.yml is not covered by examples.test.js, and it is the one // pipeline whose breakage stops the project from building at all. It also -// encodes decisions that are easy to undo by accident: which tasks may job +// encodes decisions that are easy to undo by accident: which tasks may run // on any worker, and which need a docker socket. import test from 'node:test'; @@ -46,9 +46,9 @@ test('its tasks declare the features they actually need', async () => { ); } - // Conversely, the tasks meant to job anywhere must not demand features. + // Conversely, the tasks meant to run anywhere must not demand features. for (const name of ['style', 'test']) { - assert.deepEqual(byName.get(name).requires, [], `${name} should job on any worker`); + assert.deepEqual(byName.get(name).requires, [], `${name} should run on any worker`); } }); @@ -65,10 +65,10 @@ test('publishing is restricted to main and release tags', async () => { ); assert.ok( !tasks.some((j) => j.name === 'publish'), - `publish must not job for ${JSON.stringify(ref)}`, + `publish must not run for ${JSON.stringify(ref)}`, ); - // The rest of the pipeline still has to job on a branch. - assert.ok(tasks.some((j) => j.name === 'test'), `test should still job for ${JSON.stringify(ref)}`); + // The rest of the pipeline still has to run on a branch. + assert.ok(tasks.some((j) => j.name === 'test'), `test should still run for ${JSON.stringify(ref)}`); } for (const ref of ['refs/heads/main', 'refs/tags/v1.2.0']) { @@ -76,6 +76,6 @@ test('publishing is restricted to main and release tags', async () => { await fs.readFile(path.join(ROOT, '.conductor.yml'), 'utf8'), { source: '.conductor.yml', arches: ['x86_64'], ref }, ); - assert.ok(tasks.some((j) => j.name === 'publish'), `publish should job for ${ref}`); + assert.ok(tasks.some((j) => j.name === 'publish'), `publish should run for ${ref}`); } }); diff --git a/test/syntax.test.js b/test/syntax.test.js @@ -2,11 +2,11 @@ // // Most modules are covered because a test imports them, but entry points // and the dashboard are never imported by anything: the entry points start -// listeners, and the dashboard only ever jobs in a browser. A syntax error +// listeners, and the dashboard only ever runs in a browser. A syntax error // in either would otherwise reach a deployment. // // node --check parses without executing, which is what makes this safe to -// job over files that would start a server on import. +// run over files that would start a server on import. import test from 'node:test'; import assert from 'node:assert/strict';