-
Notifications
You must be signed in to change notification settings - Fork 4
Conversation
.buildbot.sh
Outdated
@@ -27,7 +28,12 @@ ulimit -d $((1024 * 1024 * 10)) # 10 GiB | |||
|
|||
# Build extended tools and install into TARBALL_TOPDIR. | |||
mkdir -p ${TARBALL_TOPDIR} | |||
/usr/bin/time -v ./x.py install --config .buildbot.config.toml | |||
# We should be able to do this, but `x.py install` is broken. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does "this" refer to here? [I eventually guessed, but it's a bit ambiguous.]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The following commented line. We can add some whitespace to make it more obvious?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'll still be ambiguous I suspect: I think the comment needs rephrasing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Give 5057cab a go.
.buildbot.sh
Outdated
@@ -28,7 +28,7 @@ ulimit -d $((1024 * 1024 * 10)) # 10 GiB | |||
|
|||
# Build extended tools and install into TARBALL_TOPDIR. | |||
mkdir -p ${TARBALL_TOPDIR} | |||
# We should be able to do this, but `x.py install` is broken. | |||
# `x.py install` currently broken, so we use a workaround for now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"is currently"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed. Fixed.
Please squash. |
This gets us going, but installs too many intermediate libraries. Once upstream fixes `x.py install` we should revert to using it.
Splat. |
Hold on a minute. I think there's a bug in the second commit. |
Sorry, that's rubbish, please carry on :) |
bors r+ |
Build succeeded: |
Upstream has fixed `x.py install` so we can go back to using it.
x.py install
seems to be broken at the moment and this in turn broke our CI. This branch proposes a workaround.The first commit is the best "easy" fix I can come up with. I'd like this to be a temporary workaround, as it's not optimal: copying the stage 2 dir copies a lot more stuff than you'd find in a typical sysroot. We could try and remove the bits we don't need, but it's difficult to know what, and we'd have to keep it in sync with upstream. I'm hoping upstream will fix
x.py
install soon...Tested on ykjit/yk#206. And here is the forced build log.
The second commit allows us to run
.buildbot.sh
in scenarios where there isn't necessarily a bors merge commit on the top of the branch (i.e. during a manual or forced build). I needed this to test my changes and it seems generally useful.