(From our-ref D130681.)
martind@swiftboat:~/tmp/D130647$ bk cp /home/martind/work/misc/tools/scripts/mean /home/martind/work/misc/tools/scripts/variance bk: fslayer.c:504: fslayer_utime: Assertion `0' failed. Aborted (core dumped) martind@swiftboat:~/tmp/D130647$ (gdb) bt #0 0xf76e1d70 in __kernel_vsyscall () #1 0xf7538367 in raise () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #2 0xf7539a23 in abort () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #3 0xf75316c7 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #4 0xf7531777 in __assert_fail () from /lib/i386-linux-gnu/i686/cmov/libc.so.6 #5 0x080b9d0c in fslayer_utime (path=0x92de8b0 "/home/martind/work/misc/tools/scripts/SCCS/s.variance", buf=0xff8edb14) at fslayer.c:504 #6 0x08145d1f in sccs_setStime (s=0x92cce50, newest=0) at slib.c:1182 #7 0x08150fcc in sccs_finishWrite (s=0x92cce50) at slib.c:2413 #8 0x08168072 in sccs_admin (sc=0x92cce50, p=0, flags=8, f=0x0, z=0x0, u=0x0, s=0x0, mode=0x0, text=0x0) at slib.c:12589 #9 0x081682e2 in sccs_adminFlag (sc=0x92cce50, flags=8) at slib.c:12222 #10 0x0816830a in sccs_newchksum (s=0x92cce50) at slib.c:12162 #11 0x0809620d in cp (quiet=, force=, to=0xff8f4839 "/home/martind/work/misc/tools/scripts/variance", from=0xff8f480e "/home/martind/work/misc/tools/scripts/mean") at cp.c:140 #12 cp_main (ac=3, av=0xff8f2554) at cp.c:45 #13 0x0804dd3d in cmd_run (av=, ac=, is_bk=, prog=0xff8f480b "cp") at bk.c:982 #14 main (ac=-1983893163, av=0xff8f2554, env=0xff8f2568) at bk.c:741 (gdb) Oh dear, that's left me with some detritus: martind@swiftboat:~/work/misc$ bk -r check -ac =============================================================================== check: tools/scripts/variance has pending deltas but no d.file, repairing. =============================================================================== martind@swiftboat:~/work/misc$ bk -r check -ac martind@swiftboat:~/work/misc$ bk sfiles -p tools/scripts/SCCS/s.variance martind@swiftboat:~/work/misc$
I was running bk-7.3.1ce+hnas0 at the time of the original occurrence. Lazily, I haven’t checked that it still happens with 7.3.2. The problem was reproducible but, and I imagine this is the key, it didn’t happen if my current directory was ~/work/misc, ie in the repo tree. That gave me an obvious and easy work-around, so this wasn’t even really an inconvenience. Nor was it a regression, in that the assertion failure happened with the commercial bk too (7.1), though that didn’t leave me with a repository that needed mending. My searches found no match for the rock and roll legend fslayer_utime.