test: [M3-9508] - Disable Cypress Cloud parallelization action option - #11855
Merged
jdamore-linode merged 1 commit intoMar 14, 2025
Conversation
jdamore-linode
requested review from
carrillo-erik and
hasyed-akamai
and removed request for
a team
March 14, 2025 16:09
bnussman-akamai
approved these changes
Mar 14, 2025
cliu-akamai
approved these changes
Mar 14, 2025
dmcintyr-akamai
approved these changes
Mar 14, 2025
|
Coverage Report: ✅ |
abailly-akamai
pushed a commit
to abailly-akamai/manager
that referenced
this pull request
Mar 17, 2025
abailly-akamai
added a commit
that referenced
this pull request
Mar 18, 2025
* Remove optional canvg dependency * Go the rollup external route * Added changeset: Remedy canvg dependency vulnerability * upcoming: [M3-9495] - Disable APL for LKE-E clusters (#11809) * Show the APL section only for standard cluster tiers * Added changeset: Disable APL for LKE-E clusters on create flow * WIP - poc for what disabled, rather than hidden, section would look like * Update with proposed UX changes * Update test coverage with mocked endpoints, UX changes * Tweak changeset * Update chip text size to small for consistency with other chips * Fix bug preventing 'no' button from being checked * test: [M3-9508] - Fix GHA Cypress pipeline by redirecting env value to file (#11853) * Fix GHA Cypress pipeline by using literal values in matrix * Redirect output to .env file * Set `record` action property to `false` (#11854) * Disable Cypress Cloud parallelization action option (#11855) * change: [M3-9434] - Update styles to CDS for create menu (#11821) * change: [M3-9434] - Theme changes to create menu * update styles to CDS * Update CreateMenu.styles.ts * Added changeset: Update styles to CSD for create menu * Update packages/manager/src/features/TopMenu/CreateMenu/CreateMenu.styles.ts Co-authored-by: Hussain Khalil <122488130+hkhalil-akamai@users.noreply.github.com> * Disabling the custom font-weight eslint rule. --------- Co-authored-by: Hussain Khalil <122488130+hkhalil-akamai@users.noreply.github.com> * fix: [M3-9459] - show details button misalignment for selected stackscript (#11838) * fix: [M3-9459] - show details button misalignment for selected stackscript * Added changeset: show details button misalignment for selected stackscript * Remove StyledRootContainer ans use actionCell prop for alignment * Update changeset description * feedback * cleanup * lock update * Switch to using 3.0.1 --------- Co-authored-by: Mariah Jacobs <114685994+mjac0bs@users.noreply.github.com> Co-authored-by: jdamore-linode <97627410+jdamore-linode@users.noreply.github.com> Co-authored-by: cpathipa <119517080+cpathipa@users.noreply.github.com> Co-authored-by: Hussain Khalil <122488130+hkhalil-akamai@users.noreply.github.com> Co-authored-by: hasyed-akamai <hasyed@akamai.com>
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
4 participants
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 📝
Our GHA pipeline is still failing because we're setting the
paralleloption on the action. Because parallelization is only available via Cypress Cloud, Cypress is failing since we've disabled Cypress Cloud recording.Setting
parallelto false will fix this issue and should finally allow the tests to run 🤞Changes 🔄
parallelCypress GHA optionTarget release date 🗓️
Please specify a release date (and environment, if applicable) to guarantee timely review of this PR. If exact date is not known, please approximate and update it as needed.
Preview 📷
Include a screenshot or screen recording of the change.
🔒 Use the Mask Sensitive Data setting for security.
💡 Use
<video src="" />tag when including recordings in table.How to test 🧪
Prerequisites
(How to setup test environment)
Reproduction steps
(How to reproduce the issue, if applicable)
Verification steps
(How to verify changes)
Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support
As an Author, before moving this PR from Draft to Open, I confirmed ✅
Commit message and pull request title format standards
<commit type>: [JIRA-ticket-number] - <description>Commit Types:
feat: New feature for the user (not a part of the code, or ci, ...).fix: Bugfix for the user (not a fix to build something, ...).change: Modifying an existing visual UI instance. Such as a component or a feature.refactor: Restructuring existing code without changing its external behavior or visual UI. Typically to improve readability, maintainability, and performance.test: New tests or changes to existing tests. Does not change the production code.upcoming: A new feature that is in progress, not visible to users yet, and usually behind a feature flag.Example:
feat: [M3-1234] - Allow user to view their login history