From: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
To: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH v14 00/16] Update Avocado testsuite
Date: Tue, 19 Oct 2021 08:34:41 +0000 [thread overview]
Message-ID: <AM4PR1001MB1220087D03FEEC8313D444B3EDBD9@AM4PR1001MB1220.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <dd2e18df-f197-5fd9-6846-23662ca76d9b@siemens.com>
> -----Original Message-----
> From: isar-users@googlegroups.com <isar-users@googlegroups.com> On Behalf Of
> Jan Kiszka
> Sent: Donnerstag, 14. Oktober 2021 17:51
> To: isar-users@googlegroups.com
> Subject: Re: [PATCH v14 00/16] Update Avocado testsuite
>
> On 14.10.21 12:25, Baurzhan Ismagulov wrote:
> > On Thu, Oct 14, 2021 at 10:54:37AM +0200, Jan Kiszka wrote:
> >> Didn't you once installed avocado for execution in CI? This is no longer
> >> happening - unless I missed something - and, thus, broke gitlab-ci.
> >
> > Yes, this happened in the v10 discussion:
> >
> > https://groups.google.com/g/isar-users/c/eSL1-OLaErE/m/6J3EfD9YCQAJ
> >
> > In a nutshell, the execution environment can have the control how the
> necessary
> > tools are provided (Debian packages or pip), just as it is today with the
> other
> > packages required by Isar.
>
> You broke gitlab-ci, please fix. This can only reasonably be done in
> Isar, not outside (avokado is not build dependency, this is not part of
> kas-isar).
Even when installing avocado manually (pip3 install avocado-framework), the tests (or rather the collection of results?) fail in GitLab CI using the kas-isar:latest container:
Traceback (most recent call last):
File "/builder/.local/lib/python3.7/site-packages/avocado/core/test.py", line 825, in _run_avocado
genio.write_file(whiteboard_file, self.whiteboard)
File "/builder/.local/lib/python3.7/site-packages/avocado/utils/genio.py", line 117, in write_file
with open(filename, 'w') as file_obj:
FileNotFoundError: [Errno 2] No such file or directory: './build/job-results/job-2021-10-15T14.02-5ab2e09/test-results/1-_builds_cEV_-yzV_0_ebsy_debian_isar_testsuite_build_test_build_test.py_CrossTest.test_cross/whiteboard'
ERROR 1-/builds/cEV_-yzV/0/ebsy/debian/isar/testsuite/build_test/build_test.py:CrossTest.test_cross -> FileNotFoundError: [Errno 2] No such file or directory: './build/job-results/job-2021-10-15T14.02-5ab2e09/test-results/1-_builds_cEV_-yzV_0_ebsy_debian_isar_testsuite_build_test_build_test.py_CrossTest.test_cross/whiteboard'
ERROR: [Errno 2] No such file or directory: './build/job-results/job-2021-10-15T14.02-5ab2e09/test-results/1-_builds_cEV_-yzV_0_ebsy_debian_isar_testsuite_build_test_build_test.py_CrossTest.test_cross/whiteboard' (5528.48 s)
INIT 2-/builds/cEV_-yzV/0/ebsy/debian/isar/testsuite/build_test/build_test.py:CrossTest.test_cross_ubuntu
PARAMS (key=timeout, path=*, default=None) => None
Test metadata:
filename: /builds/cEV_-yzV/0/ebsy/debian/isar/testsuite/build_test/build_test.py
teststmpdir: /var/tmp/avocado_haez6g83
(2/8) /builds/cEV_-yzV/0/ebsy/debian/isar/testsuite/build_test/build_test.py:CrossTest.test_cross_ubuntu: START 2-/builds/cEV_-yzV/0/ebsy/debian/isar/testsuite/build_test/build_test.py:CrossTest.test_cross_ubuntu
DATA (filename=output.expected) => NOT FOUND (data sources: variant, test, file)
Adriaan
next prev parent reply other threads:[~2021-10-19 8:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 16:45 Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 01/16] start_vm.py: Fix target name handling Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 02/16] start_vm.py: Add output and PID file vm_start.py options Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 03/16] start_vm.py: Add MIPS support Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 04/16] start_vm.py: Fix ubuntu image name Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 05/16] vm_boot_test: Fix log file path in vm_boot_test Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 06/16] vm_boot_test: Remove external varianter Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 07/16] vm_boot_test: Improve QEMU images checking Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 08/16] build_test: Refactoring build tests cases Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 09/16] testsuite: Add Python generations for testsuite in gitignore Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 10/16] testsuite: Fix test suite prepare guide Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 11/16] gitlab-ci: Add Avocado build artifacts Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 12/16] gitlab-ci: Add debug flag Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 13/16] vm_boot_test: Add automatic bitbake init Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 14/16] build_test: Protect ubuntu target with KFAIL Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 15/16] ci_build: Migrate to Avocado Anton Mikanovich
2021-09-30 16:45 ` [PATCH v14 16/16] vm_smoke_test: " Anton Mikanovich
2021-10-14 8:54 ` [PATCH v14 00/16] Update Avocado testsuite Jan Kiszka
2021-10-14 10:25 ` Baurzhan Ismagulov
2021-10-14 15:51 ` Jan Kiszka
2021-10-19 8:34 ` Schmidt, Adriaan [this message]
2021-10-22 6:54 ` Anton Mikanovich
2021-10-19 9:54 ` Henning Schild
2021-10-21 9:48 ` Baurzhan Ismagulov
[not found] <1633020197-26007-1-git-send-email-anton.mikanovich@promwad.com>
2021-10-13 14:06 ` Anton Mikanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM4PR1001MB1220087D03FEEC8313D444B3EDBD9@AM4PR1001MB1220.EURPRD10.PROD.OUTLOOK.COM \
--to=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox