Skip to content

Windows CI times out after 6 hours #2447

Description

@iteratee

Describe the bug
I am unable to get CI to pass because the windows bzlmod rules_haskell_tests run will time out at 6 hours instead of completing

To Reproduce
Create a new MR, or just re-run the job on my MR

Expected behavior
I would expect that:

  1. Effective caching would cause job re-runs to be able to re-use most of the work of a job that timed out after 6 hours
  2. None of the CI jobs would require 6 hours to complete in any case.

Environment

  • OS name + version: Windows 2022
  • Bazel version: 6.5.0
  • Version of the rules: HEAD

Additional context
The run with bzlmod disabled is also long running, but I managed to get it to finish just under the 6 hour timeout. Both should be looked at.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions