chore: capture BUILDKITE_RETRY_COUNT #25750
Merged
Conversation
This file contains 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
29 flaky tests on run #44880 ↗︎
Details:
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Test | Artifacts | |
|---|---|---|
| ... > runs generated spec |
Output
Screenshots
Video
|
|
| ... > runs generated spec |
Output
Screenshots
Video
|
|
specs_list_latest_runs.cy.ts • 1 flaky test • app-e2e
| Test | Artifacts | |
|---|---|---|
| App/Cloud Integration - Latest runs and Average duration > when no runs are recorded > shows placeholders for all visible specs |
Output
Screenshots
Video
|
|
settings.cy.ts • 1 flaky test • app-e2e
| Test | Artifacts | |
|---|---|---|
| App: Settings without cloud > the projectId section shows a prompt to log in when there is no projectId, and uses correct UTM params |
Output
Screenshots
Video
|
|
cypress-origin-communicator.cy.ts • 1 flaky test • app-e2e
| Test | Artifacts | |
|---|---|---|
| Cypress In Cypress Origin Communicator > cy.origin passivity with app interactions > passes upon test reload mid test execution |
Output
Screenshots
Video
|
|
global-mode.cy.ts • 1 flaky test • launchpad-e2e
| Test | Artifacts | |
|---|---|---|
| ... > can be opened |
Output
Screenshots
Video
|
|
The first 5 flaky specs are shown, see all 17 specs in Cypress Cloud.
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.
emilyrohrbough
changed the title
|
@estrada9166 Can you please update this PR summary to indicate why this env is needed and how it impacts the Cloud data? |
Co-authored-by: Emily Rohrbough <emilyrohrbough@users.noreply.github.com>
…o/feat/capture-build-retry-buildkite
lmiller1990
approved these changes
Mar 21, 2023
lmiller1990
changed the title
lmiller1990
changed the title
|
Looks good 👍 🪁 |
|
@lmiller1990 This needed two approvals before merging. Also this didn't have a corresponding documentation updates.... |
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.
Additional details
Capture Buildkite env variable BUILDKITE_RETRY_COUNT - used to handle ci retries
This env variable shows how many times this job has been retried - providing a value that would ensure that ci-build-id created (if it's not custom) is unique, making every retry a new run and avoiding having a passed run where the specs have been completed in the previous run (creating a false positive)
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation?type definitions?