Skip to content

Laplace tests taking too long in develop Jenkins runs #3309

Description

@WardBrian

Nearly 10 hours in just that one step. They only take 30 minutes for PRs, because we don't run ASAN.

For develop, should we:

  • not run ASAN?
  • Split across more than one executor?

I don't believe it was this bad before #3250 cc @SteveBronder

Activity

  1. SteveBronder commented on Apr 23, 2026

    @SteveBronder
    Collaborator

    Yes I think it is from me setting the jenkinsfile to compile with O3 in that branch by accident. I'll open a PR for this

    https://github.com/stan-dev/math/pull/3250/changes#diff-e6ffa5dc854b843b3ee3c3c28f8eae2f436c2df2b1ca299cca1fa5982e390cf8

  2. WardBrian commented on Apr 24, 2026

    @WardBrian
    MemberAuthor

    They're also using O3 on PRs I believe, so that's not it. If we don't optimize the tests the time we save gets swamped by the runtime of the tests taking much longer IIRC

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