20180731 RNode community testing

Table of contents


Overview

Each week we invite community members to help test RNode.

  • When - Tuesdays at 14:00 UTC
  • Where - This meeting takes place online using Zoom
    • Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/134156866
    • Or iPhone one-tap :
          US: +16468769923,,134156866# or +16699006833,,134156866#
    • Or Telephone:
          Dial(for higher quality, dial a number based on your current location):
              US: +1 646 876 9923 or +1 669 900 6833
          Meeting ID: 134 156 866
          International numbers available: https://zoom.us/u/rDfBtpt
  • Additional communications are posted in #node-testing on the RChaing Discord.


What you can expect this week

We will be testing deploy and propose and the syncing of block counts across the network using the dining philosopher and deadlock example from the Rholang tutorial

Steps for testing

  • Testers will create a network of peers
  • Several testers will deploy this code as a contract and propose a block
  • Testers will report on the number of blocks received
  • We will watch to see if the number of blocks received syncs and becomes common to all peers on the network.


Configure your network

See RNode supported network configuration for information on how to configure your network to connect to other nodes.


Installation packages

Please install RNode prior to the start of the testing session. 

RNode version for this session

We will be working with RNode v0.5.3 from the dev branch of rchain/rchain

Note - At this time RNode does not run successfully in Docker on MacOSX. 

docker pull rchain/rnode:dev

Installation and running instructions

Please see User guide for running RNode for installation and running instructions.


Other requirements

Select a validator key

Bootstrap node address

We are using the dev bootstrap node today. Please use the shown on RNode bootstrap addresses

Share your experience

You best support the improvement and development of the RChain platform when you file a bug to report challenge you faced or unsuccessful outcomes. This will help us collect all relevant information to better understand your setup and experience. 



Testing session summary

We tested block synchronization across the network. Success with this. Assertion errors emerged. Please see bug list below. Highest peer count = 22. Tested killing a node after a propose and restarting and proposing to observe equivocation.


Bugs filed

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

Chat log

Participants

  • Karen Moskowitz
  • Michael Birch
  • Dror Dayan
  • Enzo Zheng
  • Jake
  • Jeremy Busk
  • Jerry
  • Joshy Orndorff
  • Martin Lundfall
  • Mateusz Probachta
  • Lee Carter
  • Scott Thomas
  • Steven Bezzio
  • Tomáš Virtus
  • Will Qiu
  • Anson
  • Alexander
  • xuqzab
  • Paolo DOnorio De Meo
  • Medha Parlikar
  • Chibuike David Asamonye
  • Matthew Kaye
  • Ori Shimony