NSS Tinderbox Admin

This page contains documentation regarding the administration of the build slave machines listed at:

• http://tinderbox.mozilla.org/showbuilds.cgi?tree=NSS
• http://tinderbox.mozilla.org/showbuilds.cgi?tree=NSS-Stable-Branch

In order for the tests to work, we rely on the global Mozilla.org provided machine tinderbox.mozilla.org.

Make sure you understand the virtual terminal software "screen" used on Linux and OSX. The essential commands are:

• "screen -ls" to see if you have a running session
• "screen -r" to attach to a running session
• "screen" to start a new detachable session
• press "CTRL-A CTRL-D" to detch from a running session (you can disconnect from ssh afterwards, and your session will continue to run in the background)

Sometimes on Windows machines, the tests get stuck. We don't understand yet why. The only known remedy is to stop the scripts and restart. When doing so, please make sure that all background NSS server processes named "selfserv" and "httpserv" have been stopped (killed).

Mozilla data center

• nss-vm-centos6-1
  • nss-vm-centos6-1.community.scl3.mozilla.com
  • ssh (22)
  • user: niscc for scheduled NISCC tests
    • see "crontab -l" which executes /home/niscc/run/run
  • user: nssleak for continous leak testing
    • manual startup in "screen"
    • cd mozilla/security/tinderlight
    • sh run

• nss-vm-darwin10-1
  • nss-vm-darwin10-1.community.scl3.mozilla.com
  • ssh (22)
  • vnc (5900)
  • user: tinderbox
    • use ssh and manual startup in "screen"
    • cd mozilla/security/tinderlight
    • sh run

• nss-vm-darwin9-1
  • nss-vm-darwin9-1.community.scl3.mozilla.com
  • ssh (22)
  • vnc (5900)
  • user: tinderbox
    • use ssh and manual startup in "screen"
    • cd mozilla/security/tinderlight
    • ./run

• nss-vm-win32-1
  • nss-vm-win32-1.community.scl3.mozilla.com
  • rdesktop (3389)
  • user: tinderbox
  • see desktop file "readme start nss", which says:
    • use desktop icon start-msvc8
    • cd /e/mozilla/security/tinderlight
    • ./run

Red Hat data center

Name of the machines that hosts all the individual test VMs:

• nsstbox.idm.lab.bos.redhat.com

Test VMs:

• nsstestsrv
  • nsstestsrv.usersys.redhat.com
  • ssh
  • user: niscc for scheduled NISCC tests
    • see "crontab -l" which executes /home/niscc/run/run
  • user: nssleak for continous leak testing
    • manual startup in "screen"
    • cd mozilla/security/tinderlight
    • sh run

• buildnss01
  • buildnss01.idm.lab.bos.redhat.com
  • ssh
  • user: tinderbox
    • login as root
    • user "service tinderbox start" or stop

• buildnss02
  • buildnss02.usersys.redhat.com
  • ssh
  • user: tinderbox
    • use ssh and manual startup in "screen"
    • cd mozilla/security/tinderlight
    • sh run

• buildnss03
  • buildnss03.idm.lab.bos.redhat.com
  • rdesktop

• buildnss04
  • buildnss04.idm.lab.bos.redhat.com
  • ssh
  • user: tinderbox
    • use ssh and manual startup in "screen"
    • cd mozilla/security/tinderlight
    • sh runboth

• buildnss05
  • 10.16.79.162
  • rdesktop
  • user: administrator
    • start desktop shortcut "msvc10 64bit"
    • cd /c/mozilla-build/msys/tinderbox/tinderlight
    • sh run64

osuosl.org

• chinook
  • chinook.fedora.osuosl.org
  • ssh (22)
  • user: kaie
    • manual startup in "screen"
    • cd mozilla/security/tinderlight
    • sh run

at home

• macmini-powerpc

general information

In order to configure a new computer to join the NSS build+test pool, please refer to the instructions at:

• https://wiki.mozilla.org/NSS:LinuxTinderbox
• https://wiki.mozilla.org/NSS:WindowsTinderbox
• https://wiki.mozilla.org/NSS:MacOSXTinderbox

We run a special NISCC test suite (a kind of SSL/TLS and S/MIME protocol fuzzing), see

• https://wiki.mozilla.org/NSS:LinuxNisccTesting

Our tests depend on a globally accessible OCSP server, see

• https://wiki.mozilla.org/NSS:TestSuiteOCSPServer