Unexpected testsuite fauilures when building package on Versatile Express(ARM A9 smp)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Toolchain Miscellanies |
Fix Released
|
Undecided
|
Unassigned | ||
eglibc (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Source Package: eglibc (2.11.1-0ubuntu7)
Architecture: armel (A9 quad-core)
Platform: Versatile Express
Kernel 2.6.35-4.5
When doing dpkg-buildpackage -b on a unmodified source obtained with apt-get source eglibc, I obtain the following testsuite results:
#
# Testsuite failures, someone should be working towards
# fixing these! They are listed here for the purpose of
# regression testing during builds.
# Format: <Failed test>, Error <Make error code> [(ignored)]
#
annexc.out, Error 1 (ignored)
check-localplt.out, Error 1
scanf15.o, Error 1
scanf17.o, Error 1
test-fenv.out, Error 1
test-utime.out, Error 1
tst-atime.out, Error 1
tst-fdopendir.out, Error 1
tst-fseek.out, Error 1
***************
Encountered regressions that don't match expected failures (debian/
test-utime.out, Error 1
tst-atime.out, Error 1
tst-fdopendir.out, Error 1
tst-fseek.out, Error 1
TEST test-utime.out:
modtime 1280345042 <1280345037 >1280345039
TEST tst-atime.out:
atime has not changed
TEST tst-fdopendir.out:
directory atime changed
TEST tst-fseek.out:
343: st_ctime not updated
348: st_mtime not updated
439: SEEK_END works
471: SEEK_END works
Encountered progressions that don't match expected failures:
test-fpucw.out, Error 132
tst-cpuclock2.out, Error 1
tst-eintr1.out, Error 1
tst-timer.out, Error 139
description: | updated |
Changed in linaro-toolchain-misc: | |
status: | New → Fix Released |
Test buildlog attached