-
Notifications
You must be signed in to change notification settings - Fork 248
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
Change test setup to use account helper if available #285
Conversation
The CI is getting:
|
5326508
to
5e384d3
Compare
CI is failing because:
|
5e384d3
to
ed354a2
Compare
4e63ef9
to
4bc79bf
Compare
4bc79bf
to
c4584da
Compare
0108672
to
55c7ea6
Compare
55c7ea6
to
f13356d
Compare
@@ -3,6 +3,8 @@ node_js: 10 | |||
env: | |||
- NODE_ENV=ci | |||
- NODE_ENV=ci-betanet | |||
# - NODE_ENV=devnet | |||
- NODE_ENV=betanet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure whether this is a good idea. If betanet is down, near-api-js development would be blocked.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree with Bowen here, I think it's too early have to have CI check betanet. In time, perhaps
No description provided.