search for: l386

...e/d/1ROo9rZ4p7-IT68jI0nnhNMOqPNpk1l0c/view?usp=sharing Noticeable places I have to mention though are (we have some large code parts uncovered): 1) I was able to place `assert(false);` on line 386 below in ICF.cpp and all our tests pass. (https://github.com/llvm-mirror/lld/blob/master/ELF/ICF.cpp#L386) 2) In Relocations.cpp, all code inside `if`: https://github.com/llvm-mirror/lld/blob/master/ELF/Relocations.cpp#L1177 Is not covered by tests. 3) MicroMipsR6Thunk::writeTo(), MicroMipsR6Thunk::addSymbols(), MicroMipsR6Thunk::getTargetInputSection() are not covered. That seems to be all major pl...

...nhNMOqPNpk1l0c/view?usp=sharing > > Noticeable places I have to mention though are (we have some large code parts uncovered): > > 1) I was able to place `assert(false);` on line 386 below in ICF.cpp and all our tests pass. > (https://github.com/llvm-mirror/lld/blob/master/ELF/ICF.cpp#L386) > > 2) In Relocations.cpp, all code inside `if`: > https://github.com/llvm-mirror/lld/blob/master/ELF/Relocations.cpp#L1177 > Is not covered by tests. > > 3) MicroMipsR6Thunk::writeTo(), MicroMipsR6Thunk::addSymbols(), > MicroMipsR6Thunk::getTargetInputSection() are not covere...

I have read about "system() not using a shell on Windows" on the help page many times before but never understood what it means technically. Please forgive my ignorance. I still do not understand it, but thanks a lot for the explanation anyway! I'm just curious if the full path would work in system() today. If it still would not work because today's Windows is still like Windows

...external garbage collector. To this end, disks which have not been finalized are given a special description so it should be possible to find them after a full migration has completed: https://github.com/libguestfs/libguestfs/blob/e2bafffce24cd8c0436bf887ee166a3ae2257bbb/v2v/output_openstack.ml#L386-L392 IIRC virt-v2v-wrapper is sending kill -9 to virt-v2v, which it should not do. > The fourth challenge is to limit the resources allocated to virt-v2v > during conversion, because concurrent conversions may have a huge > impact on conversion host performance. In the case of an oVirt h...

[Adding Tomas Golembiovsky] On Wed, Sep 26, 2018 at 12:11 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > Rather than jumping to a solution, can you explain what the problem > is that you're trying to solve? > > You need to do <X>, you tried virt-v2v, it doesn't do <X>, etc. > Well, that's mainly IMS related challenges. We're working on

...To > this end, disks which have not been finalized are given a special > description so it should be possible to find them after a full > migration has completed: > > > https://github.com/libguestfs/libguestfs/blob/e2bafffce24cd8c0436bf887ee166a3ae2257bbb/v2v/output_openstack.ml#L386-L392 > > IIRC virt-v2v-wrapper is sending kill -9 to virt-v2v, which it should > not do. > It's not virt-v2v-wrapper that kills virt-v2v, it's ManageIQ. We have the PID from virt-v2v-wrapper state file. What would be the preferred way to interrupt it ? > > The fourth ch...