Allow explicit failure as run result

Open
#178 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, backend

Research direction

The issue does not identify files, tests, or an entry point. Begin by locating how OpenML stores flow results and how metrics such as EPP consume them; define the representation and behavior for crashes and timeouts, then verify that failed runs can be stored and used by the relevant metrics.

Written by the indexing model from the issue text.

Description

Currently there is no way to store a "failed run" result on OpenML: when a flow has been executed on a task, but the result is a crash (or timeout). We should consider storing this information (also helps with computing some metrics, e.g., EPP).

Dominant language
Python
Stars
16
Forks
50
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openml/server-api

All issues in openml/server-api

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.