Github messages for voidlinux
 help / color / mirror / Atom feed
From: jason1987d <jason1987d@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] radicale: update to 3.3.3.
Date: Sat, 04 Jan 2025 23:28:26 +0100	[thread overview]
Message-ID: <20250104222826.B567B22E57@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53225@inbox.vuxu.org>

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

New review comment by jason1987d on void-packages repository

https://github.com/void-linux/void-packages/pull/53225#discussion_r1903161550

Comment:
```
=> radicale-3.3.3_1: running do_check ...
============================= test session starts ==============================
platform linux -- Python 3.13.1, pytest-8.3.1, pluggy-1.5.0
rootdir: /builddir/radicale-3.3.3
configfile: pyproject.toml
plugins: flake8-1.1.1, cov-5.0.0
collected 202 items

radicale/tests/test_auth.py ...................................          [ 17%]
radicale/tests/test_base.py ............................................ [ 39%]
.......................................................                  [ 66%]
radicale/tests/test_config.py ...............                            [ 73%]
radicale/tests/test_expand.py ....                                       [ 75%]
radicale/tests/test_rights.py ...........                                [ 81%]
radicale/tests/test_server.py .......                                    [ 84%]
radicale/tests/test_storage.py ............................              [ 98%]
radicale/tests/test_web.py ...                                           [100%]

=============================== warnings summary ===============================
radicale/tests/test_base.py: 96 warnings
radicale/tests/test_expand.py: 8 warnings
radicale/tests/test_storage.py: 16 warnings
  /builddir/radicale-3.3.3/radicale/app/report.py:174: DeprecationWarning: Testing an element's truth value will always return True in future versions.  Use specific 'len(elem)' or 'elem is not None' test instead.
    props: Union[ET.Element, List] = root.find(xmlutils.make_clark("D:prop")) or []

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
====================== 202 passed, 120 warnings in 6.76s =======================
```

  parent reply	other threads:[~2025-01-04 22:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 16:28 [PR PATCH] radicale: update to 3.3.1 jason1987d
2024-12-15 16:29 ` [PR PATCH] [Updated] " jason1987d
2025-01-01  3:29 ` [PR PATCH] [Updated] radicale: update to 3.3.2 jason1987d
2025-01-01  3:31 ` radicale: update to 3.3.3 jason1987d
2025-01-01  3:40 ` [PR PATCH] [Updated] " jason1987d
2025-01-01  3:46 ` jason1987d
2025-01-01  3:50 ` jason1987d
2025-01-04 17:47 ` [PR REVIEW] " ahesford
2025-01-04 17:47 ` ahesford
2025-01-04 22:28 ` jason1987d [this message]
2025-01-05  3:19 ` ahesford
2025-01-05 15:41 ` jason1987d
2025-01-05 15:44 ` jason1987d
2025-01-05 15:47 ` jason1987d
2025-01-05 18:53 ` [PR PATCH] [Updated] " jason1987d
2025-01-05 18:53 ` jason1987d
2025-01-05 19:23 ` ahesford
2025-01-12  0:41 ` jason1987d
2025-01-12 19:19 ` [PR PATCH] [Updated] " jason1987d
2025-01-12 19:23 ` radicale: update to 3.4.0 jason1987d
2025-01-12 19:23 ` jason1987d
2025-01-12 19:58 ` [PR REVIEW] " ahesford
2025-01-12 20:30 ` [PR PATCH] [Updated] " jason1987d
2025-01-12 20:39 ` [PR PATCH] [Merged]: " ahesford

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=20250104222826.B567B22E57@inbox.vuxu.org \
    --to=jason1987d@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).