[Buildbot-commits] [buildbot/buildbot] 166d0d: use uname, if possible, on slaves, to avoid socket...

noreply at github.com noreply at github.com
Sun Nov 27 17:52:43 UTC 2011


  Branch: refs/heads/master
  Home:   https://github.com/buildbot/buildbot

  Commit: 166d0de13ca38643b69ca2140c00f5981ba0d9d9
      https://github.com/buildbot/buildbot/commit/166d0de13ca38643b69ca2140c00f5981ba0d9d9
  Author: Dustin J. Mitchell <dustin at mozilla.com>
  Date:   2011-11-26 (Sat, 26 Nov 2011)

  Changed paths:
    M slave/buildslave/bot.py
  M slave/buildslave/test/unit/test_bot_BuildSlave.py

  Log Message:
  -----------
  use uname, if possible, on slaves, to avoid socket.getfqdn hangs


  Commit: 7fb2bf75dcd3316245f7d2a085dae39e13677516
      https://github.com/buildbot/buildbot/commit/7fb2bf75dcd3316245f7d2a085dae39e13677516
  Author: Dustin J. Mitchell <dustin at mozilla.com>
  Date:   2011-11-27 (Sun, 27 Nov 2011)

  Changed paths:
    A master/buildbot/db/migrate/versions/015_remove_bad_master_objectid.py
  M master/buildbot/master.py
  M master/buildbot/test/integration/test_upgrade.py
  A master/buildbot/test/unit/test_db_migrate_versions_015_remove_bad_master_objectid.py
  M master/buildbot/test/unit/test_master.py
  A master/buildbot/test/util/migration.py
  M master/docs/developer/database.rst

  Log Message:
  -----------
  Fix master state tracking.

In the previous version, the master tracked its last_processed_change
using a name/class of 'master'/'buildbot.master.BuildMaster', but
tracked build requests using the master name with class 'BuildMaster'.

The migration script given here combines these two objects into one,
discarding the last_processed_change value if it is ambiguous which
master owns it.  In the end, the object name is the master name, and the
class is 'buildbot.master.BuildMaster'.

This also adds a framework for unit-testing migration scripts, and uses
it.


Compare: https://github.com/buildbot/buildbot/compare/a15f765...7fb2bf7




More information about the Commits mailing list