Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tmp: investigate notification e2e smoke issue #11370

Closed
wants to merge 1 commit into from

Conversation

Prithpal-Sooriya
Copy link
Contributor

@Prithpal-Sooriya Prithpal-Sooriya commented Sep 23, 2024

Description

This is not to be merged.

Investigated the issues we have with upgrading some controllers:

  • @metamask/notification-services-controller
  • @metamask/profile-sync-controller

Here are some breakdown notes:

e2e compilation issues
This was resolved in: MetaMask/core#4721
It seems there was an issue with compiling exported async arrow functions with hermes. This has now been resolved.

e2e failing
Now it seems that e2e tests are outright failing, which is odd. To keep scope minimal, we are only upgrading the packages in this PR.

Related issues

Fixes:

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

Before

After

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

@Prithpal-Sooriya Prithpal-Sooriya added the DO-NOT-MERGE Pull requests that should not be merged label Sep 23, 2024
Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@github-actions github-actions bot added the team-notifications Notifications team label Sep 23, 2024
@Prithpal-Sooriya Prithpal-Sooriya changed the title investigate notification e2e smoke issue tmp: investigate notification e2e smoke issue Sep 23, 2024
@Prithpal-Sooriya Prithpal-Sooriya added the Run Smoke E2E Triggers smoke e2e on Bitrise label Sep 23, 2024
Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@metamask/[email protected] network 0 1.21 MB metamaskbot
npm/@metamask/[email protected] network 0 1.01 MB metamaskbot
npm/[email protected] None 0 29.6 kB sindresorhus

🚮 Removed packages: npm/@metamask/[email protected], npm/@metamask/[email protected], npm/[email protected]

View full report↗︎

Copy link
Contributor

github-actions bot commented Sep 23, 2024

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 9e9061c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/09966e05-1048-4d15-b08e-ae0f37855a42

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

  • Check the documentation if you have any doubts on how to understand the failure on bitrise

Copy link

sonarcloud bot commented Sep 23, 2024

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
DO-NOT-MERGE Pull requests that should not be merged Run Smoke E2E Triggers smoke e2e on Bitrise team-notifications Notifications team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant