Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / ethereum/system-testing issues and pull requests

#62 - Update kibana to a recent snapshot

Pull Request - State: closed - Opened by konradkonrad about 9 years ago

#61 - update go cli params according to new spec [DO NOT MERGE YET]

Pull Request - State: closed - Opened by zelig over 9 years ago

#60 - Update elasticsearch to 1.4.4

Pull Request - State: closed - Opened by konradkonrad over 9 years ago

#59 - Adding new go client structlog argument

Pull Request - State: closed - Opened by LefterisJP over 9 years ago
Labels: looksgood

#58 - Structured Logging Error Event for mining

Issue - State: closed - Opened by LefterisJP over 9 years ago - 1 comment

#57 - Tweak for tests to work on an Archlinux Venv

Pull Request - State: closed - Opened by LefterisJP over 9 years ago

#56 - RPC method updating

Pull Request - State: closed - Opened by LefterisJP over 9 years ago

#55 - Pytest integration

Pull Request - State: closed - Opened by jnnk over 9 years ago - 1 comment

#54 - go client: implement all defined log events

Issue - State: closed - Opened by heikoheiko over 9 years ago - 4 comments
Labels: prio1

#53 - map rpc server to external port

Issue - State: closed - Opened by heikoheiko over 9 years ago - 1 comment
Labels: prio1

#52 - test transaction propagation

Issue - State: open - Opened by heikoheiko over 9 years ago - 5 comments
Labels: test scenario, in progress, prio1

#51 - Enable client start stop scenario for go

Issue - State: closed - Opened by sveneh over 9 years ago - 2 comments
Labels: ready, prio1

#50 - test that the go clients connect to each other

Issue - State: closed - Opened by sveneh over 9 years ago - 2 comments
Labels: test scenario, prio1

#49 - Define logging spec for base scenario

Issue - State: closed - Opened by sveneh over 9 years ago

#48 - test that the python client connect to each other

Issue - State: closed - Opened by sveneh over 9 years ago - 1 comment
Labels: enhancement, test scenario

#46 - Scale one scenario to 200 instances

Issue - State: closed - Opened by sveneh over 9 years ago - 1 comment

#45 - increase ansible operation speed

Issue - State: closed - Opened by sveneh over 9 years ago

#44 - test network split and network separation

Issue - State: closed - Opened by sveneh over 9 years ago - 1 comment
Labels: question, test scenario, prio1

#41 - Add kibana4 container and custom elasticsearch

Pull Request - State: closed - Opened by konradkonrad over 9 years ago

#40 - client numbered naming

Issue - State: closed - Opened by heikoheiko over 9 years ago - 2 comments

#39 - individual clients can be started for mining, and stopped

Issue - State: closed - Opened by sveneh over 9 years ago - 1 comment

#38 - test that multiple different clients can connect to each other with the new PoC-8 network protocol

Issue - State: open - Opened by sveneh over 9 years ago - 2 comments
Labels: test scenario, prio1

#37 - client nodes can be identified by an id for later reference

Issue - State: closed - Opened by sveneh over 9 years ago - 1 comment

#35 - Have consistent name (ip, dns) for elastic search node

Issue - State: open - Opened by sveneh over 9 years ago - 1 comment
Labels: enhancement

#34 - Find a better way to address AWS nodes from separate playbooks

Issue - State: closed - Opened by sveneh over 9 years ago - 1 comment
Labels: enhancement

#33 - check that AWS instances are instanciated correctly before installing software

Issue - State: closed - Opened by sveneh over 9 years ago
Labels: enhancement

#32 - upgrade clients to poc-8 develop version

Issue - State: closed - Opened by sveneh over 9 years ago

#31 - Automate docker file creation

Issue - State: closed - Opened by sveneh over 9 years ago - 2 comments
Labels: enhancement

#30 - also add go-ethereum into test network

Issue - State: closed - Opened by sveneh over 9 years ago - 7 comments

#29 - elastic search + kibana server is deployed in test network

Issue - State: closed - Opened by sveneh over 9 years ago

#28 - pyethereum in docker can be deployed into test network

Issue - State: closed - Opened by sveneh over 9 years ago

#27 - AWS nodes can be instantiated and destroyed with Ansible

Issue - State: closed - Opened by sveneh over 9 years ago

#26 - Secure stress testnet from outside access

Issue - State: open - Opened by sveneh over 9 years ago

#25 - Do we need an integration of the stress testbed with any other testnet?

Issue - State: closed - Opened by sveneh over 9 years ago - 1 comment
Labels: question

#24 - test random contract execution scenario

Issue - State: open - Opened by sveneh over 9 years ago - 2 comments
Labels: test scenario

#23 - elastic search server has persistent storage

Issue - State: open - Opened by sveneh over 9 years ago

#22 - integrate docker log with log forwarder

Issue - State: closed - Opened by sveneh over 9 years ago

#21 - other people can play with system testing, not just me

Issue - State: closed - Opened by sveneh over 9 years ago - 4 comments

#20 - test general mining scenario

Issue - State: open - Opened by sveneh over 9 years ago - 4 comments
Labels: test scenario, in progress, prio1

#19 - automate config file deploy to node clients

Issue - State: closed - Opened by sveneh over 9 years ago - 1 comment

#18 - also add cpp-ethereum into test network

Issue - State: closed - Opened by sveneh over 9 years ago - 2 comments
Labels: prio1

#17 - deploy a bootstrap node in test network

Issue - State: closed - Opened by sveneh over 9 years ago - 1 comment

#16 - enable logging from node client to master elastic search server

Issue - State: closed - Opened by sveneh over 9 years ago
Labels: help wanted

#15 - automated delivery of logging tools to node clients

Issue - State: closed - Opened by sveneh over 9 years ago

#14 - test blocktime variantions between 0 and unlimited

Issue - State: open - Opened by sveneh over 9 years ago
Labels: test scenario

#13 - test gas price variation

Issue - State: open - Opened by sveneh over 9 years ago
Labels: test scenario

#12 - test sibil attacks

Issue - State: open - Opened by sveneh over 9 years ago - 1 comment
Labels: question, test scenario

#11 - test injections of invalid blocks

Issue - State: open - Opened by sveneh over 9 years ago
Labels: test scenario

#10 - test different order of transactions

Issue - State: open - Opened by sveneh over 9 years ago
Labels: test scenario, prio2

#9 - test resiliency wrt share of malicious nodes

Issue - State: open - Opened by sveneh over 9 years ago
Labels: test scenario

#8 - test spamming, ddos,

Issue - State: open - Opened by sveneh over 9 years ago
Labels: test scenario, prio2

#7 - test intentional takeover, double spending

Issue - State: open - Opened by sveneh over 9 years ago
Labels: test scenario

#6 - test different clients with clock skew

Issue - State: open - Opened by sveneh over 9 years ago
Labels: test scenario

#5 - test when percentage of nodes behind NAT

Issue - State: open - Opened by sveneh over 9 years ago
Labels: test scenario

#4 - test Hashing power discrepancy (fork rate, mining pools)

Issue - State: open - Opened by sveneh over 9 years ago - 2 comments
Labels: test scenario, prio2

#3 - test network latency and limited bandwidth

Issue - State: open - Opened by sveneh over 9 years ago - 3 comments
Labels: test scenario, prio1

#2 - churn / test clients leaving and rejoining the network

Issue - State: open - Opened by sveneh over 9 years ago - 8 comments
Labels: question, test scenario, in progress, prio1

#1 - Add proposed scenarios to issues

Issue - State: closed - Opened by heikoheiko over 9 years ago - 1 comment
Labels: help wanted