Looking at a series from Luca, I found build errors for opensuse: http://mails.dpdk.org/archives/test-report/2020-February/118961.html The splat is: An uncaught exception was raised. We may already know about the issue. If your patch is not run again after one business day, feel free to contact us to let us know. Traceback (most recent call last): File "/opt/dpdklab/dpdklab-ci/compile_with_podman.py", line 48, in <module> compile_dpdk.build() File "/opt/dpdklab/dpdklab-ci/compile_with_podman.py", line 35, in build self.image_build(image) File "/opt/dpdklab/dpdklab-ci/ci.py", line 202, in image_build cwd=script_dir + '/containers') File "/opt/dpdklab/dpdklab-ci/ci.py", line 180, in check_call subprocess.check_call(command, **kwargs) File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '('podman', 'build', '-t', 'opensuse-leap15/dpdk_compile', '-f', 'opensuse-leap15/dpdk_compile.Dockerfile', '.')' returned non-zero exit status 1. Is this being looked at? Thanks. -- David Marchand
On Mon, Mar 2, 2020 at 3:22 PM David Marchand <david.marchand@redhat.com> wrote: > > Looking at a series from Luca, I found build errors for opensuse: > http://mails.dpdk.org/archives/test-report/2020-February/118961.html > > The splat is: > > An uncaught exception was raised. We may already know about the issue. > If your patch is not run again after one business day, feel free to > contact us to let us know. > Traceback (most recent call last): > File "/opt/dpdklab/dpdklab-ci/compile_with_podman.py", line 48, in <module> > compile_dpdk.build() > File "/opt/dpdklab/dpdklab-ci/compile_with_podman.py", line 35, in build > self.image_build(image) > File "/opt/dpdklab/dpdklab-ci/ci.py", line 202, in image_build > cwd=script_dir + '/containers') > File "/opt/dpdklab/dpdklab-ci/ci.py", line 180, in check_call > subprocess.check_call(command, **kwargs) > File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call > raise CalledProcessError(retcode, cmd) > subprocess.CalledProcessError: Command '('podman', 'build', '-t', > 'opensuse-leap15/dpdk_compile', '-f', > 'opensuse-leap15/dpdk_compile.Dockerfile', '.')' returned non-zero > exit status 1. And as a bonus, where can I find those scripts? It would be easier to look into this kind of issue, or remove build options that are dead, like CONFIG_RTE_EAL_ALLOW_INV_SOCKET_ID [1] which is still set by this script. Thanks. 1: https://git.dpdk.org/dpdk/commit/?id=8e35792c5325f9fd2cb7cfab507aa23fc956ced7 -- David Marchand
[-- Attachment #1.1: Type: text/plain, Size: 2277 bytes --] Hi David, We have looked into the openSUSE compile errors. The issue was discovered to be related to Podman and have been resolved; we are now rerunning all tests that have been affected. Please give it a moment to complete all tests. As for the scripts used for starting the test, I have attached a zip that contains scripts used to kick off the tests. However, our team does still need to come up with a way to submit script changes to the project. Thanks On Mon, Mar 2, 2020 at 9:38 AM David Marchand <david.marchand@redhat.com> wrote: > On Mon, Mar 2, 2020 at 3:22 PM David Marchand <david.marchand@redhat.com> > wrote: > > > > Looking at a series from Luca, I found build errors for opensuse: > > http://mails.dpdk.org/archives/test-report/2020-February/118961.html > > > > The splat is: > > > > An uncaught exception was raised. We may already know about the issue. > > If your patch is not run again after one business day, feel free to > > contact us to let us know. > > Traceback (most recent call last): > > File "/opt/dpdklab/dpdklab-ci/compile_with_podman.py", line 48, in > <module> > > compile_dpdk.build() > > File "/opt/dpdklab/dpdklab-ci/compile_with_podman.py", line 35, in > build > > self.image_build(image) > > File "/opt/dpdklab/dpdklab-ci/ci.py", line 202, in image_build > > cwd=script_dir + '/containers') > > File "/opt/dpdklab/dpdklab-ci/ci.py", line 180, in check_call > > subprocess.check_call(command, **kwargs) > > File "/usr/lib64/python3.6/subprocess.py", line 311, in check_call > > raise CalledProcessError(retcode, cmd) > > subprocess.CalledProcessError: Command '('podman', 'build', '-t', > > 'opensuse-leap15/dpdk_compile', '-f', > > 'opensuse-leap15/dpdk_compile.Dockerfile', '.')' returned non-zero > > exit status 1. > > And as a bonus, where can I find those scripts? > It would be easier to look into this kind of issue, or remove build > options that are dead, like CONFIG_RTE_EAL_ALLOW_INV_SOCKET_ID [1] > which is still set by this script. > > Thanks. > > > 1: > https://git.dpdk.org/dpdk/commit/?id=8e35792c5325f9fd2cb7cfab507aa23fc956ced7 > > -- > David Marchand > > -- Brandon Lo UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 blo@iol.unh.edu www.iol.unh.edu [-- Attachment #1.2: Type: text/html, Size: 4660 bytes --] [-- Attachment #2: dpdklab_scripts.zip --] [-- Type: application/zip, Size: 25454 bytes --]
02/03/2020 17:25, Brandon Lo:
> As for the scripts used for starting the test, I have attached a zip that
> contains scripts used to kick off the tests.
> However, our team does still need to come up with a way to submit script
> changes to the project.
I think there are steps before allowing script changes from the community:
1/ publish the code
2/ correlate the results with the published scripts
3/ split setup-specifics and re-usable scripts
4/ use or improve scripts from dpdk-ci.git
5/ submit re-usable simple scripts to dpdk-ci for review & merge
If there is a consensus on above priorities,
we can add them to the bugzilla.
On Mon, Mar 2, 2020 at 5:26 PM Brandon Lo <blo@iol.unh.edu> wrote:
> We have looked into the openSUSE compile errors.
> The issue was discovered to be related to Podman and have been resolved; we are now rerunning all tests that have been affected.
> Please give it a moment to complete all tests.
Thanks, looks good now.
I should have created a bz to track this.
Will do for what I can find in the reports atm.
--
David Marchand