Bug 433809 - subversion failing selftests on ia64
Summary: subversion failing selftests on ia64
Alias: None
Product: Fedora
Classification: Fedora
Component: subversion
Version: rawhide
Hardware: ia64
OS: Linux
Target Milestone: ---
Assignee: Doug Chapman
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: fedora-ia64
TreeView+ depends on / blocked
Reported: 2008-02-21 15:53 UTC by Doug Chapman
Modified: 2008-02-25 04:59 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2008-02-25 04:59:23 UTC

Attachments (Terms of Use)

Description Doug Chapman 2008-02-21 15:53:00 UTC
Description of problem:

This will be assigned to someone in the fedora-ia64 team for more triage since
we don't have installable rawhide-ia64 trees yet.

Subversion failing on ia64.  I will investigate more but it appears python is
not getting pulled in to the mock build.

From the build.log:

ENTER do("bash --login -c 'rpmbuild -bs --target ia64 --nodeps
'/var/lib/mock/dist-f9-build-2547-758/root/', 0, True, 0, <mock.uid.uidManager
object at 0x200000000530a090>, 100, 103, None,
logger=<mock.trace_decorator.getLog object at 0x200000000530a750>)
run cmd timeout(0): bash --login -c 'rpmbuild -bs --target ia64 --nodeps
/etc/profile: line 38: /bin/hostname: No such file or directory
cat: /usr/include/httpd/.mmn: No such file or directory
sh: ruby: command not found
sh: /usr/bin/python: No such file or directory
sh: /usr/bin/python: No such file or directory
sh: /usr/bin/python: No such file or directory
sh: /usr/bin/python: No such file or directory

Then, after the build of subversion itself many (but oddly not all) tests
written in python fail:

Running all tests in translate-test...success
Running all tests in utf-test...success
Running all tests in target-test.py...success
Running all tests in getopt_tests.py...success
Running all tests in basic_tests.py...FAILURE
Running all tests in commit_tests.py...FAILURE
Running all tests in update_tests.py...FAILURE
Running all tests in switch_tests.py...FAILURE
Running all tests in prop_tests.py...FAILURE

Full build log can be found at:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Doug Chapman 2008-02-21 19:01:07 UTC
It appears the "sh: /usr/bin/python: No such file or directory" messages are
unrelated.  I chedked on an x86_64 koji build log and it shows those same errors
but that build passed.  those are just seen when doing the rpmbuild -bs, not
when doing the actual build of the binary rpm.

So now it is just a matter of trying to figure out why many of the tests are
failing on ia64.

Comment 2 Zhan, Yi 2008-02-22 09:57:44 UTC
I tried to build the package on my box using mock and the ia64 rawhide bits,
excepting one package buildsys-build, which we used to create the root-cache in
F8-cycle. But I was unable to reproduce this bug. The package just built
cleanly. I think it might be helpful to build it on other build servers again to
verify the error.  

Comment 3 Doug Chapman 2008-02-25 04:59:12 UTC
subversion-1.4.6-5 has now built cleanly on our koji server.  Odd, must have
been a glitch on the build server I guess?

Note You need to log in before you can comment on or make changes to this bug.