Your message dated Thu, 07 Mar 2024 20:52:51 +0000
with message-id <e1rikjt-00f4it...@fasolo.debian.org>
and subject line Bug#1061754: fixed in python-json-log-formatter 0.5.2-3
has caused the Debian Bug report #1061754,
regarding python-json-log-formatter ftbfs with Python 3.12 as default
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1061754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-json-log-formatter
Version: 0.5.2-2
Severity: serious
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

With python3-defaults from experimental, the package fails to build:

[...]
============================= test session starts ==============================
platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.4.0
cachedir: .tox/py312/.pytest_cache
rootdir: /<<PKGBUILDDIR>>
collected 29 items

tests.py ...FF........................

=================================== FAILURES =================================== _ JSONFormatterTest.test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided _

self = <tests.JSONFormatterTest testMethod=test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided>

def test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided(self):
        logger.info('Sign up', extra={'fizz': 'bazz'})
        json_record = json.loads(log_buffer.getvalue())
        expected_fields = set([
            'message',
            'time',
            'fizz',
        ])
>       self.assertEqual(set(json_record), expected_fields)
E       AssertionError: Items in the first set but not the second:
E       'taskName'

tests.py:72: AssertionError
------------------------------ Captured log call -------------------------------
INFO     test:tests.py:65 Sign up
_ JSONFormatterTest.test_message_and_time_are_in_json_record_when_extra_is_blank _

self = <tests.JSONFormatterTest testMethod=test_message_and_time_are_in_json_record_when_extra_is_blank>

    def test_message_and_time_are_in_json_record_when_extra_is_blank(self):
        logger.info('Sign up')
        json_record = json.loads(log_buffer.getvalue())
        expected_fields = set([
            'message',
            'time',
        ])
>       self.assertEqual(set(json_record), expected_fields)
E       AssertionError: Items in the first set but not the second:
E       'taskName'

tests.py:62: AssertionError
------------------------------ Captured log call -------------------------------
INFO     test:tests.py:56 Sign up
=============================== warnings summary ===============================
tests.py: 28 warnings
/<<PKGBUILDDIR>>/json_log_formatter/__init__.py:123: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
    extra['time'] = datetime.utcnow()

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
=========================== short test summary info ============================ FAILED tests.py::JSONFormatterTest::test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided FAILED tests.py::JSONFormatterTest::test_message_and_time_are_in_json_record_when_extra_is_blank ================== 2 failed, 27 passed, 28 warnings in 0.17s ===================
py312: exit 1 (0.36 seconds) /<<PKGBUILDDIR>>> pytest -s tests.py pid=5939

--- End Message ---
--- Begin Message ---
Source: python-json-log-formatter
Source-Version: 0.5.2-3
Done: Colin Watson <cjwat...@debian.org>

We believe that the bug you reported is fixed in the latest version of
python-json-log-formatter, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <cjwat...@debian.org> (supplier of updated 
python-json-log-formatter package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 07 Mar 2024 19:47:05 +0000
Source: python-json-log-formatter
Architecture: source
Version: 0.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Colin Watson <cjwat...@debian.org>
Closes: 1061754
Changes:
 python-json-log-formatter (0.5.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Replace test-update-ujson.patch with upstream cherry-pick (closes:
     #1061754).
Checksums-Sha1:
 c962ee0b957c318cdc1efddab558d5b9e632790d 2429 
python-json-log-formatter_0.5.2-3.dsc
 337273fbe493d7c16dd520884a6aad3015d26479 3376 
python-json-log-formatter_0.5.2-3.debian.tar.xz
Checksums-Sha256:
 92e1db958afcabad5e041961df6ef760c89787968be025ae73afacaec6739c55 2429 
python-json-log-formatter_0.5.2-3.dsc
 ba2f45235fea1d1074569ffc934da312b6f66973304937aaaa1c998b6bbf0743 3376 
python-json-log-formatter_0.5.2-3.debian.tar.xz
Files:
 bf1a26bc1f0b32678acfd086343d255f 2429 python optional 
python-json-log-formatter_0.5.2-3.dsc
 5e9442e1a55641c289ba3a0e30e943dc 3376 python optional 
python-json-log-formatter_0.5.2-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmXqGiwACgkQOTWH2X2G
UAsyvA/9HiMdEKnbVAwdwM1u8fhbceXEE0BvSInlz1RwK+dirTiUmGeaTI8QTyor
gDvxBKyM83LiJ2DFBvHd84/ICMRIhZIgLoQgtnkBSV7gA5DTF1L1/It2PNdY4Kgg
sdxv9c21RhM6RiG9jkUoR7qypjm88PzWaAfqsMNLJqZI+gMG5kgY/3j4dGV2zQuL
Vl5M3uJ/T/wsoswc0NHzEWlms2IPjmQyoC89wCJbCRdM/Qgo5QDcQvr1Oc3voNHi
vS70FIwnff3LFd3qJNYmQ3aRIloVB912CFxTYiqv4Y6KC595RcRFMOjPuroTkyWv
qqbMa/GexA2ogqP3lFavfusuUs2pTUlqaVpvZ3GJ0gaxQE6k5LOFyzQP236a5tAK
UJR49ZOgEQ9IcrEl1yF/7SSCaz3paaGq4MzP9A9ksACJqTO7g4mr/otL2pu/8Dyf
7EDE/V6YlkzC3TVWKMZLJISJraNQRcxY5R1NvCh14jgOwDStdk98CY7N0iPTeuIn
MEf9hD283ipeVuXi5m5ox5wL89Hqe6gXK1fyGRvLQjbIXXVDh0W5+ZdQ/ureeceT
jHmCs+h4QpJ8d1J2CqDAlK4fEJDf71AKnuOlBeQpCcp91B2FjFXFGT+x6KSspKmx
D8eeXHckUqSqF2WSvojohx3p8pghJmg6kw59bhwybmIRfnCmvp4=
=wMWp
-----END PGP SIGNATURE-----

Attachment: pgp1p5tvE3Mdr.pgp
Description: PGP signature


--- End Message ---

Reply via email to