Skip to content

Actions: jump-dev/MultiObjectiveAlgorithms.jl

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
684 workflow runs
684 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Enable algorithms to update the ideal_point during a solve CI #276: Pull request #102 synchronize by odow
12m 15s od/ideal-point-lazy
od/ideal-point-lazy
12m 15s
Enable algorithms to update the ideal_point during a solve format-check #268: Pull request #102 synchronize by odow
1m 7s od/ideal-point-lazy
od/ideal-point-lazy
1m 7s
Enable algorithms to update the ideal_point during a solve CI #275: Pull request #102 opened by odow
12m 7s od/ideal-point-lazy
od/ideal-point-lazy
12m 7s
Enable algorithms to update the ideal_point during a solve format-check #267: Pull request #102 opened by odow
1m 4s od/ideal-point-lazy
od/ideal-point-lazy
1m 4s
TagBot trigger issue TagBot #136: Issue comment #38 (comment) created by JuliaTagBot
2m 24s
2m 24s
Prep for v1.4.1 (#101) CI #274: Commit 048fe40 pushed by odow
20m 57s master
master
20m 57s
Prep for v1.4.1 (#101) format-check #266: Commit 048fe40 pushed by odow
3m 36s master
master
3m 36s
Prep for v1.4.1 TagBot #135: Issue comment #101 (comment) created by codecov bot
1s
1s
Prep for v1.4.1 CI #273: Pull request #101 opened by odow
12m 5s odow-patch-1
odow-patch-1
12m 5s
Prep for v1.4.1 format-check #265: Pull request #101 opened by odow
1m 4s odow-patch-1
odow-patch-1
1m 4s
Move computing the ideal point after the optimizer has run (#100) format-check #264: Commit af7ce29 pushed by odow
59s master
master
59s
Move computing the ideal point after the optimizer has run (#100) CI #272: Commit af7ce29 pushed by odow
11m 58s master
master
11m 58s
Move computing the ideal point after the optimizer has run TagBot #134: Issue comment #100 (comment) created by odow
1s
1s
Move computing the ideal point after the optimizer has run TagBot #133: Issue comment #100 (comment) created by remi-garcia
2s
2s
Move computing the ideal point after the optimizer has run TagBot #132: Issue comment #100 (comment) created by codecov bot
1s
1s
Move computing the ideal point after the optimizer has run CI #271: Pull request #100 opened by odow
22m 51s od/move-ideal-point
od/move-ideal-point
22m 51s
Move computing the ideal point after the optimizer has run format-check #263: Pull request #100 opened by odow
2m 9s od/move-ideal-point
od/move-ideal-point
2m 9s
Add time limits to compute ideal point & dichotomy starting solutions… format-check #262: Commit 65b565d pushed by odow
6m 31s master
master
6m 31s
Add time limits to compute ideal point & dichotomy starting solutions… CI #270: Commit 65b565d pushed by odow
40m 39s master
master
40m 39s
Add time limits to compute ideal point & dichotomy starting solutions TagBot #131: Issue comment #99 (comment) created by sandyspiers
1s
1s
Add time limits to compute ideal point & dichotomy starting solutions CI #269: Pull request #99 synchronize by sandyspiers
36m 41s sandyspiers:add-time-limits
sandyspiers:add-time-limits
36m 41s
Add time limits to compute ideal point & dichotomy starting solutions format-check #261: Pull request #99 synchronize by sandyspiers
11m 4s sandyspiers:add-time-limits
sandyspiers:add-time-limits
11m 4s
Add time limits to compute ideal point & dichotomy starting solutions TagBot #130: Issue comment #99 (comment) created by codecov bot
1s
1s
Add time limits to compute ideal point & dichotomy starting solutions TagBot #129: Issue comment #99 (comment) created by kofgokhan
1s
1s
Add time limits to compute ideal point & dichotomy starting solutions format-check #260: Pull request #99 opened by sandyspiers
14m 13s sandyspiers:add-time-limits
sandyspiers:add-time-limits
14m 13s
ProTip! You can narrow down the results and go further in time using created:<2025-04-07 or the other filters available.