-
https://build.golang.org/log/56b688f3bdc981ffdeb03abab6d7519abbb782a6 shows numerous failures & timeouts for the `x/tools` repo on the new `darwin-amd64-longtest` builder (#35678).
They all appear …
-
In #20892, I re-opened an issue, only to have @gopherbot re-close it. This is an issue to follow-up on what happened there. cc @andybons @kevinburke
-
(consider this as a work-in-progress design doc, it will be periodically updated)
EDIT 2019-06-20
# Data Flow Trace
The Data Flow Trace (DFT) tells the fuzzing engine which bytes of a given inpu…
-
File "train.py", line 122, in
train_abs(args, device_id)
File "E:\project\PreSumm\src\train_abstractive.py", line 273, in train_abs
train_abs_single(args, device_id)
File "E:\projec…
-
In lieu of an automated builder, I run the x/build tests in Travis CI. @andybons has fixed two problems with cmd/cl and with cloud.google.com depedencies, but this has revealed a number of underlying …
-
First of all, I found I had to change ./configure by removing the leading `../` and trailing `/` in the path:
```
(cd build >/dev/null 2>&1 && cmake -DEIGEN3_INCLUDE_DIR=eigen .. "$@")
```
so…
-
Both CFLite and CIFuzz exit as soon as they discover a bug but it would be great if it was possible to let them run all fuzz targets and report all the bugs. It would be consistent with how test suite…
-
Go-fuzz (https://github.com/dvyukov/go-fuzz) is quite successful at finding bugs in Go code and reasonably widely used in Go community. However there are several problems with the current go-fuzz impl…
-
I get:
```
thread 'main' panicked at 'there is no reactor running, must be called from the context of a Tokio 1.x runtime', /Users/moritz/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.8.1/…
-
We have lots of places where we have type constraints that are not necessary, old code that is not supported/unused, things which we have no tests for, code is disorganised due to the many hands probl…