CI / Build and test (pull_request) Failing after 2m3s
CI / PostgreSQL 16 integration (pull_request) Skipped
CI / PostgreSQL 17 integration (pull_request) Skipped
CI / Docker image (pull_request) Skipped
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 4s
The owner renamed the product and moved the repository to the self-hosted Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control, and asked for Actions and a first automatic release with the server package and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md). - Chronos everywhere: a byte-exact rename of contents and paths, then a per-language review of the forms the old name's ending had dictated. - Gitea instead of GitHub: the update check, licence, issue and support links read ChronosReleasesUrl; the update check takes the highest stable version, offers a pre-release build its final release and reports a repository it cannot see as a failed check. EULA, security policy and Gitea issue forms live at the repository root. - Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release, nightly image and performance gates in the .NET SDK container with git checkout. The release cross-compiles the Windows programs, checks their icon, version and DPI manifest, packs installers and zips, publishes the Gitea release and pushes the server image (REGISTRY_TOKEN). Windows-only tests run in an opt-in job on a Windows runner (WINDOWS_RUNNER). - New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the docker-exec script, which Gitea's service containers do not allow) and pe-check. BREAKING CHANGE: programs, settings, data folders, file types, environment variables and the Docker image use the new name; nothing is migrated from Titano, which never had a release. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
38 lines
2.1 KiB
C#
38 lines
2.1 KiB
C#
using Chronos.Testing;
|
|
using Chronos.Tools.Commands;
|
|
|
|
namespace Chronos.Tools.Tests;
|
|
|
|
/// <summary>The fixtures command reports a sample it cannot fetch instead of passing silently (BRIEF §20.2).</summary>
|
|
public sealed class FixturesCommandTests(TestContext context)
|
|
{
|
|
[Test]
|
|
public void TheWarningAnnotationNamesTheFixtureAndEscapesWorkflowCommandCharacters()
|
|
{
|
|
var entry = new FixturesCommand.Entry("canon-eos-r5.cr3", new Uri("https://raw.pixls.us/data/Canon/EOS%20R5/IMG_0001.CR3"), null, null, "Cr3");
|
|
var line = FixturesCommand.Annotation("tests/fixtures/manifest.json", entry, "Response status code 404, 100% missing\r\nretry later.");
|
|
Assert.Equal(
|
|
"::warning file=tests/fixtures/manifest.json,title=RAW fixture missing::canon-eos-r5.cr3 (Cr3) could not be fetched from " +
|
|
"https://raw.pixls.us/data/Canon/EOS%2520R5/IMG_0001.CR3: Response status code 404, 100%25 missing%0D%0Aretry later. " +
|
|
"Its decode tests are skipped. Replace the url in the manifest (see its 'instructions').",
|
|
line);
|
|
Assert.True(FixturesCommand.Annotation("a:b,c.json", entry, "x").StartsWith("::warning file=a%3Ab%2Cc.json,title=", StringComparison.Ordinal));
|
|
}
|
|
|
|
[Test]
|
|
public async Task AMissingFixtureFailsTheCommandUnlessMissingFilesAreAllowed()
|
|
{
|
|
var folder = context.CreateTempDirectory();
|
|
var manifest = Path.Combine(folder, "manifest.json");
|
|
// Port 1 refuses the connection at once (or the proxy answers with an error): the fixture stays missing.
|
|
await File.WriteAllTextAsync(manifest, """
|
|
{ "files": [ { "name": "missing.dng", "url": "https://127.0.0.1:1/missing.dng", "sha256": null, "size": null, "format": "Dng" } ] }
|
|
""");
|
|
var output = Path.Combine(folder, "external");
|
|
|
|
Assert.Equal(1, await new FixturesCommand().RunAsync(["--manifest", manifest, "--out", output]));
|
|
Assert.Equal(0, await new FixturesCommand().RunAsync(["--manifest", manifest, "--out", output, "--allow-missing"]));
|
|
Assert.FileMissing(Path.Combine(output, "missing.dng"));
|
|
}
|
|
}
|