Skip to content

test_work_stealing_on_scaling_up failing #336

Closed

Description

@ian-r-rose

#308 was merged a few days ago. It appears to be skipped for 2022.6.0 (cf #306), but it runs on upstream.
I have seen it fail a number of times with killed workers:

https://github.com/coiled/coiled-runtime/actions/runs/3062687464/jobs/4943938999
https://github.com/coiled/coiled-runtime/actions/runs/3062426988/jobs/4943389537

We may want to skip it for the time being. cc @hendrikmakait

Activity

  1. fjetter commented on Sep 16, 2022

    @fjetter
    Contributor

    I'd like to point out that this is not a flakiness problem since it now fails very reliably. There appears to be a problem with the software environments

      +-------------+-----------------------+-----------+----------+
      | Package     | client                | scheduler | workers  |
      +-------------+-----------------------+-----------+----------+
      | dask        | 2022.9.0+22.g982376ef | 2022.6.0  | 2022.6.0 |
      | distributed | 2022.9.0+13.g1fd07f03 | 2022.6.0  | 2022.6.0 |
      +-------------+-----------------------+-----------+----------+
    

    Did this fail before package_sync as well? The CI jobs you are pointing to are using package_sync.

  2. fjetter commented on Sep 16, 2022

    @fjetter
    Contributor

    This test is using cluster.scale to upscale an existing cluster. @shughes-uk is this supported with package sync?

  3. changed the title [-]`test_work_stealing_on_scaling_up` flaky[/-] [+]`test_work_stealing_on_scaling_up` failing[/+] on Sep 16, 2022
  4. hendrikmakait commented on Sep 16, 2022

    @hendrikmakait
    Contributor

    Note the difference between the mismatch on CI

      +-------------+-----------------------+-----------+----------+
      | Package     | client                | scheduler | workers  |
      +-------------+-----------------------+-----------+----------+
      | dask        | 2022.9.0+25.g1a8533fd | 2022.6.0  | 2022.6.0 |
      | distributed | 2022.9.0+13.g1fd07f03 | 2022.6.0  | 2022.6.0 |
      +-------------+-----------------------+-----------+----------+
    

    and the mismatch for worker i-04790bd562d506836 on the corresponding cluster

    Sep 16 00:34:42 ip-10-0-11-96 cloud-init[1125]: +-------------+-------------+-----------+---------------------------------------+
    Sep 16 00:34:42 ip-10-0-11-96 cloud-init[1125]: | Package     | This Worker | scheduler | workers                               |
    Sep 16 00:34:42 ip-10-0-11-96 cloud-init[1125]: +-------------+-------------+-----------+---------------------------------------+
    Sep 16 00:34:42 ip-10-0-11-96 cloud-init[1125]: | dask        | 2022.6.0    | 2022.6.0  | {'2022.6.0', '2022.9.0+25.g1a8533fd'} |
    Sep 16 00:34:42 ip-10-0-11-96 cloud-init[1125]: | distributed | 2022.6.0    | 2022.6.0  | {'2022.6.0', '2022.9.0+13.g1fd07f03'} |
    Sep 16 00:34:42 ip-10-0-11-96 cloud-init[1125]: +-------------+-------------+-----------+---------------------------------------+
    
  5. ntabris commented on Sep 16, 2022

    @ntabris
    Member
  6. ian-r-rose commented on Sep 16, 2022

    @ian-r-rose
    ContributorAuthor

    Thanks @ntabris, is this deployed yet? If not, I'd propose skipping this test until then.

  7. ntabris commented on Sep 16, 2022

    @ntabris
    Member

    is this deployed yet?

    No, we were waiting on pyzmq wheels for linux x86 which are now out. I'd expect Coiled release today or Monday.

  8. shughes-uk commented on Sep 17, 2022

    @shughes-uk
    Contributor

    Should be deployed now

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

      Issue actions