On Tue, Aug 20, 2024 at 5:34 AM M.Tarkeshwar Rao <tarkeshwa...@gmail.com> wrote:
>
> As part of regular LCM activity we are doing GoLang LCM. Issue is:
>
> This is to bring to your immediate attention that while doing golang LCM ,
> we changed it to 1.22.3 but CI job failed on the same .
> Upon debugging application it was deduced that there may be memory issue.
> But even after trying the same on different dev machines same issue occurred.
> Trying locally also it is failing with same error.
> This is application error applicaton Docker image building.
>
> This is a blocker for us. Kindly help us deducing how to proceed further.
>
> Error:
> Step 41/72 : RUN make build-go GO_BUILD_TAGS=${GO_BUILD_TAGS}
> WIRE_TAGS=${WIRE_TAGS}
> ---> Running in 0c954cffd4a6
> (re)installing /root/go/bin/wire-v0.5.0
> go: downloading github.com/pmezard/go-difflib v1.0.0
> go: downloading github.com/google/subcommands v1.0.1
> go: downloading golang.org/x/tools v0.0.0-20190422233926-fe54fb35175b
> generate go files
> /root/go/bin/wire-v0.5.0 gen -tags oss ./pkg/server
> panic: runtime error: invalid memory address or nil pointer dereference
> [recovered]
> panic: runtime error: invalid memory address or nil pointer
> dereference
> [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x57fd2f]
>
> goroutine 875 [running]:
> go/types.(*Checker).handleBailout(0xc000d09800, 0xc00636fca8)
> /usr/local/go/src/go/types/check.go:367 +0x88
>
> My query is that what should we do for this error. We need to revert back or
> move to another version.
Is there a way that we can recreate the problem?
Ian
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/CAOyqgcWt3no867vP4BdL5HHxWJ%3DkVHsc5v-8LZmamO%3DpmD8pBw%40mail.gmail.com.
