Visitar URL original
sccache consistently errors on CI since Rust nightly-2019-11-07 · Issue #24714 · servo/servo · GitHub
Skip to content

sccache consistently errors on CI since Rust nightly-2019-11-07 #24714

Closed

Description

@SimonSapin

https://community-tc.services.mozilla.com/tasks/NvN6U22bQ-C626hsVGu4fA

error: failed to execute compile
caused by: error reading compile response from server
caused by: Failed to read response header
caused by: failed to fill whole buffer
error: could not compile `script`.

The error message is the same as in #24510, but setting SCCACHE_IDLE_TIMEOUT to zero does not help.

Merges in the regression range of nightly-2019-11-06 to nightly-2019-11-07 rust-lang/rust@1423bec...3804876:

Activity

  1. added
    I-bustageThe effect of the issue remaining unresolved.
    on Nov 12, 2019
  2. jdm commented on Nov 12, 2019

    @jdm
    Member

    What's the best way to tackle this? Try to reproduce this locally?

  3. SimonSapin commented on Nov 12, 2019

    @SimonSapin
    MemberAuthor

    I haven’t managed to reproduce when building on my machine with the same version of sccache.

    The output shows that this errors occurs when read_exact fails to read 4 bytes from a BufReader<TcpStream>.

    https://github.com/mozilla/sccache/blob/f1322dca19577310cfcfb40059ff954d2140598b/src/client.rs#L56-L59

    This happens when libc::recv returns 0, which indicates that the TCP connection has been closed.

  4. jdm commented on Nov 12, 2019

    @jdm
    Member

    Is it worth seeing if there's any interesting compiler output on CI if we don't use sccache?

  5. SimonSapin commented on Nov 12, 2019

    @SimonSapin
    MemberAuthor
  6. SimonSapin commented on Nov 12, 2019

    @SimonSapin
    MemberAuthor

    By the way, my workflow for this kind of "try build" without a PR is:

    • Make a local branch
    • Make changes to try
    • In the try-taskcluster list in the by_branch_name dict in etc/taskcluster/decision_task.py, add tasks to be run
    • Commit
    • git push origin -f HEAD:try-taskcluster
    • Navigate to https://github.com/servo/servo/commits/try-taskcluster
    • Click the orange dot on the latest commit (which should be the one you just pushed)
    • Click "Community-TC (push)" to view the task group on Taskcluster

    It’s mostly out of habit, I don’t know if it’s really better or worse than using try* Homu commands in a PR that is not destined to be merged.

  7. SimonSapin commented on Nov 12, 2019

    @SimonSapin
    MemberAuthor

    if we don't use sccache?

    https://community-tc.services.mozilla.com/tasks/Wxja6BOTQ6OYbp-79FhFtA succeeded. The only thing of note is that it generated more than 300k stderr lines worth of warnings, most of them from #24684. And rust-lang/rust#65134 is in the regression range.

    I’ve also started https://community-tc.services.mozilla.com/tasks/BgPRR43VTKWDVM8nY6A5Ew with RUST_LOG=trace into a log file for the sccache server.

  8. SimonSapin commented on Nov 12, 2019

    @SimonSapin
    MemberAuthor

    https://community-tc.services.mozilla.com/tasks/BgPRR43VTKWDVM8nY6A5Ew/runs/0/logs/https%3A%2F%2Fcommunity-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2FBgPRR43VTKWDVM8nY6A5Ew%2Fruns%2F0%2Fartifacts%2Fpublic%2Fsccache.log#L321219

    ERROR 2019-11-12T15:31:54Z: sccache::server: frame size too big
    

    https://github.com/tokio-rs/tokio/blob/master/tokio-util/src/codec/length_delimited.rs

                // Default max frame length of 8MB
                max_frame_len: 8 * 1_024 * 1_024,

    mozilla/sccache#329 / https://github.com/mozilla/sccache/blob/master/src/server.rs

            if let Ok(max_frame_length_str) = env::var("SCCACHE_MAX_FRAME_LENGTH") {
                if let Ok(max_frame_length) = max_frame_length_str.parse::<usize>() {
                    builder.max_frame_length(max_frame_length);
  9. SimonSapin commented on Nov 12, 2019

    @SimonSapin
    MemberAuthor

    https://community-tc.services.mozilla.com/tasks/LpLx0VqfTaqiCXEmEo-Qfw is green with SCCACHE_MAX_FRAME_LENGTH set to 100 MB.

  10. added 6 commits that reference this issue on Nov 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    I-bustageThe effect of the issue remaining unresolved.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions