Repository navigation
fix(tests): pin production HETA to 2.1.1 - #775
Merged
Merged
Conversation
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.
|
OX Security reviewed this pull request — nothing to fix.
Branch |
Codecov Report✅ All modified and coverable lines are covered by tests. |
olivermeyer
approved these changes
Nov 11, 2026
olivermeyer
enabled auto-merge (rebase)
November 11, 2026 17:17
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Why
Production now offers
he-tme2.1.1(released 2026-11-09). For2.1.0it lists nothing, andGETreturns403 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 only2.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 productionHETA_APPLICATION_VERSIONfrom2.1.0to2.1.1. Staging still offers2.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:
1 failed, 4 passedbefore,5 passed, 4 skippedafter)test_platform_artifact_file_endpoint_resolves_to_working_urlnow skips (no2.1.1runs yet, see Known gaps)Before this change, the same workflows failed on
mainfor the reason above. That is the "red" half of the proof.Known gaps (not changed here)
2.1.1runs taggedscheduledyet, 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_urland thegui_testpagination tests._find_and_validateinplatform/e2e_test.pyloops over the runs it finds and passes when it finds none, sotest_platform_heta_app_find_and_validatecan't fail without runs. That was already true before this change.2.1.0.