Intermittent build failures should be gone on OSX

(Johan Lorenzo) #1

@julienw and I worked on making the build more stable on OSX. With the latest landings on master, you should be in a more stable state. A couple of actions you might need to do:

1. Install pkg-config

If you encounter:

Panicked at 'called `Result::unwrap()` on an `Err` value: Command { command: "\"pkg-config\" \"--libs\" \"--cflags\" \"libupnp\"", cause: Error { repr: Os { code: 2, message: "No such file or directory" } } }', ../src/libcore/
note: Run with `RUST_BACKTRACE=1` for a backtrace.

You have to install the pkg-config binary. See the packages to install at the bottom of the package table.

2. Use new exported env variables

Instructions here

The openssl intermittent failure was due to sqlite exposing /usr/lib as a custom library path (aka “-L /usr/lib”). The order of -L params was what caused the intemittent-cy. (it changed from a cargo build to another). As a workaround and until the root cause is fixed, if we use the brew version of sqlite, the problem goes away.

3. Edit .cargo/config

.cargo/config was removed from git in favor or defining the rule in Cargo.toml. If you added some other rules in there, you might need to update that file. In any case, changes in .cargo won’t be added to git anymore.

What next?

We haven’t noticed any build intermittents since then. But if you do or if you have some troubles, please drop us a message in this thread.

1 Like

(Michiel de Jong) #2

Awesome, I can finally build master again! \o/


(Johan Lorenzo) #3

A new intermittent failure popped on Travis: Even though every step passed, the job failed for no reason (apparent in the logs).

A fix is on its way at: