Hi Jeremy, Thank you for providing feedbacks, for the log access, I think it's my network problem. Yes, I'll try to fix as your solution pointed. Regards, David -----Original Message----- From: starlingx-discuss-request@lists.starlingx.io <starlingx-discuss-request@lists.starlingx.io> Sent: Thursday, July 20, 2023 9:20 PM To: starlingx-discuss@lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 62, Issue 41 CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Send Starlingx-discuss mailing list submissions to starlingx-discuss@lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request@lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner@lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Starlingx-discuss Digest, Vol 62, Issue 38 (Jeremy Stanley) 2. Re: Community Communication Channels - VOTE NEEDED (Cervi, Thales Elero) ---------------------------------------------------------------------- Message: 1 Date: Thu, 20 Jul 2023 12:32:29 +0000 From: Jeremy Stanley <fungi@yuggoth.org> To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Starlingx-discuss Digest, Vol 62, Issue 38 Message-ID: <20230720123228.fzrsixloayxl5hbf@yuggoth.org> Content-Type: text/plain; charset="us-ascii" On 2023-07-20 03:08:05 +0000 (+0000), Liu, David wrote:

I'm working on submit some code for review, and the zuul gate job failed, but I can't download the detailed logs, is there a problem with The CI server side?

My zuul job is here: https://zuul.opendev.org/t/openstack/build/760e0e486b024f9c9e5c5883af4 9299c/artifacts [...]

I'm not sure what logs you think are missing, but the console log there shows that the pyflakes static analysis tool you're running encountered a fatal exception: AttributeError: 'FlakesChecker' object has no attribute 'JOINEDSTR' https://zuul.opendev.org/t/openstack/build/760e0e486b024f9c9e5c5883af49299c/... I'm able to reproduce this by checking out your change and running `tox -e pep8 -c distributedcloud-client/tox.ini` under python3.7, while running the same with a fresh checkout of the master branch completes successfully, so there's definitely something about https://review.opendev.org/888424 which is triggering the problem. A quick web search on the exact error string turns up this mailing list thread from 2019 about incompatibilities between the hacking plugin and (then) newer flake8/pyflakes versions: https://lists.openstack.org/pipermail/openstack-discuss/2019-November/011027... My best guess, without digging deeper, is that something in the code being added in change 888424 is tickling the necessary code paths through pyflakes to hit the incompatibility with hacking. Indeed, editing distributedcloud-client/test-requirements.txt and bluntly replacing the hacking entry with just flake8 gets it to succeed, but of course this is only a reasonable solution if you don't care about the additional rules that module was enforcing. -- Jeremy Stanley