[INFO] cloning repository https://github.com/MinersP/blog_os
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/MinersP/blog_os" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FMinersP%2Fblog_os", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FMinersP%2Fblog_os'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] a70f3af1c2da98debcb12dca79ecd78cbe2a66ce
[INFO] checking MinersP/blog_os against master#9f48dedc9763334a587c66558974635807a113ed for pr-137394
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FMinersP%2Fblog_os" "/workspace/builds/worker-1-tc1/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-1-tc1/source'...
[INFO] [stderr] done.
[INFO] validating manifest of git repo https://github.com/MinersP/blog_os on toolchain 9f48dedc9763334a587c66558974635807a113ed
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9f48dedc9763334a587c66558974635807a113ed" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking git repo https://github.com/MinersP/blog_os
[INFO] finished tweaking git repo https://github.com/MinersP/blog_os
[INFO] tweaked toml for git repo https://github.com/MinersP/blog_os written to /workspace/builds/worker-1-tc1/source/Cargo.toml
[INFO] crate git repo https://github.com/MinersP/blog_os already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+9f48dedc9763334a587c66558974635807a113ed" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded volatile v0.2.5
[INFO] [stderr]   Downloaded font8x8 v0.2.4
[INFO] [stderr]   Downloaded array-init v0.0.3
[INFO] [stderr]   Downloaded uart_16550 v0.1.0
[INFO] [stderr]   Downloaded skeptic v0.5.0
[INFO] [stderr]   Downloaded fixedvec v0.2.3
[INFO] [stderr]   Downloaded bootloader v0.3.11
[INFO] [stderr] error: failed to parse manifest at `/workspace/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/bootloader-0.3.11/Cargo.toml`
[INFO] [stderr] 
[INFO] [stderr] Caused by:
[INFO] [stderr]   the cargo feature `publish-lockfile` has been removed in the 1.37 release
[INFO] [stderr] 
[INFO] [stderr]   This package cannot be used with this version of Cargo, as the unstable feature `publish-lockfile` is no longer supported.
[INFO] [stderr]   See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#publish-lockfile for more information about using this feature.


command failed: exit status: 101

    Blocking waiting for file lock on package cache
    Updating crates.io index
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
 Downloading crates ...
  Downloaded volatile v0.2.5
  Downloaded font8x8 v0.2.4
  Downloaded array-init v0.0.3
  Downloaded uart_16550 v0.1.0
  Downloaded skeptic v0.5.0
  Downloaded fixedvec v0.2.3
  Downloaded bootloader v0.3.11
error: failed to parse manifest at `/workspace/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/bootloader-0.3.11/Cargo.toml`

Caused by:
  the cargo feature `publish-lockfile` has been removed in the 1.37 release

  This package cannot be used with this version of Cargo, as the unstable feature `publish-lockfile` is no longer supported.
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#publish-lockfile for more information about using this feature.