Opened 7 years ago
Closed 7 years ago
#14010 closed bug (fixed)
buildbot build broken
Reported by: | korli | Owned by: | haiku-sysadmin |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Sys-Admin | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
It seems the usual Haiku build tasks now try to build the buildtools, which is unexpected:
../haiku/configure -j2 --build-cross-tools x86_64 ../buildtools in dir /home/builder/builds/haiku-repository-x86_64/../cross-tools-x86_64
To compare with https://buildbot.haiku-os.org/builders/haiku-repository-x86_64/builds/3903 there is a new task at step 2.
Change History (4)
comment:1 by , 7 years ago
Description: | modified (diff) |
---|
comment:2 by , 7 years ago
comment:3 by , 7 years ago
aww yup. buildbot squats and watches those scripts for modifications and removes the binaries when messed with.
factory.addStep( ShellCommand( command = dedent(""" if ! cmp -s ../haiku/build/scripts/%(script)s \ ../trigger-files/%(haikuBranch)s/%(script)s; then rm -f ../cross-tools-*/cross-tools-*/bin/* mkdir -p ../trigger-files/%(haikuBranch)s cp ../haiku/build/scripts/%(script)s \ ../trigger-files/%(haikuBranch)s/ fi """[1:]) % { 'haikuBranch' : haikuBranch, 'script' : script, }, description = ['check', script], name = 'check ' + script, workdir = Property('builddir'), hideStepIf = True))
hrev51825 should indeed work around the issue. I wonder if that buildbot logic should be removing the whole cross-tools-XXX directory and not just the bins?
comment:4 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
this was fixed per hrev51825. There was an additional issue of baron being full. I just fixed that as well.
We need some code to cleanup nightly images on maui when we go live with it. (maybe keep even builds only after XX days or something)
I double checked the buildbot config, and nothing has changed recently.
Noticed the logic here was slightly flawed:
It's a simple directory check to see if the toolchain is there. I improved it in hrev51825 to check for the directory, and for a compiler binary.
Lets see if that kicks things back. Nothing has changed recently, the thing that triggered the issue seems to be touching the build-cross-tools-gcc4 script.