On Thu, Dec 26, 2019 at 12:04 PM Daniel Shahaf <d...@daniel.shahaf.name> wrote: > > Here are the contents of fails.log.svn-check-svn-bdb -- could be some > > kind of fluke? I just started another full test run. Let's see if it > > repeats: > > It's _possible_ that some dependency upgrade introduced a heisenbug, but > Occam's razor says it's more likely to be something in your setup. I guess > svn-test-work is on a ramdisk, so it could be its mount options.
Hmmm. I reran the tests (same sources, with r1866425-rework-patch applied). This time all the tests passed, including autoprop_tests.py #7 for svnserve x bdb. Both times, I ran everything under a ramdrive, which is mounted with rw,relatime: $ cat /proc/mounts | grep ramdrive /dev/sdb1 /home/nate/ramdrive ext4 rw,relatime 0 0 (If you're wondering about /dev/sdb1, it appears to be a regular disk, not a ramdrive, because this is a virtual machine and the ramdrive is a disk image in RAM on the host. This allows it to persist through reboots of the guest, moved to other guests, etc). I don't know why the test failed before. Could be timing or something else happening on the computer? As I continue experimenting, we'll see if it fails again... I'll keep everyone posted. Also, I'll try the default-jdk-headless and junit4 packages and let you know how that works out... Thanks for your help... Nathan
