[prev in list] [next in list] [prev in thread] [next in thread]
List: darcs-devel
Subject: [darcs-devel] How to tell when the test suite fails?
From: "Jason Dagit" <dagit () codersbase ! com>
Date: 2008-04-23 18:00:27
Message-ID: b97f58860804231100o4eb19bb7q3423934c3e305958 () mail ! gmail ! com
[Download RAW message or body]
Hello,
I'm often confused by the output of the darcs test suite. In this
case I recorded a patch which required the test suite to run and in
the end darcs accepted it. During the process though I almost stopped
the test suite because I thought it had failed. As you can see below.
Did my tests really pass or fail? Below is a cut&paste from my
terminal's scrollback.
Thanks,
Jason
Running shell tests on hashed repositories...
Running shell tests on old-fashioned repositories...
Demonstrating shell bugs on hashed repositories...
Running shell tests on darcs-2 repositories...
Demonstrating shell bugs on old-fashioned repositories...
Running perl tests on hashed repositories...
Running perl tests on darcs-2 repositories...
Running perl tests on old-fashioned repositories...
Demonstrating shell bugs on format-2 repositories...
Demonstrating perl bugs on old-fashioned repositories...
Demonstrating perl bugs on hashed repositories...
Demonstrating perl bugs on darcs-2 repositories...
Running either_dependency.sh ... Running
either_dependency.sh ... Running either_dependency.sh
...
whatsnew.......whatsnew.......whatsnew.......Running what_sl.sh ...
workingdir.............................Running
what_sl.sh ... whatsnew.......1/? passed.
whatsnew.......ok cel.sh ...
All tests successful.
Files=1, Tests=2, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.09 cusr
0.07 csys = 0.18 CPU)
Result: PASS
Done demonstrating bugs on old-fashioned repositories...
passed.
whatsnew.......ok cel.sh ...
All tests successful.
Files=1, Tests=2, 2 wallclock secs ( 0.01 usr 0.00 sys + 0.09 cusr
0.07 csys = 0.17 CPU)
Result: PASS
Done demonstrating bugs on hashed repositories...
passed.
Running unrevert_cancel.sh ...
workingdir......................whatsnew.......ok
orkingdir.............................
All tests successful.
Files=1, Tests=2, 2 wallclock secs ( 0.01 usr 0.01 sys + 0.09 cusr
0.06 csys = 0.17 CPU)
Result: PASS
Done demonstrating bugs on darcs-2 repositories...
passed.
Running unrevert.sh ... passed.
Running unrevert.sh ... passed.
Running unrevert.sh ... passed.
Running unrecord.sh ... passed.
Running unrecord.sh ... passed.
Running unrecord.sh ... passed.
Running unpull.sh ... passed.
Running unpull.sh ... passed.
Running unpull.sh ... FAILED!
Output from failed either_dependency.sh:
test $DARCS || DARCS=$PWD/../darcs
export DARCS_EMAIL=test
rm -rf tmp_d1 tmp_d2 tmp_d
# Preparations:
# Set up two repos, each with a patch (d1 and d2 respectively) with both
# an individual change and a change that is identical in both repos,
# and thus auto-merge, i.e., they don't conflict in darcs2. Pull them
# together and record a patch (problem) on top of the auto-merged change,
# so that it depends on EITHER of two patches.
mkdir tmp_d1; cd tmp_d1
$DARCS init --darcs-2
echo a > a
echo b > b
echo c > c
$DARCS rec -alm init
Finished recording patch 'init'
echo a-independent > a
echo c-common > c
$DARCS rec -am d1
Finished recording patch 'd1'
cd ..
$DARCS get --to-patch init tmp_d1 tmp_d2
Copying patches, to get lazy repository hit ctrl-C...
Unapplying 1 patch.
Finished getting.
cd tmp_d2
echo b-independent > b
echo c-common > c
$DARCS rec -am d2
Finished recording patch 'd2'
$DARCS pull -a ../tmp_d1
Finished pulling and applying.
# no conflicts -- c-common is identical
echo c-problem > c
$DARCS rec -am problem
Finished recording patch 'problem'
cd ..
# I want to pull the 'problem' patch, but expect darcs to get confused
# because it doesn't know how to select one of the two dependent patches.
$DARCS get --to-patch init ../tmp_d2 tmp_d
Copying patches, to get lazy repository hit ctrl-C...
Unapplying 3 patches.
Finished getting.
cd tmp_d
echo n/n/y |tr / \\012 |$DARCS pull ../tmp_d2
Pulling from "../tmp_d2"...
Wed Apr 23 10:41:16 PDT 2008 test
* d2
Shall I pull this patch? (1/3) [ynWvpxdaqjk], or ? for help:
Wed Apr 23 10:41:15 PDT 2008 test
* d1
Shall I pull this patch? (2/3) [ynWvpxdaqjk], or ? for help:
Wed Apr 23 10:41:18 PDT 2008 test
* problem
Shall I pull this patch? (3/3) [ynWsfvpxdaqjk], or ? for help:
Finished pulling and applying.
$DARCS cha
Wed Apr 23 10:41:18 PDT 2008 test
* problem
Wed Apr 23 10:41:16 PDT 2008 test
* d2
Wed Apr 23 10:41:14 PDT 2008 test
* init
# This is weird, we got d2 though we said No. I would have expected
# darcs to skip the 'problem' patch in this case.
# Try to pull d1 and unpull d2.
$DARCS pull -a ../tmp_d1
Finished pulling and applying.
echo n/y/d |tr / \\012 |$DARCS obl -p d2
Wed Apr 23 10:41:18 PDT 2008 test
* problem
Shall I obliterate this patch? (1/2) [ynWsfvpxdaqjk], or ? for help:
Wed Apr 23 10:41:16 PDT 2008 test
* d2
Shall I obliterate this patch? (2/2) [ynWvpxdaqjk], or ? for help:
darcs: bug in darcs!
patches to commute_to_end does not commutex (1) at
src/Darcs/Patch/Depends.lhs:440 compiled Apr 23 2008 10:39:13
I'm unable to check http://darcs.net/maintenance to see if this
version is supported.
If it is is supported, please report this to bugs@darcs.net
If possible include the output of 'darcs --exact-version'.
Running broken-pipe.sh ... passed.
workingdir.............................1/? passed.
workingdir.............................1/? passed.
Running uniqueoptions.sh ... FAILED!
Output from failed either_dependency.sh:
test $DARCS || DARCS=$PWD/../darcs
export DARCS_EMAIL=test
rm -rf tmp_d1 tmp_d2 tmp_d
# Preparations:
# Set up two repos, each with a patch (d1 and d2 respectively) with both
# an individual change and a change that is identical in both repos,
# and thus auto-merge, i.e., they don't conflict in darcs2. Pull them
# together and record a patch (problem) on top of the auto-merged change,
# so that it depends on EITHER of two patches.
mkdir tmp_d1; cd tmp_d1
$DARCS init --darcs-2
echo a > a
echo b > b
echo c > c
$DARCS rec -alm init
Finished recording patch 'init'
echo a-independent > a
echo c-common > c
$DARCS rec -am d1
Finished recording patch 'd1'
cd ..
$DARCS get --to-patch init tmp_d1 tmp_d2
Copying patches, to get lazy repository hit ctrl-C...
Unapplying 1 patch.
Finished getting.
cd tmp_d2
echo b-independent > b
echo c-common > c
$DARCS rec -am d2
Finished recording patch 'd2'
$DARCS pull -a ../tmp_d1
Finished pulling and applying.
# no conflicts -- c-common is identical
echo c-problem > c
$DARCS rec -am problem
Finished recording patch 'problem'
cd ..
# I want to pull the 'problem' patch, but expect darcs to get confused
# because it doesn't know how to select one of the two dependent patches.
$DARCS get --to-patch init ../tmp_d2 tmp_d
Copying patches, to get lazy repository hit ctrl-C...
Unapplying 3 patches.
Finished getting.
cd tmp_d
echo n/n/y |tr / \\012 |$DARCS pull ../tmp_d2
Pulling from "../tmp_d2"...
Wed Apr 23 10:41:16 PDT 2008 test
* d2
Shall I pull this patch? (1/3) [ynWvpxdaqjk], or ? for help:
Wed Apr 23 10:41:15 PDT 2008 test
* d1
Shall I pull this patch? (2/3) [ynWvpxdaqjk], or ? for help:
Wed Apr 23 10:41:19 PDT 2008 test
* problem
Shall I pull this patch? (3/3) [ynWsfvpxdaqjk], or ? for help:
Finished pulling and applying.
$DARCS cha
Wed Apr 23 10:41:19 PDT 2008 test
* problem
Wed Apr 23 10:41:16 PDT 2008 test
* d2
Wed Apr 23 10:41:14 PDT 2008 test
* init
# This is weird, we got d2 though we said No. I would have expected
# darcs to skip the 'problem' patch in this case.
# Try to pull d1 and unpull d2.
$DARCS pull -a ../tmp_d1
Finished pulling and applying.
echo n/y/d |tr / \\012 |$DARCS obl -p d2
Wed Apr 23 10:41:19 PDT 2008 test
* problem
Shall I obliterate this patch? (1/2) [ynWsfvpxdaqjk], or ? for help:
Wed Apr 23 10:41:16 PDT 2008 test
* d2
Shall I obliterate this patch? (2/2) [ynWvpxdaqjk], or ? for help:
darcs: bug in darcs!
patches to commute_to_end does not commutex (1) at
src/Darcs/Patch/Depends.lhs:440 compiled Apr 23 2008 10:39:13
I'm unable to check http://darcs.net/maintenance to see if this
version is supported.
If it is is supported, please report this to bugs@darcs.net
If possible include the output of 'darcs --exact-version'.
workingdir.............................1/? passed.
workingdir.............................2/? FAILED!
Output from failed either_dependency.sh:
test $DARCS || DARCS=$PWD/../darcs
export DARCS_EMAIL=test
rm -rf tmp_d1 tmp_d2 tmp_d
# Preparations:
# Set up two repos, each with a patch (d1 and d2 respectively) with both
# an individual change and a change that is identical in both repos,
# and thus auto-merge, i.e., they don't conflict in darcs2. Pull them
# together and record a patch (problem) on top of the auto-merged change,
# so that it depends on EITHER of two patches.
mkdir tmp_d1; cd tmp_d1
$DARCS init --darcs-2
echo a > a
echo b > b
echo c > c
$DARCS rec -alm init
Finished recording patch 'init'
echo a-independent > a
echo c-common > c
$DARCS rec -am d1
Finished recording patch 'd1'
cd ..
$DARCS get --to-patch init tmp_d1 tmp_d2
Copying patches, to get lazy repository hit ctrl-C...
Unapplying 1 patch.
Finished getting.
cd tmp_d2
echo b-independent > b
echo c-common > c
$DARCS rec -am d2
Finished recording patch 'd2'
$DARCS pull -a ../tmp_d1
Finished pulling and applying.
# no conflicts -- c-common is identical
echo c-problem > c
$DARCS rec -am problem
Finished recording patch 'problem'
cd ..
# I want to pull the 'problem' patch, but expect darcs to get confused
# because it doesn't know how to select one of the two dependent patches.
$DARCS get --to-patch init ../tmp_d2 tmp_d
Copying patches, to get lazy repository hit ctrl-C...
Unapplying 3 patches.
Finished getting.
cd tmp_d
echo n/n/y |tr / \\012 |$DARCS pull ../tmp_d2
Pulling from "../tmp_d2"...
Wed Apr 23 10:41:17 PDT 2008 test
* d2
Shall I pull this patch? (1/3) [ynWvpxdaqjk], or ? for help:
Wed Apr 23 10:41:15 PDT 2008 test
* d1
Shall I pull this patch? (2/3) [ynWvpxdaqjk], or ? for help:
Wed Apr 23 10:41:19 PDT 2008 test
* problem
Shall I pull this patch? (3/3) [ynWsfvpxdaqjk], or ? for help:
Finished pulling and applying.
$DARCS cha
Wed Apr 23 10:41:19 PDT 2008 test
* problem
Wed Apr 23 10:41:17 PDT 2008 test
* d2
Wed Apr 23 10:41:14 PDT 2008 test
* init
# This is weird, we got d2 though we said No. I would have expected
# darcs to skip the 'problem' patch in this case.
# Try to pull d1 and unpull d2.
$DARCS pull -a ../tmp_d1
Finished pulling and applying.
echo n/y/d |tr / \\012 |$DARCS obl -p d2
Wed Apr 23 10:41:19 PDT 2008 test
* problem
Shall I obliterate this patch? (1/2) [ynWsfvpxdaqjk], or ? for help:
Wed Apr 23 10:41:17 PDT 2008 test
* d2
Shall I obliterate this patch? (2/2) [ynWvpxdaqjk], or ? for help:
darcs: bug in darcs!
patches to commute_to_end does not commutex (1) at
src/Darcs/Patch/Depends.lhs:440 compiled Apr 23 2008 10:39:13
I'm unable to check http://darcs.net/maintenance to see if this
version is supported.
If it is is supported, please report this to bugs@darcs.net
If possible include the output of 'darcs --exact-version'.
Running broken-pipe.sh ... passed.
Running tricky_unrecord.sh ... passed.
workingdir.............................2/? passed.
workingdir.............................5/? passed.
Running three_way_conflict.sh ... passed.
workingdir.............................ok
whatsnew...............................ok
workingdir.............................ok
workingdir.............................ok
whatsnew...............................1/? passed.
unpull.................................1/? passed.
whatsnew...............................ok
unpull.................................ok
tag.................................... passed.
whatsnew...............................ok
tag....................................ok
unpull.................................ok
tag.................................... passed.
Running ssh.sh ... passed.
unpull.................................1/? passed.
Running ssh.sh ... passed.
tag....................................ok
unpull.................................ok
show_contents..........................ok
setpref................................ passed.
Running ssh.sh ... passed.
tag....................................ok
show_contents..........................ok
setpref................................ok
show_contents..........................ok
setpref................................ok
setpref................................ok
set_scripts_executable.................ok
set_scripts_executable.................ok
set_scripts_executable.................ok
rollback_conflict......................ok
rmdir..................................ok
restrictive_upstream_permissions.......ok
rollback_conflict......................ok
rollback_conflict......................ok
rmdir..................................ok
rmdir..................................ok
repo_not_writable......................ok
restrictive_upstream_permissions.......ok
restrictive_upstream_permissions.......ok
record_editor..........................ok
repo_not_writable......................ok
record.................................8/?
record_editor........................repo_not_writable......................ok
record.................................ok
record_editor..........................ok
record_editor..........................ok
put....................................ok
record.................................ok
push...................................ok
put....................................ok
record.................................ok
put....................................ok
push...................................ok
push...................................ok
pull_many_files........................1/? passed.
Running show_tags.sh ... passed.
Running several_commands.sh ... passed.
Running send_apply.sh ... passed.
Running send.sh ... passed.
Running sametwice.sh ... passed.
Running show_tags.sh ... passed.
Running rollback.sh ... passed.
Running several_commands.sh ... passed.
Running show_tags.sh ... passed.
Running send_apply.sh ... passed.
Running several_commands.sh ... passed.
Running send_apply.sh ... passed.
Running send.sh ... passed.
Running rmdir.sh ... passed.
Running sametwice.sh ... passed.
pull_many_files........................2/? passed.
pull_many_files........................3/? passed.
Running rollback.sh ... passed.
Running rmconflict.sh ... passed.
TESTS FAILED!
either_dependency.sh
Done demonstrating bugs on old-fashioned repositories...
pull_many_files........................2/? passed.
pull_many_files........................3/? passed.
pull_many_files........................2/? passed.
Running revert_interactive.sh ... passed.
pull_many_files........................3/? passed.
Running repodir.sh ... passed.
Running rmdir.sh ... passed.
Running replace_after_pending_mv.sh ... passed.
Running rmconflict.sh ... passed.
Running replace_after_pending_add.sh ... passed.
Running replace.sh ... passed.
Running revert_unrecorded_add.sh ... passed.
Running rmconflict.sh ... passed.
Running revert_interactive.sh ... passed.
Running repair.sh ... passed.
Running revert_unrecorded_add.sh ... passed.
Running revert_interactive.sh ... passed.
Running repodir.sh ... passed.
Running recordrace.sh ... passed.
Running replace_after_pending_mv.sh ... passed.
Running query_manifest.sh ... passed.
Running replace_after_pending_add.sh ... passed.
Running replace.sh ... passed.
Running repodir.sh ... passed.
Running replace_after_pending_mv.sh ... passed.
Running replace_after_pending_add.sh ... passed.
Running replace.sh ... passed.
Running repair.sh ... passed.
Running repair.sh ... passed.
Running recordrace.sh ... passed.
Running recordrace.sh ... passed.
Running query_manifest.sh ... passed.
Running query_manifest.sh ... passed.
Running push_lock.sh ... passed.
pull_many_files........................4/? passed.
Running pull_two.sh ... passed.
pull_many_files........................5/? passed.
pull_many_files........................5/? passed.
Running push.sh ... passed.
Running push_lock.sh ... passed.
Running pull_binary.sh ... passed.
Running pull_two.sh ... passed.
pull_many_files........................4/? passed.
Running pull.sh ... passed.
Running pull_two.sh ... passed.
Running pull_compl.sh ... passed.
Running prehook.sh ... passed.
pull_many_files........................5/? passed.
Running prefs.sh ... passed.
Running posthook.sh ... passed.
Running perms.sh ... passed.
Running pending.sh ... passed.
Running pull_binary.sh ... passed.
Running pull_binary.sh ... passed.
Running pull.sh ... passed.
Running partial.sh ... passed.
Running pull.sh ... passed.
Running prehook.sh ... passed.
Running optimize_relink.sh ... passed.
Running prefs.sh ... passed.
Running posthook.sh ... passed.
Running obliterate.sh ... passed.
Running prehook.sh ... passed.
Running perms.sh ... passed.
Running prefs.sh ... passed.
Running posthook.sh ... passed.
Running perms.sh ... passed.
Running pending.sh ... passed.
Running nonewline.sh ... passed.
Running pending.sh ... passed.
Running partial.sh ... passed.
Running partial.sh ... passed.
pull_many_files........................6/? passed.
Running optimize_relink.sh ... passed.
Running optimize_relink.sh ... passed.
pull_many_files........................6/? passed.
Running obliterate.sh ... passed.
Running obliterate.sh ... passed.
pull_many_files........................6/? passed.
Running mv_and_remove_tests.sh ... passed.
Running nonewline.sh ... passed.
pull_many_files........................ok
pull_directory_not_empty............... passed.
Running nodeps.sh ... passed.
pull_directory_not_empty...............ok
passed.
pull_many_files........................ok
pull...................................7/? Writing inventory 1/1 : ...........
pull_directory_not_empty...............ok
pull...................................13/? passed.
TESTS FAILED!
either_dependency.sh
Done demonstrating bugs on hashed repositories...
pull...................................15/? passed.
pull...................................7/? passed.
pull_many_files........................ok
pull_directory_not_empty............... passed.
Running mergeresolved.sh ... passed.
pull...................................15/? passed.
pull...................................17/? passed.
pull_directory_not_empty...............ok
pull...................................16/? passed.
TESTS FAILED!
either_dependency.sh
Done demonstrating bugs on format-2 repositories...
pull...................................1/? passed.
Running mv_and_remove_tests.sh ... passed.
Running mv_and_remove_tests.sh ... passed.
Running mv.sh ... passed.
pull...................................7/? passed.
Running mv-test-suite.sh ... passed.
Running mergeresolved.sh ... passed.
pull...................................17/? passed.
pull...................................18/? passed.
pull...................................ok
printer................................ok
pending_has_conflicts..................ok
optimize...............................ok
pull...................................ok
obliterate_before_a_tag................ok
obliterate............................. passed.
obliterate.............................1/? passed.
obliterate.............................ok
printer................................13/? passed.
printer................................ok
pending_has_conflicts.................. passed.
pending_has_conflicts..................1/? passed.
pending_has_conflicts..................ok
mv.....................................1/13
optimize............................... passed.
mv.....................................2/13 passed.
Running issue458.sh ... passed.
mv.....................................ok
missed_resolution...................... passed.
optimize...............................ok
obliterate_before_a_tag................ passed.
pull...................................ok
passed.
Running issue194.sh ...
printer................................ passed.
obliterate_before_a_tag................ok
printer................................1/? passed.
printer................................ok
obliterate.............................ok
mv..................................... passed.
pending_has_conflicts..................ok ...
missed_resolution......................ok
passed.
Running impossible_unrevert.sh ...
merging_newlines....................... passed.
mv.....................................1/13 passed.
Running issue706.sh ... passed.
Running justrm.sh ... passed.
optimize...............................1/? passed.
Running issue706.sh ... passed.
optimize...............................ok
obliterate_before_a_tag................ passed.
merging_newlines.......................1/? passed.
mv.....................................ok
missed_resolution...................... passed.
Running issue458.sh ... passed.
Running issue436.sh ... passed.
Running issue381.sh ... passed.
merging_newlines.......................3/?
# Failed (TODO) test 'after a conflict, darcs resolve should report
a conflict'
# at merging_newlines.pl line 48.
# 'No conflicts to mark.
# '
# matches '(?i-xsm:no conflicts)'
passed.
merging_newlines.......................ok
match.................................. passed.
Running issue257.sh ... passed.
Running issue381.sh ... passed.
Running issue194.sh ... passed.
match..................................1/? passed.
obliterate_before_a_tag................ok
obliterate.............................ok
mv..................................... passed.
Running invalid_pending_after_mv_to_self.sh ... passed.
match..................................26/? passed.
Running hashed_inventory.sh ... passed.
Running impossible_unrevert.sh ... passed.
missed_resolution......................ok ...
merging_newlines....................... passed.
match..................................29/? passed.
match..................................46/? passed.
mv.....................................ok
missed_resolution...................... passed.
Running illegal_mv.sh ... passed.
merging_newlines.......................3/?
# Failed (TODO) test 'after a conflict, darcs resolve should report
a conflict'
# at merging_newlines.pl line 48.
# 'No conflicts to mark.
# '
# matches '(?i-xsm:no conflicts)'
merging_newlines.......................ok
match..................................80/? passed.
match..................................1/? passed.
match..................................7/? passed.
missed_resolution......................ok
merging_newlines....................... passed.
Running harness.sh ... passed.
match..................................ok
mark-conflicts.........................ok
# Failed (TODO) test 'after a conflict, darcs resolve should report
a conflict'
# at merging_newlines.pl line 48.
# 'No conflicts to mark.
# '
# matches '(?i-xsm:no conflicts)'
merging_newlines.......................ok
match..................................69/? passed.
Running directory_confusion.sh ... passed.
Running diff.sh ... passed.
match..................................ok
mark-conflicts.........................ok
match..................................80/? passed.
match..................................94/? passed.
match..................................ok
mark-conflicts.........................ok
issue279............................... passed.
Running bad-match-pattern.sh ... passed.
Running bad-format.sh ... passed.
issue279...............................ok
issue184............................... passed.
issue184...............................ok
init................................... passed.
init...................................ok
get....................................ok
filepath...............................1/? passed.
filepath...............................5/? passed.
filepath...............................ok
external...............................1/? passed.
Running addexitval.sh ... passed.
Running add.sh ... passed.
All tests successful!
Done running tests on darcs-2 repositories...
external...............................ok
issue279...............................ok
issue184...............................ok
dist...................................1/?
init.................................dist...................................ok
init...................................ok
disable................................ok
get....................................ok
issue279...............................ok
issue184...............................ok
filepath...............................ok
init...................................ok
external...............................ok
dist................................... passed.
Running harness.sh ... passed.
get....................................ok
dist...................................ok
disable................................ok
filepath...............................ok
external...............................1/? passed.
external...............................ok
dist................................... passed.
Running diff.sh ... passed.
Running harness.sh ... passed.
dist...................................1/? passed.
dist...................................ok
disable................................ok
conflict-doppleganger..................33/?
changes_with_move...................changes_with_move......................ok
changes_send_context...................ok
changes_moved_files....................ok
changes................................9/? passed.
conflict-doppleganger..................42/? passed.
changes................................ok
binary................................. passed.
Running checkpoint.sh ... passed.
binary.................................ok
annotate............................... passed.
annotate...............................ok
conflict-doppleganger..................ok
amend-record...........................ok
changes_with_move......................ok
changes_send_context...................ok
changes_moved_files....................ok
changes................................ passed.
add_in_subdir..........................ok
add.................................... passed.
changes................................1/? passed.
Running checkpoint.sh ... passed.
changes................................9/?
# Failed (TODO) test 'add should fail on files it can't read
(because it would fail to record it later anyway).'
# at add.pl line 67.
# ''
# doesn't match '(?-xism:permission denied)'
add....................................ok
All tests successful.
Files=45, Tests=445, 742 wallclock secs ( 0.21 usr 0.18 sys + 11.66
cusr 18.85 csys = 30.90 CPU)
Result: PASS
Done running tests on hashed repositories...
changes................................ok
binary................................. passed.
binary.................................ok
annotate...............................ok
conflict-doppleganger..................44/? passed.
Running annotate.sh ... passed.
amend-record...........................ok
add_in_subdir..........................1/? passed.
conflict-doppleganger..................ok
changes_with_move...................... passed.
changes_with_move......................1/? passed.
changes_with_move......................3/? passed.
add_in_subdir..........................ok
changes_with_move......................ok
add....................................3/? passed.
changes_send_context...................ok
changes_moved_files....................1/?
# Failed (TODO) test 'add should fail on files it can't read
(because it would fail to record it later anyway).'
# at add.pl line 67.
# ''
# doesn't match '(?-xism:permission denied)'
add....................................ok
All tests successful.
Files=46, Tests=490, 746 wallclock secs ( 0.23 usr 0.18 sys + 12.39
cusr 20.11 csys = 32.91 CPU)
Result: PASS
Done running tests on old-fashioned repositories...
changes_moved_files....................ok
changes................................1/? passed.
Running addexitval.sh ... passed.
changes................................10/? passed.
Running annotate.sh ... passed.
All tests successful!
Done running tests on old-fashioned repositories...
passed.
changes................................ok
binary.................................ok
annotate...............................ok
amend-record...........................1/? passed.
amend-record...........................ok
add_in_subdir..........................1/? passed.
add_in_subdir..........................ok
add....................................1/? passed.
Running addexitval.sh ... passed.
Running add.sh ...
# Failed (TODO) test 'add should fail on files it can't read
(because it would fail to record it later anyway).'
# at add.pl line 67.
# ''
# doesn't match '(?-xism:permission denied)'
passed.
All tests successful!
Done running tests on hashed repositories...
add....................................ok
All tests successful.
Files=46, Tests=490, 753 wallclock secs ( 0.23 usr 0.18 sys + 12.70
cusr 20.05 csys = 33.16 CPU)
Result: PASS
Done running tests on darcs-2 repositories...
Test ran successfully.
_______________________________________________
darcs-devel mailing list
darcs-devel@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic