Bug#886886: ros-bond-core: FTBFS on m68k: timeout generating Python from MSG bond/Constants

2018-04-01 Thread Jochen Sprickerhof 

Hi Adrian,

did you have time to look into this already? Meanwhile ros-bond-core 
build successfully again, so I would propose to either assign this to 
qemu-m68k or close it.


Cheers Jochen

* John Paul Adrian Glaubitz  [2018-01-11 00:56]:

Hi Aaron!

On 01/11/2018 12:48 AM, Aaron M. Ucko wrote:

  [ 54%] Generating Python from MSG bond/Constants
  cd /<>/obj-m68k-linux-gnu/bond && ../catkin_generated/env_cached.sh /usr/bin/python 
/usr/lib/genpy/genmsg_py.py /<>/bond/msg/Constants.msg -Ibond:/<>/bond/msg 
-Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o 
/<>/obj-m68k-linux-gnu/devel/lib/python2.7/dist-packages/bond/msg
  E: Build killed with signal TERM after 600 minutes of inactivity


Please note that such stalls are likely to indicate a bug in qemu. In fact,
I'm rather confident that this is a qemu issue and not a problem with this
particular package as we have had similar issues in the past many times.

Also, the last successful build was on December 26th while I updated the
qemu version used on the m68k buildds with a qemu-m68k snapshot on December
28th. So, I think it's very likely that we have run into a qemu regression
here.

Either way, thanks for spotting this issue. I will look into it and will
file a qemu-m68k bug if my initial suspicion turns out to be right.

Adrian

--
.''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
 `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


signature.asc
Description: PGP signature
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#886886: ros-bond-core: FTBFS on m68k: timeout generating Python from MSG bond/Constants

2018-04-01 Thread John Paul Adrian Glaubitz 
Hi Jochen!

On 04/01/2018 01:23 PM, Jochen Sprickerhof wrote:
> did you have time to look into this already? Meanwhile ros-bond-core build 
> successfully again, so I would propose to either assign this to qemu-m68k or 
> close it.

Feel free to close this bug. It's most likely a QEMU issue that
has been fixed.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#886886: ros-bond-core: FTBFS on m68k: timeout generating Python from MSG bond/Constants

2018-01-10 Thread Aaron M. Ucko 
John Paul Adrian Glaubitz  writes:

> Hi Aaron!

Hi, Adrian.

> Either way, thanks for spotting this issue. I will look into it and will
> file a qemu-m68k bug if my initial suspicion turns out to be right.

Great, thanks.  Your hypothesis would certainly explain why this package
suddenly broke.

Meanwhile, what's your take on
https://buildd.debian.org/status/fetch.php?pkg=tinyssh=m68k=20180101-1=1515027549=0?
More qemu lossage or an actual tinyssh bug?

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#886886: ros-bond-core: FTBFS on m68k: timeout generating Python from MSG bond/Constants

2018-01-10 Thread John Paul Adrian Glaubitz 
Hi Aaron!

On 01/11/2018 12:48 AM, Aaron M. Ucko wrote:
>   [ 54%] Generating Python from MSG bond/Constants
>   cd /<>/obj-m68k-linux-gnu/bond && 
> ../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
> /<>/bond/msg/Constants.msg -Ibond:/<>/bond/msg 
> -Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o 
> /<>/obj-m68k-linux-gnu/devel/lib/python2.7/dist-packages/bond/msg
>   E: Build killed with signal TERM after 600 minutes of inactivity

Please note that such stalls are likely to indicate a bug in qemu. In fact,
I'm rather confident that this is a qemu issue and not a problem with this
particular package as we have had similar issues in the past many times.

Also, the last successful build was on December 26th while I updated the
qemu version used on the m68k buildds with a qemu-m68k snapshot on December
28th. So, I think it's very likely that we have run into a qemu regression
here.

Either way, thanks for spotting this issue. I will look into it and will
file a qemu-m68k bug if my initial suspicion turns out to be right.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#886886: ros-bond-core: FTBFS on m68k: timeout generating Python from MSG bond/Constants

2018-01-10 Thread Aaron M. Ucko 
Source: ros-bond-core
Version: 1.8.1-2
Severity: important
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: m68k

Builds of ros-bond-core 1.8.1-2 for m68k (admittedly not a release
architecture) have been failing, per the below excerpt from [1]:

  [ 54%] Generating Python from MSG bond/Constants
  cd /<>/obj-m68k-linux-gnu/bond && 
../catkin_generated/env_cached.sh /usr/bin/python /usr/lib/genpy/genmsg_py.py 
/<>/bond/msg/Constants.msg -Ibond:/<>/bond/msg 
-Istd_msgs:/usr/share/std_msgs/cmake/../msg -p bond -o 
/<>/obj-m68k-linux-gnu/devel/lib/python2.7/dist-packages/bond/msg
  E: Build killed with signal TERM after 600 minutes of inactivity

This version already received a second build attempt, so the problem
wasn't just a one-off glitch, and builds are otherwise generally
quick.  (The only other instance I see on [2] of taking more than an
hour was an m68k build of 1.7.16-3+b1 in February of 2016 that took
about 9.5 hours; most other builds were well under an hour.)

Could you please take a look?

Thanks!

[1] 
https://buildd.debian.org/status/fetch.php?pkg=ros-bond-core=m68k=1.8.1-2=1515504032=0
[2] https://buildd.debian.org/status/logs.php?pkg=ros-bond-core

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers