Project

General

Profile

Actions

action #163787

open

https://progress.opensuse.org/issues/163787 [openqa-in-openqa] autoinst-log.txt uploaded from within the test should always return non-empty content if jobs are actually executed size:S

Added by okurz 16 days ago. Updated 1 day ago.

Status:
In Progress
Priority:
High
Assignee:
Category:
Feature requests
Target version:
Start date:
2024-07-11
Due date:
2024-08-09 (Due in 13 days)
% Done:

0%

Estimated time:

Description

Observation

openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in
test_running due to #163784
but investigation is harder because as visible in https://openqa.opensuse.org/tests/4333739#step/test_running/16 no autoinst-log.txt is found but still an empty file is uploaded.

Acceptance criteria

  • AC1: test_running_autoinst-log.txt has non-zero content also on incomplete jobs failing in early stages

Suggestions

  • Instead of (cat foo.txt */*/bar.txt ||: | tee …) consider using find … -exec … or another approach which only uploads a file if it actually exists and does not print confusing error messages
  • Others uploaded files do not seem to be affected
  • This affects any Incomplete jobs in openQA-in-openQA tests, e.g. if CASEDIR is invalid

Related issues 1 (1 open0 closed)

Related to openQA Project - action #163784: [openqa-in-openqa] test fails in test_running on "retry -s 10 -r 6 -e -- sh -c 'test -f /var/lib/openqa/share/tests/*/.git/config", probably due to transient network errors size:SWorkable2024-07-11

Actions
Actions #1

Updated by okurz 9 days ago

  • Priority changed from Normal to High
  • Target version changed from future to Ready
  • Parent task deleted (#163784)
Actions #2

Updated by okurz 9 days ago

  • Related to action #163784: [openqa-in-openqa] test fails in test_running on "retry -s 10 -r 6 -e -- sh -c 'test -f /var/lib/openqa/share/tests/*/.git/config", probably due to transient network errors size:S added
Actions #3

Updated by tinita 9 days ago

I had a quick look and ran find /var/lib/openqa/pool/ /var/lib/openqa/testresults/ in the post_fail_hook:

/var/lib/openqa/pool/
/var/lib/openqa/pool/1
/var/lib/openqa/pool/1/.locked
/var/lib/openqa/testresults/
/var/lib/openqa/testresults/00000
/var/lib/openqa/testresults/00000/00000001-example-DVD-x86_64-Buildtest-simple_boot@64bit
/var/lib/openqa/testresults/00000/00000001-example-DVD-x86_64-Buildtest-simple_boot@64bit/.thumbs
/var/lib/openqa/testresults/00000/00000001-example-DVD-x86_64-Buildtest-simple_boot@64bit/ulogs
/var/lib/openqa/testresults/00000/00000001-example-DVD-x86_64-Buildtest-simple_boot@64bit/details-GRU.json

that's really not much...
When I have an incomplete test locally, I at least have these files in the testresults dir: autoinst-log.txt ulogs vars.json worker-log.txt

Actions #4

Updated by okurz 9 days ago

  • Tracker changed from coordination to action
Actions #5

Updated by robert.richardson 3 days ago · Edited

  • Subject changed from [openqa-in-openqa] autoinst-log.txt should always return non-empty content if jobs are actually executed to https://progress.opensuse.org/issues/163787 [openqa-in-openqa] autoinst-log.txt uploaded from within the test should always return non-empty content if jobs are actually executed size:S
  • Status changed from New to Workable
Actions #6

Updated by robert.richardson 3 days ago

  • Description updated (diff)
Actions #7

Updated by tinita 2 days ago

  • Status changed from Workable to In Progress
  • Assignee set to tinita
Actions #8

Updated by tinita 2 days ago

While running the test locally with vncviewer, I realized that the error message does not come from https://github.com/os-autoinst/os-autoinst/blob/master/OpenQA/Isotovideo/Utils.pm#L84 but from https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/Task/Git/Clone.pm#L60

I have to get familiar with how to set that up locally.
If it happens before the autoinst-log.txt is ever created, we might need something else.

Actions #9

Updated by openqa_review 1 day ago

  • Due date set to 2024-08-09

Setting due date based on mean cycle time of SUSE QE Tools

Actions

Also available in: Atom PDF