-
Notifications
You must be signed in to change notification settings - Fork 671
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
[testing] Add scheduled jobs to test bootstrap from mainnet and testnet #3172
Conversation
757eaa6
to
592daa7
Compare
ca36d5f
to
2144e36
Compare
2b74717
to
260ab20
Compare
}) | ||
|
||
// Create a new single-node network that will bootstrap from the specified network | ||
network := &tmpnet.Network{ |
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.
Use of tmpnet to start the nodes is primarily to take advantage of its configuration of metrics and log collection in CI. If reviewers feel strongly it should be possible to extract the monitoring configuration for reuse instead.
3cdd0ae
to
89a5670
Compare
4928b06
to
5a46786
Compare
5e9a28b
to
b245d28
Compare
585a15c
to
f79f576
Compare
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.
lgtm once the conflict and lint issue is solved. Left a couple of optional suggestions
f79f576
to
fdcf4ae
Compare
Moving to draft, am actively working on this. |
This supports building an image on a mac that will work in an amd64 eks cluster.
fdcf4ae
to
53230b7
Compare
Why this should be merged
Periodic bootstrap testing is intended to insure that bootstrapping issues are detected prior to releasing to testnet and mainnet.
How this works
How this was tested