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

chore: update to cucumber test to use sydney seed monero url address #3167

Merged
merged 2 commits into from
Aug 6, 2021

Conversation

SWvheerden
Copy link
Collaborator

Description

Changed the monero URL address used by the cucumber test from: http://monero-stagenet.exan.tech:38081 to http://3.104.4.129:18081/

Motivation and Context

How Has This Been Tested?

Checklist:

  • I'm merging against the development branch.
  • I have squashed my commits into a single commit.

stringhandler
stringhandler previously approved these changes Aug 6, 2021
@stringhandler stringhandler changed the title fix: Update to cucumber test to use Sydney seed monero url address chore: update to cucumber test to use sydney seed monero url address Aug 6, 2021
@aviator-app
Copy link
Contributor

aviator-app bot commented Aug 6, 2021

PR queued successfully. Your position in queue is: 2

@aviator-app
Copy link
Contributor

aviator-app bot commented Aug 6, 2021

PR is on top of the queue now

@aviator-app aviator-app bot added the mq-failed label Aug 6, 2021
@aviator-app
Copy link
Contributor

aviator-app bot commented Aug 6, 2021

PR failed to merge with reason: Some CI status(es) failed
Failed CI(s): ci/circleci: run-integration-tests

@aviator-app
Copy link
Contributor

aviator-app bot commented Aug 6, 2021

PR queued successfully. Your position in queue is: 1

@aviator-app aviator-app bot merged commit 4e70d91 into tari-project:development Aug 6, 2021
@SWvheerden SWvheerden deleted the sw_proxy_address branch August 12, 2021 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants