Decathlon / Decathlon/ara

Cannot differentiate between an inexistant and an unfinished execution

Open
#318 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
80
Forks
17
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
When checking an execution quality status, it is not possible to differentiate between an inexistant execution (via job url) and unfinished execution. In both case, the response is `STILL_COMPUTING`. This is misleading.

**To Reproduce**
Steps to reproduce the behavior:
1. Open your ARA Swagger
2. Go to `execution-resource`
3. Go to `GET` `/api/projects/{projectCode}/executions/quality-status` (`getQualityStatus`)
4. In the `projectCode` field, type a **valid** project code but an **invalid** url in the `jobUrl` field

**Expected behavior**
Inexistant executions should return a different status, such as `UNKNOWN`.

**Screenshots**
![ezgif com-gif-maker](https://user-images.githubusercontent.com/47318765/92936615-930bc200-f44a-11ea-9524-376d53b58441.png)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.