Hey guys! We heavily utilize gopacket (specifically pcapgo) in one of our projects. We use GitHub Actions to handle CI, and noticed that Linux ARM builds started failing when we switched from google/gopacket to gopacket/gopacket.
This is all of the information that the runner gives us, but hopefully it's helpful :) We don't actively need our project on Linux ARM, so we just removed that build from the pipeline. It's probably be good to get this straightened out though :D
Thanks!
--> linux/arm error: exit status 1
Stderr: # github.com/gopacket/gopacket/pcapgo
Error: /home/runner/go/pkg/mod/github.com/gopacket/[email protected]/pcapgo/capture.go:112:29: cannot use tstamp.Sec (variable of type int32) as int64 value in argument to time.Unix
Error: /home/runner/go/pkg/mod/github.com/gopacket/[email protected]/pcapgo/capture.go:112:41: cannot use tstamp.Nsec (variable of type int32) as int64 value in argument to time.Unix
Error: /home/runner/go/pkg/mod/github.com/gopacket/[email protected]/pcapgo/capture.go:115:29: cannot use tstamp.Sec (variable of type int32) as int64 value in argument to time.Unix
Hey guys! We heavily utilize
gopacket(specificallypcapgo) in one of our projects. We use GitHub Actions to handle CI, and noticed that Linux ARM builds started failing when we switched fromgoogle/gopackettogopacket/gopacket.This is all of the information that the runner gives us, but hopefully it's helpful :) We don't actively need our project on Linux ARM, so we just removed that build from the pipeline. It's probably be good to get this straightened out though :D
Thanks!