influxdata / influxdata/kapacitor
Flakey Test TestServer_AlertHandlers/snmptrap-17
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
2020/04/22 16:44:08 D! ALERT test/testAlertHandlers message
--- FAIL: TestServer_AlertHandlers (6.00s)
--- FAIL: TestServer_AlertHandlers/snmptrap-17 (0.23s)
server_test.go:10547: snmptrap: unexpected snmptrap request:
exp
[{Pdu:{IsNil:false Type:SNMPTrapV2 ErrorStatus:NoError ErrorIndex:0 VarBinds:[{Oid:1.3.6.1.2.1.1.3.0 Value:1000 Type:TimeTicks} {Oid:1.3.6.1.6.3.1.1.4.1.0 Value:1.1.2 Type:Oid} {Oid:1.1.2.1 Value:message Type:OctetString} {Oid:1.1.2.2 Value:CRITICAL Type:OctetString}]} Error:}]
got
[]
FAIL
Contributor guide
Research direction
Start by running TestServer_AlertHandlers, focusing on the snmptrap-17 case reported at server_test.go:10547. Compare the expected and received SNMP trap data in the failure output and trace the alert handler path. Done means the test reliably receives the expected trap and passes without intermittent failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100