Matthew Flatt

Ah — that URL and the log looks like what we'd call a regular Racket build, instead of a minimal Racket build (which is more minimal). Building from non-minimal sources...

When you build from the minimal Racket source and finish with ``` raco pkg update --auto racket-lib ``` as described in `racket/src/README.txt`, that gets an initial set of libraries: libssl,...

Currently, `.desktop` file creation is specifically skipped in tethering mode. After refreshing my memory on how this all works, it looks like the consistent approach would be to add `'addon-tethered-app-dir`...

That idea seems to work out, at least in my experiments so far. I've pushed the change, partly with the idea that a round of snapshots will make it easier...

Many of the test failures appear to be due to a contract check added in racket/rackunit#158.

I'm not sure sure about this one. I see how it lets dotted calls turn into method calls with less in between, but there are some small issues, at least....

Ok if we keep this open, though? That will make the experiment easier to find until we sort out everything.

It's a strange workaround, but FWIW, I think moving the `racket` the next line also avoids the problem.

I think the problem here is that the test is broken. The test is meant to call `compute-size-increments` with only a single thread active, but it's possible that a sleep...

The diff in that output is showing only `Expected error` lines. Also, the direction of the diff is `>`, which means lines in the second argument to `diff` that are...