porridge@beczulka:~/Desktop/coding/go/src/k8s.io/ingress$ ls -l gover.coverprofile;gover
ls: cannot access gover.coverprofile: No such file or directory
porridge@beczulka:~/Desktop/coding/go/src/k8s.io/ingress$ ls -l gover.coverprofile;gover
-rw-r----- 1 porridge eng 146137 lut 24 14:58 gover.coverprofile
porridge@beczulka:~/Desktop/coding/go/src/k8s.io/ingress$ ls -l gover.coverprofile;gover
-rw-r----- 1 porridge eng 292264 lut 24 14:58 gover.coverprofile
porridge@beczulka:~/Desktop/coding/go/src/k8s.io/ingress$ ls -l gover.coverprofile;gover
-rw-r----- 1 porridge eng 438391 lut 24 14:58 gover.coverprofile
porridge@beczulka:~/Desktop/coding/go/src/k8s.io/ingress$
This means gover.coverprofile needs to be explicitly cleaned up before each execution of gover. Otherwise it causes data corruption and can lead to goveralls crashing (https://github.com/mattn/goveralls/issues/86).
I think this picture speaks for itself:
This means
gover.coverprofile
needs to be explicitly cleaned up before each execution ofgover
. Otherwise it causes data corruption and can lead to goveralls crashing (https://github.com/mattn/goveralls/issues/86).This happened for us in https://github.com/kubernetes/ingress/issues/338.
Is this by design, or a bug?