Project

General

Profile

Actions

action #98394

closed

Fix MicroOS scheduling to have incidents

Added by livdywan over 2 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
High
Assignee:
Target version:
Start date:
2021-09-06
Due date:
% Done:

0%

Estimated time:

Description

Motivation

MicroOS does not have Incidents. bot-ng can't deal with these cases, see also #98198.

Suggestion

  • Change the schedule... where?

Files


Related issues 1 (0 open1 closed)

Copied from QA - action #98198: [bot-ng] Fix auto-approve on updates without Incidents size:MResolvedosukup2021-09-06

Actions
Actions #1

Updated by livdywan over 2 years ago

  • Copied from action #98198: [bot-ng] Fix auto-approve on updates without Incidents size:M added
Actions #2

Updated by osukup over 2 years ago

  • Description updated (diff)
Actions #3

Updated by livdywan over 2 years ago

Updated by osukup about 2 hours ago
Description updated (diff)

@osukup You forgot the most important part: where does this need to be changed? This is why the ticket isn't workable yet.

Actions #4

Updated by okurz over 2 years ago

  • Status changed from New to Feedback
  • Assignee set to okurz

Hi, we tried to estimate this ticket in the daily 2021-09-13. The problem seems to be that there are simply no incident tests for the flavor MicroOS defined so there is nothing that bot-ng can schedule.

@cdywan where does this ticket come from? Did you report it on behalf of someone else?

Actions #5

Updated by livdywan over 2 years ago

  • Status changed from Feedback to Rejected

okurz wrote:

Hi, we tried to estimate this ticket in the daily 2021-09-13. The problem seems to be that there are simply no incident tests for the flavor MicroOS defined so there is nothing that bot-ng can schedule.

@cdywan where does this ticket come from? Did you report it on behalf of someone else?

We filed it during an estimation because #98198 was about behavior of bot-ng, and this ticket is about adjusting the test configuration so that there's no need for a special-case - I take it there's nothing to fix here then, I simply didn't get a straight answer during the call.

Actions

Also available in: Atom PDF