Skip to content

Benchmarking script depends on downstream packages #5418

@giordano

Description

@giordano

The benchmarking script depends on packages like ClimaSeaIce and NumericalEarth

ClimaSeaIce = "6ba0ff68-24e6-4315-936c-2e99227c95a4"
Dates = "ade2ca70-3891-5945-98fb-dc099432e06a"
JLD2 = "033835bb-8acc-5ee8-8aae-3f567f8a3819"
JSON = "682c06a0-de6a-54ab-a142-c8b1cf79cde6"
NCDatasets = "85f8d34a-cbdd-5861-8df4-14fed0d494ab"
NumericalEarth = "904d977b-046a-4731-8b86-9235c0d1ef02"
which themselves depend on Oceananigans, which means that when a new breaking version is tagged here, the benchmarking script won't work until those packages are updated to support the newer version. Ideally, the benchmarking script should be somewhat "self-sufficient" in the sense that it doesn't depend on packages downstream of Oceananigans, which then cause a sort of circular dependency. CC @glwagner @simone-silvestri.

Metadata

Metadata

Assignees

No one assigned

    Labels

    benchmark performanceruns preconfigured benchamarks and spits out timing

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions