Skip to content
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

Test benchmark [Do not merge] #18

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Test benchmark [Do not merge] #18

wants to merge 1 commit into from

Conversation

tmigot
Copy link
Member

@tmigot tmigot commented Oct 2, 2021

No description provided.

@codecov
Copy link

codecov bot commented Oct 2, 2021

Codecov Report

Merging #18 (cab25d1) into main (ce52fe0) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage   73.86%   73.86%           
=======================================
  Files           9        9           
  Lines         681      681           
=======================================
  Hits          503      503           
  Misses        178      178           
Impacted Files Coverage Δ
src/algo.jl 76.19% <0.00%> (ø)
src/feasibility.jl 65.21% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ce52fe0...cab25d1. Read the comment docs.

@tmigot
Copy link
Member Author

tmigot commented Oct 2, 2021

Benchmark Report for FletcherPenaltyNLPSolver

Job Properties

  • Time of benchmarks:
    • Target: 2 Oct 2021 - 04:35
    • Baseline: 2 Oct 2021 - 04:45
  • Package commits:
    • Target: cab25d
    • Baseline: ce52fe
  • Julia commits:
    • Target: f9720d
    • Baseline: f9720d
  • Julia command flags:
    • Target: None
    • Baseline: None
  • Environment variables:
    • Target: None
    • Baseline: None

Results

A ratio greater than 1.0 denotes a possible regression (marked with ❌), while a ratio less
than 1.0 denotes a possible improvement (marked with ✅). Only significant results - results
that indicate possible regressions or improvements - are shown below (thus, an empty table means that all
benchmark results remained invariant between builds).

ID time ratio memory ratio
["cutest_fps_ipopt_equality_benchmark"] 0.91 (5%) ✅ 0.73 (1%) ✅
["cutest_fps_ipopt_mixed_benchmark"] 1.11 (5%) ❌ 1.11 (1%) ❌

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