Closed Bug 769897 Opened 12 years ago Closed 12 years ago

Win32 Builders have wrong basedir set for buildbot.tac

Categories

(SeaMonkey :: Release Engineering, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: Callek)

References

Details

So, I was trying to figure out why our SeaMonkey 2.11b4 windows builds were messing up. (Specifically trying to grab a mozconfig, and failing to |cat| it, and then on closer inspection, we were actually building thunderbird :/

I noticed the difference between this and the previously successful beta build, and it was in the "in dir" path, which is also the "basedir" as specified in buildbot.tac

What we had before:

basedir = r'/builds/slave'

which is obviously what we had on a linux slave.

What I changed it to:

basedir = 'e:\\builds\\slave'

I did this change on all our win32 slaves right now, with one exception sea-vm-win32-1, which I can't seem to RDP into, if it doesn't come up soon will file an IT bug on that.
vm-1 is done too.

I'm surprised we didn't hit this before (and we are lucky that we didn't hit this before)

BTW: Fallen, I CC'ed you as a warning incase your windows buildbot.tac has a unix basedir rather than the win-style one.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Thanks, I checked and luckily we already had a windows-style directory.
You need to log in before you can comment on or make changes to this bug.