Update python3-aiohttp-utils to 3.2.x

mentioned in merge request swh/devel/swh-loader-metadata!6 (merged)

I see the build for swh.core is green now. Do we still need this?

Yes, this is the debian unstable build that is failing as it provides Python 3.11.

thx. Yes, It hit me a tad later (after i submitted the question) that the green build must have been related to the buster build...

mentioned in issue #4793 (closed)

mentioned in issue #4794 (closed)

mentioned in commit swh/infra/ci-cd/debs/python3-aiohttp-utils@8f1e3954

mentioned in commit swh/infra/ci-cd/debs/python3-aiohttp-utils@5e087650

mentioned in commit ardumont/swh-jenkins-jobs@d8ccc6fa

mentioned in commit swh/infra/ci-cd/debs/python3-aiohttp-utils@28e507dc

mentioned in commit swh/infra/ci-cd/debs/python3-aiohttp-utils@2c1546fe

So I initially started the work to have jenkins build that dependency because I thought it was blocking. In the end, it was not but might as well go up to the finish line.

So it's wired in jenkins now and the version in question got debian built (and uploaded to swh debian repository).

fun fact, it was already packaged somewhere... (but not wired in jenkins).

(I should have started by looking out in pergamon like this command below).

root@pergamon:/srv/softwareheritage/repository# reprepro ls python3-aiohttp-utils
python3-aiohttp-utils |   3.1.1-1+swh~bpo91 | stretch-swh | i386, amd64
python3-aiohttp-utils | 3.2.1-1+swh1~bpo101 |  buster-swh | i386, amd64
python3-aiohttp-utils |        3.2.1-1+swh1 |         sid | i386, amd64

mentioned in commit swh/infra/ci-cd/debs/python3-aiohttp-utils@11ab03a4

mentioned in commit ardumont/swh-jenkins-jobs@5c7c7f20

mentioned in commit ardumont/swh-jenkins-jobs@703f3f26

fwiw, i've also unstuck the pipeline job for debian dependency. It was broken due to a missing { parenthesis in the groovy, hence the 2 commits above ^ (one fail, one success in order ;)

I had to rebuild it since i fixed a typo of mine in the package debian dependency (i had noticed the pipeline error the first build time around and forgot to fix it initially).

New version uploaded:

root@pergamon:/srv/softwareheritage/repository# reprepro ls python3-aiohttp-utils
python3-aiohttp-utils |    3.1.1-1+swh~bpo91 | stretch-swh | i386, amd64
python3-aiohttp-utils | 3.2.1-2+swh1~bpo10+1 |  buster-swh | i386, amd64
python3-aiohttp-utils |         3.2.1-2+swh1 |         sid | i386, amd64

So it's packaged as per the initial demand.

swh.core build is still broken (locally) but no longer for that missing dependency. It's for another reason (an api change in asyncio) [2]

I've triggered the build remotely which should break the same way [1] (it did [2]).

I've opened #4798 (closed) to track the effort.

[1] https://jenkins.softwareheritage.org/view/swh-debian%20(draft)/job/debian/job/packages/job/DCORE/job/gbp-buildpackage/267/console

[2]

=================================== FAILURES ===================================
_____________________________ test_timed_coroutine _____________________________

statsd = <swh.core.statsd.Statsd object at 0x7f6334dbfe90>

    def test_timed_coroutine(statsd):
        """
        Measure the distribution of a coroutine function's run time.

        Warning: Python >= 3.5 only.
        """
        import asyncio

        @statsd.timed("timed.test")
>       @asyncio.coroutine
E       AttributeError: module 'asyncio' has no attribute 'coroutine'

closed

mentioned in issue #4798 (closed)

added 1d of time spent

Update python3-aiohttp-utils to 3.2.x

Designs

Child items ...

Activity