issues
search
laurentsenta
/
pl-github
0
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Update version.json
#25
laurentsenta
closed
1 year ago
1
Pr with ref (from fork)
#24
laurentsenta
closed
2 years ago
0
Pr with ref
#23
laurentsenta
closed
2 years ago
0
add echo name
#22
laurentsenta
closed
2 years ago
0
Throw explicit error when an event is not parsed correctly
#21
laurentsenta
opened
2 years ago
0
Notes
#20
laurentsenta
opened
2 years ago
1
Build the current libp2p/test-plans test on the k8s cluster
#19
laurentsenta
opened
2 years ago
1
make sure the rust example in testground examples works
#18
laurentsenta
opened
2 years ago
3
we have a ping test (rust implementation) that runs on local machine
#17
laurentsenta
opened
2 years ago
0
testground tasks shows "failed" but the test ran successful (go libp2p ping)
#16
laurentsenta
opened
2 years ago
1
Running testground in docker
#15
laurentsenta
opened
2 years ago
1
Sometimes testground tasks w/Docker will fail to get cleared
#14
laurentsenta
opened
2 years ago
1
the ping test passes consistently on local machine
#13
laurentsenta
opened
2 years ago
2
the ping test can be used to test interop between 2 different versions
#12
laurentsenta
opened
2 years ago
5
The builder hangs when you try to use a custom go image (`1.17-buster` in my case)
#11
laurentsenta
opened
2 years ago
1
Our main maintainers can use testground on their local machine
#10
laurentsenta
opened
2 years ago
2
When something goes wrong with the sync service, I have tools to identify the issue
#9
laurentsenta
opened
2 years ago
0
Clarify the sync service pub sub capabilities
#8
laurentsenta
closed
2 years ago
1
When a test hangs, testground eventually kills it
#7
laurentsenta
opened
2 years ago
0
Testground doesn't show weird errors in the CLI
#6
laurentsenta
opened
2 years ago
1
EPIC2: Testground is reliable
#5
laurentsenta
opened
2 years ago
1
EPIC1: Testground is used by our core maintainers on critical IP-stewart projects.
#4
laurentsenta
opened
2 years ago
0
EPIC1.3: As a go-ipfs maintainer, I can see the bitswaps testplans passing with the latest go-ipfs version.
#3
laurentsenta
opened
2 years ago
1
EPIC1.2: As a rust-libp2p maintainer, I have all the tooling I need to create new interoperability tests on my machine, have them run on the CI, and confirm interoperability with go-libp2p
#2
laurentsenta
opened
2 years ago
0
EPIC1.1: As a go-libp2p maintainer I have all the tooling I need to create new interoperability tests on my machine and make sure they are used in the CI to test every release
#1
laurentsenta
opened
2 years ago
10