Skip to content

Update Semaphore test matrix to v2.19.12 - #7

Merged
fiftin merged 13 commits into
mainfrom
codex/semaphore-v2.19.12
Sep 4, 2026
Merged

Update Semaphore test matrix to v2.19.12#7
fiftin merged 13 commits into
mainfrom
codex/semaphore-v2.19.12

Conversation

@dantro86

@dantro86 dantro86 commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • move all release server and runner profiles from Semaphore v2.19.8 to v2.19.12
  • update the recorded release source commit to 012ed06d
  • change SQLite and PostgreSQL upgrade coverage to v2.19.8 → v2.19.12
  • keep historical v2.19.8 defect evidence intact while reclassifying v2.19.12 behavior
  • isolate the strict short stdout/stderr check in a manual feature-shell-output defect profile
  • run profile test classes sequentially while stable v2.19.12 has a concurrent output-collector race; the dedicated scenario still verifies real parallel task execution inside Semaphore

Validation

  • local Gradle qualityGate: passed
  • final PR gate: passed framework checks, SQLite API/UI baseline and Allure build
  • configuration matrix: all 11 profiles passed, including PostgreSQL, MySQL, MariaDB, persistent runner, SSH, HTTPS Git, OIDC, proxy OIDC, LDAPS, TOTP and encryption rotation; Allure built successfully
  • release upgrade: SQLite and PostgreSQL v2.19.8 → v2.19.12 passed; Allure built successfully

Stable-release defect found during validation

Short successful tasks can lose arbitrary stdout/stderr fragments in the persisted output on
v2.19.12. Initial concurrent matrix runs reproduced the same loss in otherwise successful Ansible
tasks across multiple databases and feature profiles. Retrying the output endpoint and adding a
final playbook delay did not recover the missing fragments, so this is not treated as eventual
consistency or hidden by retries.

The strict reproducer remains available through the manual feature-shell-output profile and the
include_shell_output_investigation workflow input. Stable profile classes run sequentially to
avoid amplifying the server-side collector race; ProjectConcurrencyApiTest still launches real
concurrent Semaphore tasks. The workaround and removal criteria are documented in
test-environment/shell-output-loss-defect.md.

Upstream fixes already present after v2.19.12:

@fiftin
fiftin merged commit 0b1db64 into main Sep 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants