Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Invalid
-
1.2.x
-
None
-
Linux
Description
After building subversion 1.2 cleanly and running the self-test prior to doing a "make install" a number of tests (close to half) failed. If subversion is installed with "make install" and then the "make check" is run all of the tests pass. This is not good since the "make check" is intended to insure that the new build is functional. I had a fresh 1.1.4 install which I was using to learn subversion and was doing the builds to update to 1.2.0 since I did not have any true repositories as yet. This is the result at the end of the "make check". for 1.2.0 after the "make install" All of the prior tests reported "success". The logs from the 1.2.0 "make check" were attached to the emails in the mailing list. Running all tests in strings-reps-test...success At least one test was SKIPPED, checking /home/laster/SubVersion/subversion-1.2.0/tests.log SKIP: revert_tests.py 2: reverting to corrupt text base should fail SKIP: utf8_tests.py 1: conversion of paths and logs to/from utf8 The "make check" in 1.1.4 runs without having to have to perform the "make install" first. In order to allow both sets of binaries to exist there are installed in two different directories and links are used in /usr/local/bin for the executables. The idea to "install" the code first was from the user mailing list (subject is the same as the summary). I am still doing testing as well.
Original issue reported by drlasterjr