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

Disabling the Moonpay/Bitcoin.com widget [1.17] #7147

Merged
merged 1 commit into from
Nov 18, 2020
Merged

Conversation

ryanml
Copy link
Contributor

@ryanml ryanml commented Nov 14, 2020

Fixes: brave/brave-browser#12699
Uplifts: #7145

Approved, please ensure that before merging:

  • You have checked CI and the builds, lint, and tests all pass or are not related to your PR.
  • You have tested your change on Nightly.
  • The PR milestones match the branch they are landing to.

After you merge:

  • The associated issue milestone is set to the smallest version that the changes is landed on.

@ryanml ryanml added this to the 1.17.x - Release milestone Nov 14, 2020
@ryanml ryanml requested a review from a team November 14, 2020 23:40
@ryanml ryanml self-assigned this Nov 14, 2020
Disabling the Moonpay/Bitcoin.com widget
@kjozwiak
Copy link
Member

Going to restart macOS, Linux & Win x64 as test-browser keeps failing a lot of tests. Usually we have ~1-2 intermittent failures but there appears to be a lot more than usual.

@kjozwiak
Copy link
Member

Restarting Win x64 as it appears like CI had issues with the instance as per https://ci.brave.com/job/pr-brave-browser-remove-bdc-1.17-windows/4/execution/node/200/log/.

16:08:13  Cannot contact i-0e690ad4f29a2abe0-windows-swarm-427e4294: hudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException
16:13:13  Could not connect to i-0e690ad4f29a2abe0-windows-swarm-427e4294 to send interrupt signal to process

test-browser failed on macOS due to BraveContentBrowserClientTest.RewriteChromeSync crashing as per https://ci.brave.com/job/pr-brave-browser-remove-bdc-1.17-macos/3/execution/node/251/log/.

05:05:15  1 test crashed:
05:05:15      BraveContentBrowserClientTest.RewriteChromeSync (../../brave/browser/brave_content_browser_client_browsertest.cc:215)

Created brave/brave-browser#12753 for the BraveContentBrowserClientTest.RewriteChromeSync issue but the rest appear to be rewards related which isn't related to this PR.

@kjozwiak
Copy link
Member

test-browser failed on Win x64 due to BraveContentBrowserClientTest.RewriteChromeSync failing as per https://ci.brave.com/job/pr-brave-browser-remove-bdc-1.17-windows/5/execution/node/247/log/.

20:28:19  1 test crashed:
20:28:19      BraveContentBrowserClientTest.RewriteChromeSync (../../brave/browser/brave_content_browser_client_browsertest.cc:215)

test-browser failed on Linux due to both BraveContentBrowserClientTest.RewriteChromeSync & BraveSchemeLoadBrowserTest.SettingsPageIsNotAllowedInPrivateWindow crashing as per https://ci.brave.com/job/pr-brave-browser-remove-bdc-1.17-linux/7/execution/node/251/log/.

18:41:05  2 tests crashed:
18:41:05      BraveContentBrowserClientTest.RewriteChromeSync (../../brave/browser/brave_content_browser_client_browsertest.cc:215)
18:41:05      BraveSchemeLoadBrowserTest.SettingsPageIsNotAllowedInPrivateWindow (../../brave/browser/brave_scheme_load_browsertest.cc:225)

Created brave/brave-browser#12753 for the BraveContentBrowserClientTest.RewriteChromeSync issue but the rest appear to be rewards related which isn't related to this PR.

Copy link
Member

@kjozwiak kjozwiak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uplift into 1.17.x approved after deliberating with @brave/uplift-approvers. QA has verified the PR on Nightly via #7145 (comment).

@kjozwiak kjozwiak merged commit 5fc21da into 1.17.x Nov 18, 2020
@kjozwiak kjozwiak deleted the remove-bdc-1.17 branch November 18, 2020 04:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants