<LnL>
gchristensen pulled the community builders recently IIRC
<LnL>
also he's probably still on a plane right now
<nh2>
LnL: what does pulled mean in this context, disabled them or merged some functionality from a PR?
<LnL>
disabled, all linux builds should be running on infrastructure machines now
<MichaelRaskin>
I think there was an idea of maaaybe reinstanting community builders with fixed-output derivations only built on infrastructure builders (and substituted on the community ones)
<nh2>
LnL: doesn't that make "running your own builder" essentially obsolete? My plan was to add my own builder to help with building large packages that time out after 1 hour
<LnL>
for the moment yes, but being able to contribute cpu cycles for trusted builds would still be really nice
<nh2>
LnL: so right now I can't do that and have to wait, right?
<MichaelRaskin>
And I think filtering to make use of larger timeout would also need extra code
<LnL>
yeah the builder currently decides the timeout
<nh2>
MichaelRaskin: it looks like I can set that for my builder with `build_timeout_seconds`, so I could just set it very high
<MichaelRaskin>
Yes; the problem is that you still won't be preferred for Chromium PRs
<nh2>
MichaelRaskin: ah, you mean filtering to do a better assignment of which builder does what. I see
<nh2>
another issue I encountered: ofborg master doesn't compile for me:
<nh2>
in src/easyamqp.rs:311:19, in `let session = try!(amqp::Session::new(options));`
<nh2>
error: use of deprecated item 'try': use the `?` operator instead
<LnL>
ofborg currently doesn't know the drv count when building so the timeouts are mostly in place to avoid building "too much"
<LnL>
that's odd, try nix-build release.nix -A ofborg.rs.x86_64-linux
<nh2>
LnL: that builds, is it possible that the dependencies aren't pinned correctly for the `cargo build` in nix-shell as shown in the readme?
<MichaelRaskin>
Maybe wrong default edition or something like that?
<LnL>
I generally use my direnv alias with the latest rust instead, but the shell expression is also pinned and worked fine last time I used it