Page Comparison

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:

I can't see my cursor/text after I exit using CTRL-C from REPL

1GB Ubuntu VM

2GB Debian VM

4GB Fedora VM

Ubuntu LTS baremetal 32GB

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

(DEB, Binary Tarball)

Results (Binary Tarball):

•  

  Started node manually

•  Tested REPL
•  Tested EVAL
•  Tested Deploy Demo

Results (DEB):

•  Installed cleanly
•  

  Started systemd service succesfully

•  Tested REPL
•  Tested EVAL
•  Tested Deploy Demo

Fedora Laptop (8 GB RAM, 4 CPU)

(RPM, Binary Tarball)

Results (Binary Tarball):

•  

  Started node manually

•  Tested REPL
•  Tested EVAL
•  Tested Deploy Demo

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

Eval works "as advertised" but it is really counterintuitive to have to provide the absolute path to a file on the server, rather than client.

Jeremy and I evaluated every file in the top-level of /usr/share/rnode/examples in networked mode and all is good

Test docker

1 CPU, 1 GB RAM

Results (Docker)

•  Installed cleanly
•  REPL in Connected Mode
•  EVAL in connected Mode
•  Deploy Demo
•  Tutorial - first 2 examples
•  EVAL, Deploy-Demo running together
•   

Comments:

If the path is wrong in eval mode, exception is not returned to user.  Exception appears on server side.  Need to file a ticket.

Casper issue, at some point the same block is passed around (observed at block 8)

Starting standalone mode after having been in connected mode results in: 

17:35:55.795 [main] INFO  logger - Starting stand-alone node.

17:36:04.044 [repl-io-26] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352})

17:36:04.061 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352})

17:36:10.500 [repl-io-26] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5})

17:36:10.506 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5})

17:36:10.512 [repl-io-26] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352})

17:36:10.517 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5})

17:36:10.520 [repl-io-26] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352})

17:36:44.116 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352})

17:36:44.127 [repl-io-27] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 0f365f1016a54747b384b386b8e85352})

17:36:50.709 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5})

17:36:50.715 [repl-io-27] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5})

17:36:50.725 [repl-io-24] ERROR logger - error while handling frame message: PeerNodeNotFound(#{PeerNode 08ecdc398b4040ebb51a87e441097ac5})

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

assembly jar

docker

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

test docker

with dev