Skip to content

CI: Make sure that we can bootstrap with cfg(parallel_queries). #48607

Closed

Description

@michaelwoerister

For now a docker image that just builds with cfg(parallel_queries) (but without running tests) should be enough.

cc @Zoxc

Activity

  1. added
    T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.
    on Mar 9, 2018
  2. Zoxc commented on Mar 9, 2018

    @Zoxc
    Contributor

    I would also like Travis PRs builds to run x.py check with cfg(parallel_queries) before doing the normal build without cfg(parallel_queries).

  3. Zoxc commented on Mar 9, 2018

    @Zoxc
    Contributor

    cc @rust-lang/infra

  4. added
    T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
    on Mar 9, 2018
  5. changed the title [-]CI: Make sure the we can bootstrap with cfg(parallel_queries).[/-] [+]CI: Make sure that we can bootstrap with cfg(parallel_queries).[/+] on Mar 9, 2018
  6. alexcrichton commented on Mar 9, 2018

    @alexcrichton
    Member

    We unfortunately don't have a lot of spare cycles on CI right now, both in terms of overall capacity and extra time to run more tests on builders (we're already timing out all over the place). If this is "things are on fire we really need this" then this can be prioritized, but otherwise this probably won't happen for awhile.

  7. alexcrichton commented on Mar 9, 2018

    @alexcrichton
    Member

    er, didn't mean to close

  8. michaelwoerister commented on Mar 12, 2018

    @michaelwoerister
    MemberAuthor

    I think it would be great if we could at least make sure that stage 0 builds with cfg(parallel_queries). Down the line we'll have to run test too but that's not so urgent.

  9. alexcrichton commented on Mar 12, 2018

    @alexcrichton
    Member

    That may be easier to do so, yeah. We could probably do something like RUSTFLAGS_STAGE0=... on whatever builder executes the fastest today, such as x86_64-gnu-debug

  10. Zoxc commented on Mar 12, 2018

    @Zoxc
    Contributor

    I'd be satisfied with running x.py check on some configuration which should take like 6 minutes (assuming it skips LLVM).

  11. Zoxc commented on Mar 16, 2018

    @Zoxc
    Contributor

    Running x.py check first would also serve to quickly reject PRs with compile errors. I'm not sure that matters for the bors queue, but it might help with PR builds.

  12. alexcrichton commented on Mar 16, 2018

    @alexcrichton
    Member

    Oh yeah that could for sure work! The check build finishes so quickly we could just add a slew of extra builders on Travis. They can get scheduled in the cracks between other builds

  13. michaelwoerister commented on Mar 16, 2018

    @michaelwoerister
    MemberAuthor

    That seems like a good first step.

  14. michaelwoerister commented on May 4, 2018

    @michaelwoerister
    MemberAuthor

    The ./x.py check approach was added in #49120 and #50444 extends it a little.

  15. added a commit that references this issue on May 4, 2018
  16. added a commit that references this issue on May 5, 2018
  17. added
    C-enhancementCategory: An issue proposing an enhancement or a PR with one.
    on May 14, 2018
  18. added
    T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
    and removed
    T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
    on Apr 21, 2019
  19. Mark-Simulacrum commented on Aug 19, 2019

    @Mark-Simulacrum
    Member

    Closing as per the above. @aturon is taking over some of the parallel compiler review work though so I think as we move closer to making that stable we'll probably want to enable more builders and such but keeping this open doesn't seem too useful.

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

    C-enhancementCategory: An issue proposing an enhancement or a PR with one.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions