Project

General

Profile

Actions
Copy link

action #106756

open

cmd returned 32768 repeatedly reported on o3

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

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
QA - future
Start date:
2022-02-03
Due date:
% Done:

0%

Estimated time:

Description

Observation

[2022-02-14T09:26:31.328344Z] [error] [pid:23389] cmd returned 32768
[2022-02-14T09:26:31.356457Z] [error] [pid:23389] cmd returned 32768

Log entry with context:

[2022-02-14T09:26:31.303584Z] [info] [pid:23389] Running cmd: git -C /var/lib/openqa/share/tests/opensuse log --stat --pretty=oneline --abbrev-commit --no-merges cc2f36979a48111386b4a94cc7a5cbe0ba1aeaf8..18cc7c92e7af279e57588192f124621111a4256e
[2022-02-14T09:26:31.328179Z] [warn] [pid:23389] fatal: Invalid revision range cc2f36979a48111386b4a94cc7a5cbe0ba1aeaf8..18cc7c92e7af279e57588192f124621111a4256e
[2022-02-14T09:26:31.328344Z] [error] [pid:23389] cmd returned 32768

Acceptance criteria

AC1:

Suggestions

Related issues 2 (1 open — 1 closed)

Copied from openQA Infrastructure - action #105828: 4-7 logreport emails a day cause alert fatigue size:MResolvedtinita2022-02-032022-02-17

Actions
Copied to openQA Infrastructure - action #107023: cmd returned 31744 repeatedly reported on o3New2022-02-03

Actions
Actions
Copy link
 #1

Updated by livdywan about 2 years ago

  • Copied from action #105828: 4-7 logreport emails a day cause alert fatigue size:M added
Actions
Copy link
 #2

Updated by tinita about 2 years ago

  • Assignee deleted (tinita)
Actions
Copy link
 #3

Updated by tinita about 2 years ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by tinita about 2 years ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by okurz about 2 years ago

  • Due date deleted (2022-02-17)
  • Target version changed from Ready to future

Thanks. Having it excluded from alerting is enough for now

Actions
Copy link
 #6

Updated by tinita about 2 years ago

okurz wrote:

Thanks. Having it excluded from alerting is enough for now

Hm, do we have that?

Actions
Copy link
 #7

Updated by okurz about 2 years ago

  • Status changed from New to In Progress
  • Assignee set to okurz
  • Priority changed from Normal to Urgent
  • Target version changed from future to Ready

Sorry, I confused pull requests. As long as we keep getting alerts on this message we should definitely treat this with higher prio. But removing urgency should be easily doable with a simple pull request to https://github.com/os-autoinst/openqa-logwarn

Actions
Copy link
 #8

Updated by okurz about 2 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #9

Updated by okurz about 2 years ago

  • Status changed from Feedback to New
  • Assignee deleted (okurz)
  • Priority changed from Urgent to Low
  • Target version changed from Ready to future

PR merged and it's deployed on o3. The rest needs to be followed up later.

Actions
Copy link
 #10

Updated by livdywan about 2 years ago

  • Copied to action #107023: cmd returned 31744 repeatedly reported on o3 added
Actions
Copy link

Also available in: Atom PDF