Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] python3-ansible-lint: update to 5.2.0.
Date: Wed, 13 Oct 2021 12:59:10 +0200	[thread overview]
Message-ID: <20211013105910.-L-IN1L-PUoIp4P5QNeyumG5LaNTtRFgCZ12OflPLz4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31998@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

New review comment by jcgruenhage on void-packages repository

https://github.com/void-linux/void-packages/pull/31998#discussion_r727943220

Comment:
I think I've found the reason for these, the custom loader that ansible uses implements methods deprecated in Python 3.4, and Python 3.10 started spitting out warnings. In the context of tests, `filterwarnings` is set to `error`, which causes the tests to fail there. Fixes for these are being implemented in ansible, meaning we should get working tests. Apparently, as far as I can tell, the old methods still work, so it doesn't actually break anything in actual use, but the tests will still fail.

The failures in ansible-lint come from the imported ansible-core, the issue is not in ansible-lint itself.

  parent reply	other threads:[~2021-10-13 10:59 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 10:45 [PR PATCH] python3-ansible-lint: update to 5.0.12 jcgruenhage
2021-10-12 16:22 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-12 17:32 ` [PR PATCH] [Updated] python3-ansible-lint: update to 5.2.0 jcgruenhage
2021-10-12 18:01 ` [PR REVIEW] " paper42
2021-10-12 18:01 ` paper42
2021-10-13  9:25 ` jcgruenhage
2021-10-13  9:29 ` jcgruenhage
2021-10-13 10:59 ` jcgruenhage [this message]
2021-10-13 11:41 ` jcgruenhage
2021-10-13 12:59 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-13 15:03 ` [PR PATCH] [Updated] python3-ansible-lint: rename to ansible-lint, " jcgruenhage
2021-10-13 15:09 ` jcgruenhage
2021-10-13 16:45 ` [PR REVIEW] " Chocimier
2021-10-13 16:48 ` Chocimier
2021-10-13 16:48 ` Chocimier
2021-10-13 16:48 ` Chocimier
2021-10-13 17:30 ` jcgruenhage
2021-10-13 17:35 ` jcgruenhage
2021-10-13 18:10 ` jcgruenhage
2021-10-13 18:10 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-14 16:29 ` [PR REVIEW] " Chocimier
2021-10-14 16:29 ` Chocimier
2021-10-14 16:29 ` Chocimier
2021-10-14 16:30 ` Chocimier
2021-10-14 17:12 ` jcgruenhage
2021-10-14 20:02 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-14 20:04 ` jcgruenhage
2021-10-14 20:12 ` jcgruenhage
2021-10-14 20:12 ` [PR REVIEW] " jcgruenhage
2021-10-14 20:13 ` jcgruenhage
2021-10-14 20:22 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-14 21:26 ` [PR REVIEW] " jcgruenhage
2021-10-15 16:22 ` Chocimier
2021-10-15 16:23 ` Chocimier
2021-10-15 19:56 ` [PR REVIEW] " paper42
2021-10-16 13:49 ` jcgruenhage
2021-10-16 14:06 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-19 14:37 ` jcgruenhage
2021-10-19 15:11 ` jcgruenhage
2021-10-19 19:22 ` jcgruenhage
2021-10-19 19:29 ` [PR REVIEW] " jcgruenhage
2021-10-22 20:14 ` [PR REVIEW] python3-ansible-lint: update to 5.2.1 Chocimier
2021-10-23 10:51 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-23 10:51 ` [PR REVIEW] " jcgruenhage
2021-10-23 20:37 ` [PR PATCH] [Merged]: " Chocimier

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=20211013105910.-L-IN1L-PUoIp4P5QNeyumG5LaNTtRFgCZ12OflPLz4@z \
    --to=jcgruenhage@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).