Skip to content

CompatHelper: bump compat for IntervalArithmetic to 0.21, (keep existing compat) #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

github-actions[bot]
Copy link
Contributor

This pull request changes the compat entry for the IntervalArithmetic package from 0.14, 0.15, 0.16, 0.17, 0.18, 0.19, 0.20 to 0.14, 0.15, 0.16, 0.17, 0.18, 0.19, 0.20, 0.21.
This keeps the compat entries for earlier versions.

Note: I have not tested your package with this new compat entry.
It is your responsibility to make sure that your package tests pass before you merge this pull request.

@vtjeng vtjeng force-pushed the compathelper/new_version/2023-08-25-00-07-44-404-00039433418 branch from d6e0e18 to 6c550d1 Compare August 25, 2023 00:07
@vtjeng
Copy link
Owner

vtjeng commented Sep 5, 2023

This is failing on Julia 1 (but not 1.6) since IntervalArithmetic:0.21.0 supports only Julia 1.8. See history of version bumps:

The failure seems to have to do with the error message:

   Got exception outside of a @test
  MethodError: no method matching IntervalArithmetic.Interval(::Float64, ::Float64)
  
  Closest candidates are:
    (::Type{T})(::T) where T<:Number
     @ Core boot.jl:792

There have been many changes between the two versions, so it may be challenging to bisect to find the issue. JuliaIntervals/IntervalArithmetic.jl@v0.20.9...v0.21.0

@vtjeng
Copy link
Owner

vtjeng commented Sep 5, 2023

Superseded by #138.

@vtjeng vtjeng closed this Sep 5, 2023
@vtjeng vtjeng deleted the compathelper/new_version/2023-08-25-00-07-44-404-00039433418 branch January 1, 2024 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant