Skip to content

fix(tests): pin production HETA to 2.1.1 - #775

Merged
olivermeyer merged 1 commit into
mainfrom
fix/heta-production-version
Nov 11, 2026
Merged

olivermeyer merged 1 commit into
mainfrom
fix/heta-production-version

Conversation

@akunft

@akunft akunft commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator

Why

Production now offers he-tme 2.1.1 (released 2026-11-09). For 2.1.0 it lists nothing, and GET returns 403 Forbidden. Since then, the scheduled production workflows fail every run. For example, Production Daily and Production Hourly fail these tests:

  • application/cli_test.py::test_cli_application_list_verbose: assert '2.1.0' in .... The listing shows only 2.1.1.
  • application/cli_test.py::test_cli_application_dump_schemata: Failed to retrieve application with ID 'he-tme': (403)
  • application/gui_test.py::test_gui_cli_submit_to_run_result_delete: the same 403.

What

tests/constants_test.py: change production HETA_APPLICATION_VERSION from 2.1.0 to 2.1.1. Staging still offers 2.1.0, and its scheduled runs are green, so its pin stays.

Verification

PR CI runs against staging only, so it can't exercise this change. To prove it, I dispatched the production scheduled workflows on this branch:

  • Scheduled Testing / Production (Hourly) on this branch: green (1 failed, 4 passed before, 5 passed, 4 skipped after)
  • Scheduled Testing / Production (Daily) on this branch: green. The 3 failing tests now pass. test_platform_artifact_file_endpoint_resolves_to_working_url now skips (no 2.1.1 runs yet, see Known gaps)

Before this change, the same workflows failed on main for the reason above. That is the "red" half of the proof.

Known gaps (not changed here)

  • Production has no 2.1.1 runs tagged scheduled yet, because the submit tests are skipped (GCS_TEST_SLIDES_REMOVED_REASON). So these run-lookup tests skip on production for now: test_platform_artifact_file_endpoint_resolves_to_working_url and the gui_test pagination tests.
  • _find_and_validate in platform/e2e_test.py loops over the runs it finds and passes when it finds none, so test_platform_heta_app_find_and_validate can't fail without runs. That was already true before this change.
  • Staging will break the same way once it drops 2.1.0.

Production now offers he-tme 2.1.1 (released 2026-11-09) and returns 403 for
2.1.0. The scheduled production tests fail since then:
test_cli_application_list_verbose, test_cli_application_dump_schemata and
test_gui_cli_submit_to_run_result_delete.

Staging still offers 2.1.0, so its pin stays.
@akunft
akunft requested a review from a team as a code owner November 11, 2026 14:28
@akunft akunft added the skip:test:long_running Skip long-running tests (≥5min) label Nov 11, 2026
@ox-security

ox-security Bot commented Nov 11, 2026

Copy link
Copy Markdown

OX Security Logo

OX Security reviewed this pull request — nothing to fix.

✔ No issues found

Branch fix/heta-production-version → main

View scan in OX Security →

@codecov

codecov Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.
see 1 file with indirect coverage changes

@olivermeyer
olivermeyer enabled auto-merge (rebase) November 11, 2026 17:17
@sonarqubecloud

Copy link
Copy Markdown

@olivermeyer
olivermeyer merged commit 6859390 into main Nov 11, 2026
62 of 83 checks passed
@olivermeyer
olivermeyer deleted the fix/heta-production-version branch November 11, 2026 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip:test:long_running Skip long-running tests (≥5min)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants