Tracking issue: running crater locally

[aidanhs]

We would like people interested in crater to be able to clone and run a series of commands to be able to get a quick taste of the full crater process.

Known papercuts/issues here include:

• Building the docker container takes longer than the timeout, so fails. #71 - building the docker image for the first time takes a while, so the prepare-local command fails due to a timeout imposed on the command (prepare-local possibly shouldn't have a timeout at all). Suggested workaround is to cd docker && docker build ., so the image is built by the time you try and run prepare-local.
• demo list is not working #38 - the 'demo' set of crates doesn't work, so prepare-local will fail.

These are just the known issues so far.

[aidanhs]

rust-lang/rustup#618 (comment) - rustup issue that seems to make it impossible for crater to install its own rustup if you have a version installed in the default location.

Edit: I was wrong, just a bad error message from rustup

[aidanhs]

The README now suggests for people to use a 'mini' docker environment when testing locally, so I think this is done for now!

[alkis]

I tried this on windows but crater binary fails to compile with:

   Compiling crater v0.1.0 (file:///C:/Users/alkis/Projects/crater)
error[E0433]: failed to resolve. Use of undeclared type or module `kernel32`
   --> src\run.rs:165:26
    |
165 |             let handle = kernel32::OpenProcess(winapi::winnt::PROCESS_TERMINATE, 0, id);
    |                          ^^^^^^^^ Use of undeclared type or module `kernel32`

error[E0433]: failed to resolve. Use of undeclared type or module `winapi`
   --> src\run.rs:165:48
    |
165 |             let handle = kernel32::OpenProcess(winapi::winnt::PROCESS_TERMINATE, 0, id);
    |                                                ^^^^^^ Use of undeclared type or module `winapi`

error[E0433]: failed to resolve. Use of undeclared type or module `kernel32`
   --> src\run.rs:166:13
    |
166 |             kernel32::TerminateProcess(handle, 101);
    |             ^^^^^^^^ Use of undeclared type or module `kernel32`

error[E0433]: failed to resolve. Use of undeclared type or module `kernel32`
   --> src\run.rs:167:16
    |
167 |             if kernel32::CloseHandle(handle) == 0 {
    |                ^^^^^^^^ Use of undeclared type or module `kernel32`

error: unused extern crate
  --> src\lib.rs:14:1
   |
14 | extern crate libc;
   | ^^^^^^^^^^^^^^^^^^
   |
note: lint level defined here
  --> src\lib.rs:1:9
   |
1  | #![deny(unused_extern_crates)]
   |         ^^^^^^^^^^^^^^^^^^^^

error: aborting due to 5 previous errors

error: Could not compile `crater`.

Is crater not expected to work on windows?

[aidanhs]

Unfortunately crater does not yet work on Windows. This is absolutely a problem and something we need to fix at some point, but we've just not had a chance to get to it yet!

[alkis]

This is unfortunate. FWIW the README claims that it should work on windows :-)

In any case, do you have any idea how far away this is from working on windows? What is missing?

[aidanhs]

Yeah, the readme needs attention since I don't think that's ever been the case! I'll jot down some thoughts on #149 about Windows support.