Skip to content

CI is currently failing #613

@guillaumeeb

Description

@guillaumeeb
Member

Two things to look at:

Activity

jrueb

jrueb commented on Aug 4, 2023

@jrueb
Contributor

One thing I noticed is that this looks really outdated

- repo: https://gitlab.com/pycqa/flake8

flake8 moved to github years ago, see https://flake8.pycqa.org/en/latest/release-notes/4.0.0.html "Migrate from GitLab to GitHub"

kaelancotter

kaelancotter commented on Mar 13, 2024

@kaelancotter
Contributor

Are you looking for help with this?

guillaumeeb

guillaumeeb commented on Mar 13, 2024

@guillaumeeb
MemberAuthor

Definitely!

kaelancotter

kaelancotter commented on Mar 15, 2024

@kaelancotter
Contributor

Created PR 636 to resolve CI failures.
Unfortunately CI fails in the PR since the updated images aren't pushed from the build step if its a PR - so CI action is still using the old docker images.
LMK if there's another direction I should take this to deal with the docker image catch-22

Specific to SGE tests - adding the --full-trace flag got rid of the seg fault, but I don't have a good root cause analysis.

This PR also doesn't address CI for documentation.

added a commit that references this issue on Mar 22, 2024
8713202
jacobtomlinson

jacobtomlinson commented on Aug 21, 2024

@jacobtomlinson
Member

CI is in a much better place. #653 is still outstanding but I think we can close this issue in favour of that one.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @jacobtomlinson@kaelancotter@guillaumeeb@jrueb

        Issue actions

          CI is currently failing · Issue #613 · dask/dask-jobqueue