Bug 655731

Summary:	T065agentextend_simple fails on s390x and ppc64
Product:	[Fedora] Fedora	Reporter:	Dan Horák <dan>
Component:	net-snmp	Assignee:	Jan Safranek <jsafrane>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	jsafrane
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	net-snmp-5.6-4.fc15	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-23 08:58:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Horák 2010-11-22 10:28:58 UTC

Test T065agentextend_simple from net-snmp 5.6 fails on s390x and ppc64

extending agent functionality with extend ......................... 
not ok 2 - found 0 copies of 'hello_world' in output (/tmp/snmp-test-T065agentextend_simple-26763/output-simple_run26763-1); expected 1
not ok 3 - found 0 copies of 'hello_world' in output (/tmp/snmp-test-T065agentextend_simple-26763/output-simple_run26763-2); expected 1
not ok 4 - found 0 copies of 'hello_world' in output (/tmp/snmp-test-T065agentextend_simple-26763/output-simple_run26763-3); expected 1
not ok 5 - found 0 copies of 'INTEGER: 1' in output (/tmp/snmp-test-T065agentextend_simple-26763/output-simple_run26763-4); expected 1
not ok 6 - found 0 copies of 'INTEGER: 0' in output (/tmp/snmp-test-T065agentextend_simple-26763/output-simple_run26763-5); expected 1
Dubious, test returned 1 (wstat 256, 0x100)
Failed 5/9 subtests 

Test environments:
Fedora Rawhide on s390x
RHEL-6 on ppc64

Package version:
net-snmp-5.6-2.fc15

Comment 1 Jan Safranek 2010-11-22 14:45:56 UTC

Note to self: it seems to be fixed in current SVN trunk.

Comment 2 Jan Safranek 2010-11-22 15:18:01 UTC

Fixed in SVN rev. 19485, with following comment: "Not sure what the implications of this bug were. It might have caused very strange table behavior on 64-bit big endian systems." :)