action #106756
open
cmd returned 32768 repeatedly reported on o3
Added by livdywan about 2 years ago.
Updated about 2 years ago.
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¶
- Copied from action #105828: 4-7 logreport emails a day cause alert fatigue size:M added
- Assignee deleted (
tinita)
- Description updated (diff)
- Description updated (diff)
- Due date deleted (
2022-02-17)
- Target version changed from Ready to future
Thanks. Having it excluded from alerting is enough for now
okurz wrote:
Thanks. Having it excluded from alerting is enough for now
Hm, do we have that?
- 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
- Status changed from In Progress to Feedback
- 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.
- Copied to action #107023: cmd returned 31744 repeatedly reported on o3 added
Also available in: Atom
PDF