1539
Comment: oops :)
|
← Revision 4 as of 2009-12-14 11:34:32 ⇥
1539
|
Deletions are marked like this. | Additions are marked like this. |
Line 6: | Line 6: |
triton # screen }}} | pallas # screen }}} |
Line 11: | Line 11: |
triton # for node in galaxy1 galaxy2 ... ; do screen -t $node ssh $node ; done }}} | pallas # for node in galaxy1 galaxy2 ... ; do screen -t $node ssh $node ; done }}} |
Line 16: | Line 16: |
triton # for node in galaxy1 galaxy2 ... ; do screen -t $node-worker ssh $node /path/to/test-script ; done }}} | pallas # for node in galaxy1 galaxy2 ... ; do screen -t $node-worker ssh $node /path/to/test-script ; done }}} |
Contents
Farm node access
Use screen
pallas # screen
Open safe shells
From within screen
pallas # for node in galaxy1 galaxy2 ... ; do screen -t $node ssh $node ; done
Launch test processes
From within screen
pallas # for node in galaxy1 galaxy2 ... ; do screen -t $node-worker ssh $node /path/to/test-script ; done
Switch to nodes
In screen, enter C-a "
Then select the desired shell from the list.
Bisecting OpenAFS
Do this with a git clone. Really!
Creating the repository
In my case:
% git clone http://openafs-git.stanford.edu/openafs-test-20090528.git % cd openafs-test-20090528 % ./regen.sh
Starting the bisection
% git git bisect start openafs-stable-1_4_10 openafs-stable-1_4_8
Work cycle
Compile the current state (preferably from a build host, with repo in AFS)
% mkdir `sys` && cd `sys` && ../configure ... && make
(It can also make sense to build somewhere else entirely, filesystem-wise. Use absolute path to configure then.)
Install and test. If the bug is not yet observed:
% git bisect good
And if it is:
% git bisect bad
- Configure again, as Makefile.in may have changed here or there...
Troubleshooting
If an intermediate revision won't build or work, you can
Try and fix it. Be sure to
% git reset --hard
before the next git bisect step.
- - or -
Try followup commits:
% git bisect skip