Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 353899 - gnome-base/orbit-2.14.19 tests failed
Summary: gnome-base/orbit-2.14.19 tests failed
Status: VERIFIED DUPLICATE of bug 331709
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-06 20:08 UTC by Neil Leathers
Modified: 2011-02-08 18:11 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Build Log (build.log,328.51 KB, text/plain)
2011-02-06 20:08 UTC, Neil Leathers 		Details
emerge --info =gnome-base/orbit-2.14.19 (emerge_--info_=gnome-base_slash_orbit-2.14.19,6.99 KB, text/plain)
2011-02-06 20:09 UTC, Neil Leathers 		Details
emerge -pqv =gnome-base/orbit-2.14.19 (emerge_-pqv_=gnome-base_slash_orbit-2.14.19,66 bytes, text/plain)
2011-02-06 20:10 UTC, Neil Leathers 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Neil Leathers 2011-02-06 20:08:18 UTC 
ORBit fails testing apparently due to memory leaks:

mem usage prev/post:  2028KB /  2128KB --  1000x test_ORBit_alloc ()
**
ERROR:test-mem.c:239:main_func: assertion failed: (mem_usage_end - mem_usage_start < 50)
/bin/sh: line 5: 19984 Aborted                 ${dir}$tst
FAIL: test-mem


Reproducible: Always

Steps to Reproduce:
1. emerge orbit

Actual Results:  
Tests fail

Expected Results:  
Build installs correctly
Comment 1 Neil Leathers 2011-02-06 20:08:51 UTC 
Created attachment 261676 [details]
Build Log
Comment 2 Neil Leathers 2011-02-06 20:09:42 UTC 
Created attachment 261678 [details]
emerge --info =gnome-base/orbit-2.14.19
Comment 3 Neil Leathers 2011-02-06 20:10:09 UTC 
Created attachment 261680 [details]
emerge -pqv =gnome-base/orbit-2.14.19
Comment 4 Pacho Ramos gentoo-dev 2011-02-07 09:04:31 UTC 

*** This bug has been marked as a duplicate of bug 331709 ***