building fuzzers failed after bumping quic-go version #232
Comments
|
That is strange given that Kubeedge builds fine on OSS-Fuzz. |
|
I may not have been clear, it is not the master branch of Kubeedge that brings out this issue, it is on my own repository https://github.com/vincentgoat/kubeedge/tree/verifynodecert. |
|
When I build KubeEdge with go version 1.18, I got the same error but it works fine with go1.16/go1.17. I'm wondering if the OSS-Fuzz builder takes go1.18 to build fuzzer? |
AdamKorcz
pushed a commit
to google/oss-fuzz
that referenced
this issue
Nov 1, 2022
Signed-off-by: vincentgoat <linguohui1@huawei.com> install go1.17 for KubeEdge when building fuzzers Fix issue cncf/cncf-fuzzing#232 cc @AdamKorcz Signed-off-by: vincentgoat <linguohui1@huawei.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Building fuzzers failed after bumping quic-go version.
Errors are
/root/go/pkg/mod/github.com/lucas-clemente/quic-go@v0.24.0/internal/qtls/go118.go:6:13: cannot use "quic-go doesn't build on Go 1.18 yet." (untyped string constant) as int value in variable declaration, but it is normal when we build our artifacts manually.More details show as follows.
https://github.com/kubeedge/kubeedge/actions/runs/3359066312/jobs/5566711345
cc @AdamKorcz
The text was updated successfully, but these errors were encountered: