Fix: failing jenkins load test jobjob#239
Open
mutambaraf wants to merge 7 commits into
Open
Conversation
ACLay
reviewed
Jun 3, 2026
deepaksftc
approved these changes
Jun 10, 2026
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.
Description
Fixed a failing Jenkins job caused by GraphQL schema mismatches (shortCode on Status type) that were crashing teardown and marking k6 pods as failed despite proposals submitting successfully. Hardened run-cluster.sh with set -euo pipefail, trap-based cleanup, and fixed argument parsing. Updated the webpack build to only bundle the test being run and wired graphql-codegen into lint-staged for automatic type regeneration.
Motivation and Context
The deleteProposal and createProposal mutations were sending a field (shortCode) that no longer exists on the Status type in the live schema, causing an uncaught promise rejection in teardown that k6 treated as a fatal error. The shell script had several silent failure modes (no set -e, negative timeout, broken URL argument parser) that masked errors in CI.
How Has This Been Tested
Fixes
Changes
Depends on
Tests included/Docs Updated?