1.6.15 failure of svnlook_tests.py 11
When I run "./svnlook_tests.py 11" the test passes, but when I pass the url of an apache server such as "./svnlook_tests.py --url http://server 11" or "./svnlook_tests.py BASE_URL=http://server 11" it fails. I am running Oracle Solaris 10 9/10 s10s_u9wos_14a SPARC. Normally I pass url parameter for all tests in the BASE_URL variable when making the check target. Any help in resolving this would be appreciated. host:/proj/work/subversion-1.6.15-solaris10-sparc/subversion/tests/cmdline% ./svnlook_tests.py 11 PASS: svnlook_tests.py 11: test 'svnlook * -t' host:/proj/work/subversion-1.6.15-solaris10-sparc/subversion/tests/cmdline% ./svnlook_tests.py --url http://server 11 wrong hook logfile content EXPECTED STDOUT: U A/D/G/rho U A/mu A/ A/D/G/ ACTUAL STDOUT: /proj/work/subversion-1.6.15-solaris10-sparc/subversion/svnlook/svnlook: line 101: /proj/work/subversion-1.6.15-solaris10-sparc/subversion/svnlook/.libs/svnlook: Invalid argument /proj/work/subversion-1.6.15-solaris10-sparc/subversion/svnlook/svnlook: line 101: /proj/work/subversion-1.6.15-solaris10-sparc/subversion/svnlook/.libs/svnlook: Error 0 /proj/work/subversion-1.6.15-solaris10-sparc/subversion/svnlook/svnlook: line 101: /proj/work/subversion-1.6.15-solaris10-sparc/subversion/svnlook/.libs/svnlook: Invalid argument /proj/work/subversion-1.6.15-solaris10-sparc/subversion/svnlook/svnlook: line 101: /proj/work/subversion-1.6.15-solaris10-sparc/subversion/svnlook/.libs/svnlook: Error 0 EXCEPTION: SVNLineUnequal Traceback (most recent call last): File "/proj/work/subversion-1.6.15-solaris10-sparc/subversion/tests/cmdline/svntest/main.py", line 1226, in run rc = self.pred.run(**kw) File "/proj/work/subversion-1.6.15-solaris10-sparc/subversion/tests/cmdline/svntest/testcase.py", line 121, in run return self.func(sandbox) File "./svnlook_tests.py", line 599, in test_txn_flag verify_logfile(logfilepath, expected_data) File "./svnlook_tests.py", line 549, in verify_logfile expected_data, actual_data) File "/proj/work/subversion-1.6.15-solaris10-sparc/subversion/tests/cmdline/svntest/verify.py", line 322, in compare_and_display_lines raise raisable SVNLineUnequal FAIL: svnlook_tests.py 11: test 'svnlook * -t'
svn and autoconf
In the beta test spirit I tried something I don't usually do, to build gpsbabel under cygwin. 17 7:50svn co http://gpsbabel.googlecode.com/svn/trunk/gpsbabel gpsbabel-svn 18 7:52cd gpsbabel-svn/ 19 7:52./configure 20 7:54make The build fails because autoconf is not installed: ~/work/gpsbabel-svn% make autoconf make: autoconf: Command not found make: *** [configure] Error 127 Checking the Makefile we see the default target all depends on gpsbabel$(EXEEXT), which in turn depends on configure, which in turn depends on configure.in. all: gpsbabel$(EXEEXT) gpsbabel$(EXEEXT): configure Makefile $(OBJS) $(CC) $(CFLAGS) $(LDFLAGS) $(OBJS) -lm -lexpat -lsetupapi -lhid $(OUTPUT_SWITCH)$@ ... configure: configure.in autoconf Make has a hard time deciding if it needs to build configure. It ends up depending on the order the files were pulled during the "svn co" command. My experience on other projects is that you can not count on the timestamp order to be consistent. It seems that after a checkout make sometimes thinks a target is out of date and other times it doesn't. ~/work/gpsbabel-svn% ls -l --full-time configure* -rwxrwxrwx 1 strabert None 166729 2011-11-19 07:52:27.252371700 -0700 configure* -rwxrwxrwx 1 strabert None 11597 2011-11-19 07:52:27.630419700 -0700 configure.in* From the svn book: use-commit-times Normally your working copy files have timestamps that reflect the last time they were touched by any process, whether your own editor or some svn subcommand. This is generally convenient for people developing software, because build systems often look at timestamps as a way of deciding which files need to be recompiled. In other situations, however, it's sometimes nice for the working copy files to have timestamps that reflect the last time they were changed in the repository. The svn export command always places these “last-commit timestamps” on trees that it produces. By setting this config variable to yes, the svn checkout, svn update, svn switch, and svn revert commands will also set last-commit timestamps on files that they touch. It seems like neither choice is optimal or sufficient. For example, if I revert or update a source file after a build I need make to know the corresponding target is out of date. To get make to know it doesn't need to build configure after a checkout one might try the use-commit-times option. However, even checkout with this option may not accomplish what we want if the target and it's dependency are committed in the same changeset. In this case their times in the checkedout wc will match exactly irrespective of the timestamps these files had in the wc that was committed. Furthermore, this is an option set in the svn config file, not on the command line, so it isn't convenient to use it for one command and not another. This seems like a general issue with subversion any time a target and a dependency of that target are both in the repository. Does any body know of a good way to resolve this? Clearly I can touch configure before I make, but I am looking for a more general and automated solution. Thanks, Steve
Re: Reasearch on comment
On 5/18/2012 2:01 PM, Ryan Schmidt wrote: On May 18, 2012, at 04:12, Romain Smordowski wrote: After reasearch on the Internet, I did not find any way to find a project revision dipending on the comment. It seems that this functionnality is not yet present in subversion (I did not find an other place to ask for that). This is a good place to ask the question. You're right, Subversion doesn't have a search feature. There are third-party products you can use for that. You could even build one. They work by indexing your commits as they happen, using a post-commit hook. FishEye is a commenrial product I've heard of that I think does what you want (though I've never used it), but I'm sure there are others, possibly even open source or at least free ones. http://www.atlassian.com/software/fisheye/overview What I would like is to be able to look in a whole project the commits with a particular comment (may be with reguar expression). At work we often use specific comment (such as support issue number) so looking to the modifications that were done to answer a tocket would save a lot of time. This specific feature is usually implemented the other way around: in a post-commit hook, you parse the commit message for the ticket number. If found, you insert a comment into the ticket (hopefully your issue tracker has an API to do that) linking back to this revision (in a web-based Subversion revision viewer, which you'll probably also want a separate piece of software for, such as WebSVN, Trac, ViewVC, etc.). trac can do this. http://trac.edgewall.org/wiki/TracSearch
