Skip to content

Run 32bit test suite on PR CI? #69823

Open

Description

@RalfJung

@rust-lang/infra do we have enough spare capacity on the PR CI runner to add something like ./x.py test src/test/ui --target i686-unknown-linux-gnu --pass check? That would help find 32bit-only issues in tests before things get to bors. And running with --pass check would also ensure that the test suite actually passes in check-only mode, which is not a given (some tests fail and need ignore-pass).

Activity

  1. added
    T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.
    on Mar 8, 2020
  2. added
    C-feature-requestCategory: A feature request, i.e: not implemented / a PR.
    on Mar 8, 2020
  3. emilyalbini commented on Mar 9, 2020

    @emilyalbini
    Member

    Nominating for discussion at the infrastructure team meeting.

  4. Mark-Simulacrum commented on Mar 10, 2020

    @Mark-Simulacrum
    Member

    I would be interested in seeing error rates, at least; I have not experienced a lot of pain with 32 bit tests failing (and 64 bit tests passing). OTOH, maybe the --pass check mode is worth it...

    Do we have numbers on how long we expect this to take on CI? I would expect someone to run the UI tests that we already run on CI locally and then figure out an approximate "CI slowdown" based on how long those take, to determine how long we'd expect this test to take.

  5. emilyalbini commented on Mar 11, 2020

    @emilyalbini
    Member

    We discussed this in the infra team meeting, and we'd like to see numbers on the impact this would have in our CI times before making a decision.

  6. aidanhs commented on Mar 18, 2020

    @aidanhs
    Contributor

    To be more explicit - it's not likely that the infra team will have a chance to proactively look into this.

    As stated above, we would be looking for help on understanding:

    • how does this affect our CI times
    • how much of a 'significant bit' is this check (i.e. how often would this catch something that the current check wouldn't)
  7. emilyalbini commented on Apr 1, 2020

    @emilyalbini
    Member

    Discussed this again in the infrastructure team meeting: we're still waiting for the data before making a decision, and unfortunately nobody in the team has a chance to gather it.

  8. RalfJung commented on Apr 1, 2020

    @RalfJung
    MemberAuthor

    I am also not sure when I will have the time to do such experiments.

  9. RalfJung commented on May 8, 2020

    @RalfJung
    MemberAuthor

    @Mark-Simulacrum self-assigned this 2 days ago

    Can I take this to mean you plan to look into this? :)

  10. Mark-Simulacrum commented on May 8, 2020

    @Mark-Simulacrum
    Member

    Yes, I've been running out of time these past couple days but hopefully will get to it soon.

  11. removed their assignment
    on Aug 5, 2020
  12. Mark-Simulacrum commented on Oct 7, 2020

    @Mark-Simulacrum
    Member

    As of #72053, we are running UI tests in check mode on the PR CI builder. We are not yet running them in 32 bit mode, though, because LLVM 8 is broken on cross-compilation (IIRC, don't remember details though).

  13. added
    P-lowLow priority
    and removed on Nov 4, 2020
  14. added a commit that references this issue on Nov 19, 2020
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-feature-requestCategory: A feature request, i.e: not implemented / a PR.P-lowLow priorityT-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