ooni / probe-cli / 252

Builds Branch Commit Type Ran Committer Via Coverage
252 develop nettests: don't say ETA is infinite 1. only print time left if ETA is positive 2. skip ETA calculation with a single input 3. don't compute ETA for first entry[*] [*] this is actually what avoids emitting infinite but the other parts of this d... Pull #92 web-flow travis-ci
4.17
251 develop nettests: don't say ETA is infinite 1. only print time left if ETA is positive 2. skip ETA calculation with a single input 3. don't compute ETA for first entry[*] [*] this is actually what avoids emitting infinite but the other parts of this d... push bassosimone travis-ci
4.15
250 v3.0.0-rc.4 Readme.md build.sh: stop spreading lies about GOPATH Turns out there's no need to unset GOPATH. push bassosimone travis-ci
4.15
249 master Readme.md build.sh: stop spreading lies about GOPATH Turns out there's no need to unset GOPATH. push bassosimone travis-ci
4.15
248 master Handle the SIGINT and SIGTERM signals to support stopping a test cleanly (#84) push bassosimone travis-ci
4.17
245 release/3.0.0-rc.4 travis: run goveralls inside the docker container Factor code and reorganize location of go cache and go paths such that subsequent invocations reuse both dirs. push bassosimone travis-ci
4.16
246 release/3.0.0-rc.4 travis: run goveralls inside the docker container Factor code and reorganize location of go cache and go paths such that subsequent invocations reuse both dirs. Pull #88 web-flow travis-ci
4.15
243 release/3.0.0-rc.4 travis: run goveralls inside the docker container Factor code and reorganize location of go cache and go paths such that subsequent invocations reuse both dirs. push bassosimone travis-ci
4.15
244 release/3.0.0-rc.4 travis: run goveralls inside the docker container Factor code and reorganize location of go cache and go paths such that subsequent invocations reuse both dirs. Pull #88 web-flow travis-ci
4.15
238 clean-stop The loglevel of the line saying the signal was caught should be Info push hellais travis-ci
25.06
237 clean-stop The loglevel of the line saying the signal was caught should be Info Pull #84 web-flow travis-ci
25.06
236 clean-stop Use the atomic semantic for ensuring synchronization between goroutines See: https://golang.org/ref/mem Pull #84 web-flow travis-ci
25.06
235 clean-stop Use the atomic semantic for ensuring synchronization between goroutines See: https://golang.org/ref/mem push hellais travis-ci
25.06
233 clean-stop Add note about cancellable context push hellais travis-ci
24.98
234 clean-stop Add note about cancellable context Pull #84 web-flow travis-ci
24.98