Libbeat test failures on 32-bit systems

I'm working on getting beats to build/run on my Raspberry Pi 3, running Raspbian, which is 32-bit. I'm running into a test build failure in libbeat/processors/processor_test.go, and consequently, make unit-tests fails.

command [go test -cover -coverprofile /tmp/gotestcover-757345234 github.com/elastic/beats/libbeat/processors]: exit status 2
# github.com/elastic/beats/libbeat/processors_test
processors/processor_test.go:120: constant 2555572224 overflows int
processors/processor_test.go:138: constant 2555572224 overflows int
processors/processor_test.go:188: constant 2555572224 overflows int
processors/processor_test.go:242: constant 2555572224 overflows int
processors/processor_test.go:312: constant 2555572224 overflows int
processors/processor_test.go:404: constant 2555572224 overflows int
processors/processor_test.go:449: constant 2555572224 overflows int
processors/processor_test.go:607: constant 2555572224 overflows int
FAIL	github.com/elastic/beats/libbeat/processors [build failed]

There are a number of maps created with numeric field values that overflow int (which is 32-bits on a 32-bit OS). See the "size" field in the example below:

    event := common.MapStr{
    		"@timestamp": "2016-01-24T18:35:19.308Z",
    		"beat": common.MapStr{
    			"hostname": "mar",
    			"name":     "my-shipper-1",
    		},
    		"proc": common.MapStr{
    			"cpu": common.MapStr{
    				"start_time": "Jan14",
    				"system":     26027,
    				"total":      79390,
    				"total_p":    0,
    				"user":       53363,
    			},
    			"name":    "test-1",
    			"cmdline": "/sbin/launchd",
    			"mem": common.MapStr{
    				"rss":   11194368,
    				"rss_p": 0,
    				"share": 0,
    				"size":  2555572224,
    			},
    		},
    		"type": "process",
    	}

Should I open an issue for this on Github and submit a fix?

Thanks for reporting. Feel free to open a PR fixing the test.

PR here: https://github.com/elastic/beats/pull/3441

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.