Clarify authors.

[vext01]

The main change is 3fbad79, then there's a commit to make the README overview better.

[ltratt]

I think we can be more inclusive here. Maybe something like "Yorick is developed by a team of people which can be seen in the ." I don't think we need a special mention.

[vext01]

Fixed in 12d05fc

[ltratt]

Please squash.

[vext01]

splat.

[ltratt]

bors r+

[bors]

Build failed:

• buildbot/ykrustc-buildbot-build-script-hwt

[vext01]

bors try

[bors]

try

Build failed:

• buildbot/ykrustc-buildbot-build-script-hwt

[ltratt]

cargo not being found is a bit odd! Let's try again.

bors r+

[bors]

Build failed:

• buildbot/ykrustc-buildbot-build-script-hwt

[vext01]

I wonder if the upstream sync broke it. Maybe cargo is installed in a different location or something. I'll look into it when I find a moment.

…

On Tue, 22 Dec 2020, 09:36 Laurence Tratt, ***@***.***> wrote: cargo not being found is a bit odd! Let's try again. bors r+ — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#206 (comment)>, or unsubscribe </~https://github.com/notifications/unsubscribe-auth/AAETWGYLMFGER6MKVYETMTLSWBSBTANCNFSM4VEJWGHA> .

[vext01]

Made a little progress with this. Something seems to have changed with x.py install such that the directory we tar up for the CI snapshot is bogus, and only contains:

$ find build/ykrustc-stage2-latest/
build/ykrustc-stage2-latest/
build/ykrustc-stage2-latest/libexec
build/ykrustc-stage2-latest/libexec/cargo-credential-1password
build/ykrustc-stage2-latest/VERSION

I also notice something wrong with the CI snapshot directory:

-rwxrwxr-x  1 buildbot-worker1 buildbot-workers 124643091 Dec 15 17:18 ykrustc-hw-stage2-1b4b37bf.tar.bz2
-rwxrwxr-x  1 buildbot-worker3 buildbot-workers 124650393 Dec 15 17:26 ykrustc-hw-stage2-5ccb675d.tar.bz2
-rwxrwxr-x  1 buildbot-worker4 buildbot-workers 124634002 Dec 15 17:23 ykrustc-hw-stage2-60d5035b.tar.bz2
-rwxrwxr-x  1 buildbot-worker4 buildbot-workers    298379 Dec 21 13:48 ykrustc-hw-stage2-92cb5763.tar.bz2
-rwxrwxr-x  1 buildbot-worker1 buildbot-workers 124638644 Dec 21 13:10 ykrustc-hw-stage2-b7178dda.tar.bz2
-rwxrwxr-x  1 buildbot-worker2 buildbot-workers 124786567 Dec 17 14:59 ykrustc-hw-stage2-ec7fe7f5.tar.bz2
lrwxrwxrwx  1 buildbot-worker4 buildbot-workers        61 Dec 21 13:48 ykrustc-hw-stage2-latest.tar.bz2 -> /opt/ykrustc-bin-snapshots/ykrustc-hw-stage2-92cb5763.tar.bz2
-rwxrwxr-x  1 buildbot-worker2 buildbot-workers 124668885 Dec 16 07:21 ykrustc--stage2-5ccb675d.tar.bz2
-rwxrwxr-x  1 buildbot-worker3 buildbot-workers    298217 Dec 23 07:21 ykrustc--stage2-92cb5763.tar.bz2
lrwxrwxrwx  1 buildbot-worker3 buildbot-workers        59 Dec 23 07:21 ykrustc--stage2-latest.tar.bz2 -> /opt/ykrustc-bin-snapshots/ykrustc--stage2-92cb5763.tar.bz2

My guess there is that the removal of STD_TRACER_MODE wasn't done quite right.

Out of time for now :)

[ltratt]

Aha, OK!

[vext01]

I've been slowly investigating this. It seems the installer is currently in flux, and this is likely the source of our problems: https://rust-lang.zulipchat.com/#narrow/stream/182449-t-compiler.2Fhelp/topic/.60x.2Epy.20install.60.20broken.3F

[ltratt]

It looks like there's a PR fix up now? rust-lang/rust#80514

[vext01]

Once that's merged, I'll sync upstream and hopefully it will fix our issues. We actually saw a different problem, but I'm hoping it's related. I'm also going to add CI steps that check that certain binaries exist in the install dir, like cargo and rustc. Then we can catch this kind of thing earlier next time.

…

On Wed, 30 Dec 2020, 19:11 Laurence Tratt, ***@***.***> wrote: It looks like there's a PR fix up now? rust-lang/rust#80514 <rust-lang/rust#80514> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#206 (comment)>, or unsubscribe </~https://github.com/notifications/unsubscribe-auth/AAETWG7MNCOIGIQJKIHHJV3SXN3NLANCNFSM4VEJWGHA> .

[ltratt]

I've checked and rust-lang/rust#80514 has been merged into rust's master branch, even though the PR is still open. So I think we're good to go!

[vext01]

Using this morning's upstream master, x.py install no longer fails, but it doesn't actually put anything in the install dir.

[ltratt]

Ye gods :/

[vext01]

bors try

[bors]

try

Build succeeded:

• buildbot/ykrustc-buildbot-build-script-hwt

[vext01]

@ltratt this is good to go.

[ltratt]

Do you want/need to rebase against master?

[vext01]

It's already up to date, so we can go ahead.

[ltratt]

bors r+

[bors]

Build succeeded:

• buildbot/ykrustc-buildbot-build-script-hwt