On Mon, 2023-01-30 at 06:46 +0100, Andreas Tille wrote:
> Am Sun, Jan 29, 2023 at 10:22:24AM -0500 schrieb M. Zhou:
>
>
> Since we do not have this module[2] (yet) we should probably exclude all
> tests that need this module, right? If you think its a nice thing to
> have I would volunteer to pa
Am Sun, Jan 29, 2023 at 10:22:24AM -0500 schrieb M. Zhou:
> And Aron has uploaded pytorch to NEW.
It has cleared new quite quickly but is featuring an autopkgtest
regression[1]:
Traceback (most recent call last):
File "/tmp/autopkgtest-lxc.as10mbia/downtmp/build.o5C/src/test/run_test.py",
li
On Sun, 2023-01-29 at 09:03 +0100, Andreas Tille wrote:
>
>
> I have no idea about fmtlib but I noticed:
>
> [2022-09-04] fmtlib 9.1.0+ds1-2 MIGRATED to testing (Debian testing
> watch)
> [2022-09-04] Accepted fmtlib 9.1.0+ds1-2 (source) into unstable
> (Shengjing Zhu)
> [2022-08-27] Accepted fm
Hi,
Am Sat, Jan 28, 2023 at 03:09:47AM +0800 schrieb Aron Xu:
> On Fri, Jan 27, 2023 at 9:42 PM Andreas Tille wrote:
> >
> > So what help could I (as someone who does not know pytorch at all, just
> > maintains some packages that are depending from it) can I provide?
> >
>
> Here is the fail log
For reference, a 8 core + 16GB RAM configuration should be able to finish the
pytorch compilation timely. The build takes roughly an hour. My observation
is based on power9 -- on amd64 it should be something similar.
On Sun, 2023-01-29 at 11:09 +0800, Aron Xu wrote:
> On Fri, Jan 27, 2023 at 9:42
On Fri, Jan 27, 2023 at 9:42 PM Andreas Tille wrote:
>
> Am Fri, Jan 27, 2023 at 08:21:46PM +0800 schrieb Aron Xu:
> > On Fri, Jan 27, 2023 at 7:12 PM Andreas Tille wrote:
> > > make: *** [debian/rules:83: binary] Terminated
> > > ninja: build stopped: interrupted by user.
> > >
> > > could b
On Fri, Jan 27, 2023 at 9:42 PM Andreas Tille wrote:
>
> So what help could I (as someone who does not know pytorch at all, just
> maintains some packages that are depending from it) can I provide?
>
Here is the fail log just in case you can have a look...
/build/pytorch/build$ ninja
[1/5] Build
Feel free to break the pytorch reverse dependencies without a
transition slot -- we do not need the slot in the current status.
The rdeps are already not in testing due to RC bugs and needs
some new patchworks. Manual upload is needed for its rebuild.
On Fri, 2023-01-27 at 20:19 +0800, Aron Xu wro
Am Fri, Jan 27, 2023 at 08:21:46PM +0800 schrieb Aron Xu:
> On Fri, Jan 27, 2023 at 7:12 PM Andreas Tille wrote:
> > make: *** [debian/rules:83: binary] Terminated
> > ninja: build stopped: interrupted by user.
> >
> > could be a sign for this. Was I to naive to assume Salsa CI could
> > mana
On Fri, Jan 27, 2023 at 7:12 PM Andreas Tille wrote:
>
> BTW, I tried to switch on Salsa-CI which failed[2] and I suspect this
> might be due to insufficient memory. At least I've found references in
> Web that
>
> make: *** [debian/rules:83: binary] Terminated
> ninja: build stopped: interru
On Fri, Jan 27, 2023 at 3:48 PM Andreas Tille wrote:
>
> Hi Aron,
>
> Am Fri, Jan 27, 2023 at 02:09:05AM +0800 schrieb Aron Xu:
> >
> > The packaging work of 1.13.1[1] has started on salsa. We still have a
> > failure related to fmtlib before making the package build successfully
> > [5/1781]. Bot
BTW, I tried to switch on Salsa-CI which failed[2] and I suspect this
might be due to insufficient memory. At least I've found references in
Web that
make: *** [debian/rules:83: binary] Terminated
ninja: build stopped: interrupted by user.
could be a sign for this. Was I to naive to assume
Hi Aron,
Am Fri, Jan 27, 2023 at 02:09:05AM +0800 schrieb Aron Xu:
>
> The packaging work of 1.13.1[1] has started on salsa. We still have a
> failure related to fmtlib before making the package build successfully
> [5/1781]. Both Mo and I have limited bandwidth here and help is always
> apprecia
Hi
On Fri, Jan 27, 2023 at 1:27 AM Andreas Tille wrote:
>
> Hi,
>
> I was checking this bug log and realised, that the "Forwarded" field
> links to an old PR[1] that was merged long before this bug was filed.
> Checking upstream I realised that the Debian package is lagging behind
> upstream rel
Hi,
I was checking this bug log and realised, that the "Forwarded" field
links to an old PR[1] that was merged long before this bug was filed.
Checking upstream I realised that the Debian package is lagging behind
upstream releases.
Could someone please give a status update what might be the plan
Source: pytorch
Version: 1.12.1-1
Severity: serious
Forwarded: https://github.com/pytorch/pytorch/pull/81242
https://buildd.debian.org/status/fetch.php?pkg=pytorch&arch=amd64&ver=1.12.1-1%2Bb2&stamp=1672759960&raw=0
...
FAILED: caffe2/torch/CMakeFiles/torch_python.dir/csrc/Stream.cpp.o
/usr/bin/
16 matches
Mail list logo
