​​Rust All Hands 2018 - What can Infra do for you?
​​One reason Infra exists is to support the rest of the Rust project. So - what needs doing?
​​
​​For example:
  • ​​crater exists to help the language, compiler and library teams make decisions about possible breaking changes
  • ​​perf.rust-lang.org exists to help the compiler team identify performance issues in the compiler
  • ​​the tagging/assignment features of bors and highfive exist to help the release team manage the github issue tracker
  • ​​crates.io is somewhat unique among the services the Infra team has responsibility for, in that it exists as a public service to all users of Rust

​​We are interested in hearing

​​Realistic ideas

​​(possibly implemented as suggested)
  • ​​“I have a github bot I want to be hosted somewhere”
  • ​​“There is a de-facto standard Rust service hosted somewhere that I would like to be hosted by Infra”

​​Wild ideas

​​(possibly used as inspiration)
  • ​​“I want this list of 50 embedded devices hooked up to a machine somewhere on the internet so CI can run things on them”
  • ​​“I want a public compilation cache of the top 500 crates for the last three stable releases”
  • ​​“I want to visit ci-my-machine.rust-lang.org and it downloads some wasm to allow the Rust CI to use my machine to parallelise builds”
  • ​​“I’d like to run CI for my non-tier-1 platform on hardware I can provide”
​​

​​Wishlists

​​Niko (as Niko)

  • ​​I may not be able to attend meeting, but wanted to leave a note with the things I care about (probably no surprises here):
  • ​​I really, really want the ability to measure the perf of a PR without bothering simulacrum
  • ​​crater on windows
  • ​​able to add custom crates to crater (e.g., Github URLs)
  • ​​is possible!
  • ​​insight into the crater / perf queues (similar to bors queue)

​​nrc

  • ​​As nrc
  • ​​As tools team member and tools maintainer
  • ​​Have infra team host docs.rs
  • ​​For a tools submodule merge, use compiler artifacts from previous build (see extreme bors planning) to speed up updates
  • ​​Get notifications in advance if a PR would break a tool
  • ​​Maybe have a bot post a gentle notification that a PR may break a tool and that the developer
  • ​​Bot to auto create PRs to update tools

​​spacekookie (as a developer in the community)

  • ​​Mac machines on travis take a long time (6-8 hours) to be provisioned for testing (for the wider community)

​​TimNN (as someone interested in iOS targets)

  • ​​Check that we compile and link iOS targets, we don’t currently do enough of this on CI

​​pnkfelix (as compiler team member)

  • ​​Crater takes too long to run
  • ​​We may be able to speed up some builds via cargo check instead of build/test
  • ​​CI testing for NLL (and maybe other long-running unstable features)
  • ​​i.e., just run-pass, then more as we make progress
  • ​​Just needs to be on “easy” target(s) (linux)