Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.rc > #324026 > unrolled thread

Bug#1016228: python-taskflow: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

Started byLucas Nussbaum <lucas@debian.org>
First post2022-07-29 18:50 +0200
Last post2022-08-02 23:20 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.debian.bugs.rc


Contents

  Bug#1016228: python-taskflow: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Lucas Nussbaum <lucas@debian.org> - 2022-07-29 18:50 +0200
    Processed: Bug#1016228 marked as pending in python-taskflow "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-08-02 22:40 +0200
    Bug#1016228: marked as pending in python-taskflow Thomas Goirand <zigo@debian.org> - 2022-08-02 22:40 +0200
    Bug#1016228: marked as done (python-taskflow: FTBFS: E: Build  killed with signal TERM after 150 minutes of inactivity) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-08-02 23:20 +0200

#324026 — Bug#1016228: python-taskflow: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

FromLucas Nussbaum <lucas@debian.org>
Date2022-07-29 18:50 +0200
SubjectBug#1016228: python-taskflow: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Message-ID<EOBlv-eE8j-9@gated-at.bofh.it>
Source: python-taskflow
Version: 4.6.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>   File "/usr/lib/python3/dist-packages/kombu/messaging.py", line 592, in receive
>     [callback(body, message) for callback in callbacks]
>   File "/usr/lib/python3/dist-packages/kombu/messaging.py", line 592, in <listcomp>
>     [callback(body, message) for callback in callbacks]
>   File "/<<PKGBUILDDIR>>/taskflow/engines/worker_based/dispatcher.py", line 167, in on_message
>     self._process_message(data, message, message_type)
>   File "/<<PKGBUILDDIR>>/taskflow/engines/worker_based/dispatcher.py", line 134, in _process_message
>     handler.validator(data)
>   File "/<<PKGBUILDDIR>>/taskflow/engines/worker_based/protocol.py", line 220, in validate
>     su.schema_validate(data, schema)
>   File "/<<PKGBUILDDIR>>/taskflow/utils/schema_utils.py", line 34, in schema_validate
>     jsonschema.validate(data, schema, types=_SCHEMA_TYPES)
>   File "/usr/lib/python3/dist-packages/jsonschema/validators.py", line 1055, in validate
>     validator = cls(schema, *args, **kwargs)
> TypeError: create.<locals>.Validator.__init__() got an unexpected keyword argument 'types'
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/python-taskflow_4.6.4-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

[toc] | [next] | [standalone]


#324385 — Processed: Bug#1016228 marked as pending in python-taskflow

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2022-08-02 22:40 +0200
SubjectProcessed: Bug#1016228 marked as pending in python-taskflow
Message-ID<EQ6Qh-fxTQ-1@gated-at.bofh.it>
In reply to#324026
Processing control commands:

> tag -1 pending
Bug #1016228 [src:python-taskflow] python-taskflow: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Added tag(s) pending.

-- 
1016228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016228
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#324386 — Bug#1016228: marked as pending in python-taskflow

FromThomas Goirand <zigo@debian.org>
Date2022-08-02 22:40 +0200
SubjectBug#1016228: marked as pending in python-taskflow
Message-ID<EQ6Qh-fxTQ-3@gated-at.bofh.it>
In reply to#324026
Control: tag -1 pending

Hello,

Bug #1016228 in python-taskflow reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/libs/python-taskflow/-/commit/b2aac72727e983746b42ee3f1a6fe50b4d7d04a1

------------------------------------------------------------------------
Add Adapt-to-new-jsonschema-versions.patch (Closes: #1016228).
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1016228

[toc] | [prev] | [next] | [standalone]


#324391 — Bug#1016228: marked as done (python-taskflow: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2022-08-02 23:20 +0200
SubjectBug#1016228: marked as done (python-taskflow: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Message-ID<EQ7sZ-fyno-9@gated-at.bofh.it>
In reply to#324026

[Multipart message — attachments visible in raw view] — view raw

Your message dated Tue, 02 Aug 2022 21:09:50 +0000
with message-id <E1oIz9C-00Cg4F-Jn@fasolo.debian.org>
and subject line Bug#1016228: fixed in python-taskflow 4.6.4-3
has caused the Debian Bug report #1016228,
regarding python-taskflow: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
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 owner@bugs.debian.org
immediately.)


-- 
1016228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016228
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.rc


csiph-web