BitKeeper comes with an extensive regressions suite and new changes should be validated against those tests and the tests should be extended for any new code.
The regressions make some assumptions about the machine where they are run. This guide explains how to configure your machine. We are trying to remove some of these requirements so this document will get updated in the future.
Some tests assume Bitkeeper is installed on the current machine in the current user’s PATH.
Work from a BitKeeper repository
The regressions assume they are running from the official BitKeeper repository and do not work correctly when run from an unpacked tarball or a git clone. So do something like this:
bk clone bk://bkbits.net/u/bk/dev dev cd dev/src
Create a /build
The regressions expect a
/build filesystem that is writable by anyone. A simple way to create this is:
mkdir /tmp/build sudo chmod 1777 /tmp/build sudo ln -s /tmp/build /build
(This may not be necessary, need to test that)
Need a full hostname
Your machine needs to have a full domain name that BitKeeper knows about.
bk gethost -r needs to return a domain name that resolves to the current machine.
An easy way to do this on most machines is to edit
/etc/hosts to add a domain:
127.0.0.1 localhost 127.0.1.1 vm1 vm1.example.com
SSH connections to the localhost need to work
The code expects that
ssh localhost date and
ssh HOST date both work without prompting for a password. Usually, that can be fixed by running:
Run regressions like this:
cd src make -j p cd t make -j6 -k ls output/BAD.t.*