Versions Compared

Old Version 7

changes.mady.by.user Henry Till

Saved on

compared with

New Version 8

changes.mady.by.user Mateusz Gorski (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Testing debian version of rnode 0.3.1 on Ubuntu 16.04 LTS

...

  •  Installation completes without issues
  •  Ctrl-C terminates the program without throwing an exception
  •  Program starts without exceptions (providing that the directories needed exist on the system)
  •  In the event that the bootstrap node cannot be found, system provides a message an ends normally.


Code Block
languagebash
titleDebian Instructions
git clone https://github.com/rchain/rchain.git
cd rchain
git checkout dev
sbt clean bnfc:generate node/debian:packageBin
sudo apt install ./node/target/
sudo apt install ./node/target/rnode_0.3.1_all.deb
sudo systemctl start rnode.service
# in one terminal
sudo journalctl -f -u rnode.service
# in another terminal (for repl testing)
rnode --repl
# after that (for deploy testing)
rnode --deploy-demo

...

https://gist.github.com/henrytill/ac72d8616e52d836efc3008bbd9f67dd


Run this at the REPL as many times as humanly possible:

...

Who?

What 

Test the tasks described above in your assigned environment below.




Jeremy

Ubuntu 16.04 LTS

Results (DEB):

  •  Installed cleanly
  •  

    Started systemd service succesfully

  •  Tested REPL
  •  Tested EVAL
  •  
  •  
  •  Tested Deploy Demo

Comments:

Fedora 27 VM 

Results (RPM):

  •  Installed cleanly
  •  

    Started systemd service succesfully

  •  Tested REPL
  •  Tested EVAL
  •  
  •  
  •  Tested Deploy Demo

Comments:

Debian Stable VM

Results (DEB):

  •  Installed cleanly
  •  

    Started systemd service succesfully

  •  Tested REPL
  •  Tested EVAL
  •  
  •  
  •  Tested Deploy Demo

Comments:


Henry

Debian Stable VM (1 GB RAM, 1 CPU):

(DB, Binary Tarball


Results (DEB):

  •  Installed cleanly
  •  

    Started systemd service succesfully

  •  Tested REPL
  •  Tested EVAL
  •  
  •  Tested Deploy Demo

Comments:



Results (Binary Tarball):

  •  Installed cleanly
  •  

    Started systemd service succesfully

  •  Tested REPL
  •  Tested Deploy Demo


Fedora Laptop (8 GB RAM, 4 CPU)

(RPM, Binary Tarball)


Results (RPM):

  •  Installed cleanly
  •  

    Started systemd service succesfully

  •  Tested REPL
  •  Tested EVAL
  •  Tested Deploy Demo

Comments:

Still seeing NPE when I exit REPL with CTRL-C

https://rchain.atlassian.net/browse/CORE-485

Results (Binary Tarball):

  •  Installed cleanly
  •  

    Started systemd service succesfully

  •  Tested REPL
  •  Tested Deploy Demo




Medha

Test docker

1 CPU, 1 GB RAM




Mateusz

Ubuntu 16.04 (8 CPU 32GB RAM)

  •  Installation completes without issues
  •  Ctrl-C terminates the program without throwing an exception
  •  Program starts without exceptions (providing that the directories needed exist on the system)
  •  Started systemd service succesfully
  •  Started in standalone mode
  •  Tested REPL
  •  Tested EVAL
  •  Tested STDOUT
  •  Check Promethus server
  •  Check that all metrics in the release appear
  •  Server accepts requests and returns responses
  •  List of peers is accurate & matches what is presented on the server console.
    •  Response from peers reflects peers currently connected and changes as the peer list changes
  •   Deploy-demo call works (--deploy-demo)

Comments:

Still seeing NPE when I exit REPL with CTRL-C




Michael Birchtest locally with dev

assembly jar

docker

Result: Both work fine (modulo NPE on exit of repl via ^D)



Sebastiantest locally with dev

test docker

with dev



...