[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#720063: RFS: capnproto/0.2.0-1 [ITP] -- Tool for working with the Cap'n Proto data interchange format



Ah, the Debug.Log hang seems like it might relate to a missing
/proc/self/exe symlink -- probably because I didn't mount the /proc
filesystem. Here's the relevant bit of strace output:

[pid  7463] write(3, "[       OK ] Exception.Exception"..., 143 <unfinished ...>
[pid 13045] readlink("/proc/self/exe",  <unfinished ...>
[pid  7463] <... write resumed> )       = 143
[pid 13045] <... readlink resumed> 0x7fff11d94460, 512) = -1 ENOENT
(No such file or directory)
[pid  7463] read(0, "[ RUN      ] Debug.Log\n", 8192) = 23
[pid  7463] write(1, "[ RUN      ] Debug.Log\n", 23[ RUN      ] Debug.Log
) = 23
[pid 13045] futex(0x2aaaabaa75e0, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid  7463] write(3, "[ RUN      ] Debug.Log\n", 23) = 23
[pid  7463] read(0,

The last two futex(...) & read(...) calls wait around forever.

Might be a silly question, but I'm guessing it's standard practice to
mount /proc when doing these chrooted builds?

And assuming the build servers are using a chroot, can I also assume
they will mount procfs on /proc prior to executing a build?

Either way, I'm going to mount /proc in my chroot & try again.


On Sun, Aug 18, 2013 at 1:30 PM, Tom Lee <debian@tomlee.co> wrote:
> Interesting, I'm seeing the Debug.Log tests hang when building in a
> wheezy chroot.
>
> I'll play around with this a little more & try to reproduce in sid
> with pbuilder. I'll follow up when I have more info.
>
> Thanks for trying this out!
>
> On Sun, Aug 18, 2013 at 1:14 PM, Vincent Bernat <bernat@debian.org> wrote:
>>  ❦ 18 août 2013 20:29 CEST, Vincent Bernat <bernat@debian.org> :
>>
>>>> Weird -- I'll try that out myself & see if I can figure out what's
>>>> going wrong.
>>>
>>> I'll try again at home, I am on my laptop currently with limited
>>> Internet access. Did you use something like pbuilder/cowbuilder?  If
>>> not, you should. But I don't see how this could lead to such a
>>> backtrace.
>>
>> Same problem at home. I am building on AMD64. Please try in a sid
>> pbuilder if you didn't.
>> --
>> Use data arrays to avoid repetitive control sequences.
>>             - The Elements of Programming Style (Kernighan & Plauger)
>
>
>
> --
> Tom Lee / http://tomlee.co / @tglee



-- 
Tom Lee / http://tomlee.co / @tglee


Reply to: