[tahoe-dev] Help adjusting buildbot after upgrade?

[Zooko O'Whielacronx]

On Wed, Nov 10, 2010 at 12:04 AM, Kyle Markley <kyle at arbyte.us> wrote:
> Zooko et al,
>
> My system is back up after upgrading the OS from OpenBSD 4.6 to 4.8.  I've
> more-or-less gotten the buildslaves running again, but I could use some help
> there.
>
> (A) My buildslave name contains 'openbsd46'; I feel like this should be
> updated, but I'm nervous about breaking something.  How is this done
> correctly?

Buildmaster and buildslave have to change the name simultaneously.
I'll go change it from "starfish-openbsd46-amd64" to just "starfish"
in the buildmaster's config file, and the next time you make the same
change (in the buildbot.tac file) and restart then it will reconnect.

> (B) There are some errors running the build and I suspect they're related to
> installation snafus and missing packages.  I'd appreciate some guidance here
> on what exactly is wrong.

What errors? This is all green:

http://tahoe-lafs.org/buildbot/builders/Kyle%20OpenBSD-4.6%20amd64/builds/480

(Note that link will probably break when we rename the buildslave. Oh well.)

> It's worth mentioning that I had a "fun" upgrade.  I made a mistake and
> inadvertently blew away my /home partition.  (I naively thought that telling
> the installer which partition would become /home did *not* imply that I
> wanted the partition to be formatted during the install!)  I'm restoring my
> data from a tahoe backup right now, courtesy the undamaged portion of my
> grid.

Hooray for backups! (Did the backup succeed?)

> The only thing really bothering me right now is tahoe's behavior with
> symlinks.  It skips them.  I didn't have any kind of separate symlink
> backup, so I've lost them all.  That's a drag, because I had some pretty
> labor-intensive piles of symlinks.  I wish tahoe would cover symlinks by
> recording the link (not the file pointed to) instead of skipping it.

Brian replied to this and linked to the relevant issue ticket.

> Also, as an FYI, when doing a fresh install of tahoe (1.8.0) on this
> otherwise-clean system, I noticed that "python setup.py install" installed
> only tahoe itself.  It did not install any dependencies, and it did not fail
> because the dependencies were absent.  I had to install all of the
> dependencies manually.  Of course "python setup.py build" fetched and built
> the dependencies, but I couldn't figure out how to install them from the
> source tree to /usr/local/lib.  When I first started tinkering with tahoe a
> few versions ago, the install would also ensure the dependencies were
> installed.  If this is all fixed in 1.8.1, ignore this complaint.

Please open a ticket for this!

To test this we'll probably have to have the buildbot do something like

python setup.py install --prefix=test-full-inst-dir

and then our build system passes the test only if the following
command emits the right output: cd test-full-instdir && ./bin/tahoe
--version-and-path

Does that sound like an accurate test for your desired feature?

Regards,

Zooko