-
Notifications
You must be signed in to change notification settings - Fork 158
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
Feat/audit bootnodes ci #324
Conversation
Date: 2021-03-01 14:37:11-06:00 Signed-off-by: meows <[email protected]>
Date: 2021-03-01 14:44:50-06:00 Signed-off-by: meows <[email protected]>
Date: 2021-03-01 14:51:13-06:00 Signed-off-by: meows <[email protected]>
Date: 2021-03-01 14:55:00-06:00 Signed-off-by: meows <[email protected]>
Date: 2021-03-01 15:07:31-06:00 Signed-off-by: meows <[email protected]>
Date: 2021-03-01 15:09:33-06:00 Signed-off-by: meows <[email protected]>
Date: 2021-03-01 15:16:53-06:00 Signed-off-by: meows <[email protected]>
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, nice use of GitHub actions to check the bootnodes. I run it and it seems we have a lot of failing bootnodes at the moment. Will we clean them in a separate PR?
enode_list="$(cat "$1" |grep -E 'enode://' | sed 's-"--g' | sed 's-\t--g'| sed 's/,.*//g')" | ||
echo "$enode_list" | while read -r line; do | ||
if >/dev/null 2>&1 ./build/bin/devp2p discv4 ping "${line}"; then | ||
>&2 echo "PASS: ${line}" |
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.
Woow, nice use of redirection. I am not good at bash and I am learning new stuff by checking your code @meowsbits :)
Yea, that's what I was thinking. |
Rel #321
Installs a Github Actions CI Workflow that audits the bootnodes listed as chain configuration defaults (for all chains).
It uses
./build/bin/devp2p discv4 ping
, pinging each enode. Nodes that respond pass, nodes that fail to respond... well, they fail. You had one job....The workflow is configured to run
params/bootnodes*go
workflow_dispatch
)For
schedule
(cron) andworkflow_dispatch
triggers, the workflow will remove failing enodes and create a pull request with that change set.For
pull_request
triggers, the action will not create a PR; it will just just fail and the light will turn red ❌.As for the actual outcome of auditing the bootnodes, a complementary PR is here: meowsbits#15.