You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Found the word "TODO" in the PR description. Just letting you know incase you forgot :)
Messages
📖
DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next pr-test build run (assuming they are fixed).
📖
Access a deployed version of this PR here. Make sure to wait for the "pwa-pull-request-deploy" job to complete.
Log
ERROR ON TASK: prettierCheck
ERROR ON TASK: scaffoldingSucceeds
Error: Danger had errors running. See message(s) above for more details.
danger-results://tmp/danger-results.json
If your PR is missing information, check against the original template here. At a minimum you must have the section headers from the template and provide some information in each section.
The response we received from your web server was:
504: Gateway Timeout
This was considered a failure because the status code was not 2xx.
If you do not want status codes to cause failures pass the option: failOnStatusCode: false
Verify venia anchor links:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetProductDetailForProductPageQuery. No request ever occurred.
user should be able to add and update gift options:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetProductDetailForProductPageQuery. No request ever occurred.
user should be able to access the Categories via Home page and from Main Menu left drawer:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetCMSPageQuery. No request ever occurred.
CypressError: Timed out retrying after 20000ms: cy.wait() timed out waiting 20000ms for the 1st request to the route: resourceClientJs. No request ever occurred.
The response we received from your web server was:
504: Gateway Timeout
This was considered a failure because the status code was not 2xx.
If you do not want status codes to cause failures pass the option: failOnStatusCode: false
user should be able to place an order as a registered customer:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetProductDetailForProductPageQuery. No request ever occurred.
Registered user should be able to sign in from toast suggestion in guest checkout page:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetProductDetailForProductPageQuery. No request ever occurred.
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetProductDetailForProductPageQuery. No request ever occurred.
The response we received from your web server was:
504: Gateway Timeout
This was considered a failure because the status code was not 2xx.
If you do not want status codes to cause failures pass the option: failOnStatusCode: false
User shouldn't be able to add a CustomizableProduct from category page:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetCategoriesQuery. No request ever occurred.
The response we received from your web server was:
504: Gateway Timeout
This was considered a failure because the status code was not 2xx.
If you do not want status codes to cause failures pass the option: failOnStatusCode: false
user can fill and submit form with default badge position:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetReCaptchaV3ConfigDefaultQuery. No request ever occurred.
user can fill and submit form with inline badge position:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetReCaptchaV3ConfigInlineQuery. No request ever occurred.
The response we received from your web server was:
504: Gateway Timeout
This was considered a failure because the status code was not 2xx.
If you do not want status codes to cause failures pass the option: failOnStatusCode: false
Validate validations:
AssertionError: Timed out retrying after 30000ms: Expected to find element: [data-cy="Newsletter-root"] input[name="email"], but never found it.
user should be able to remove products:
CypressError: Timed out retrying after 60000ms: cy.wait() timed out waiting 60000ms for the 1st request to the route: gqlGetProductDetailForProductPageQuery. No request ever occurred.
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
TODO: Describe your changes in detail here.
Related Issue
Closes #ISSUE_NUMBER.
Acceptance
Verification Stakeholders
Specification
Verification Steps
Test scenario(s) for direct fix/feature
Test scenario(s) for any existing impacted features/areas
Test scenario(s) for any Magento Backend Supported Configurations
Is Browser/Device testing needed?
Any ad-hoc/edge case scenarios that need to be considered?
Screenshots / Screen Captures (if appropriate)
Breaking Changes (if any)
Checklist