[CRIU] GSoC 2019 application

[Vaibhav Gupta]

Hello,
I am also Facing same problem.

./zdtm.py run -a --parallel 2
./zdtm.py:21: DeprecationWarning: the imp module is deprecated in favour of
importlib; see the module's documentation for alternative uses
  import imp
make[3]: *** No rule to make target 'umount2'.  Stop.
Traceback (most recent call last):
  File "./zdtm.py", line 2304, in <module>
    tst.available()
  File "./zdtm.py", line 566, in available
    subprocess.check_call(["make", "umount2"])
  File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['make', 'umount2']' returned
non-zero exit status 2.
make[2]: *** [Makefile:23: zdtm] Error 1
make[1]: *** [Makefile:7: all] Error 2
make: *** [Makefile:294: test] Error 2


Let me Introduce Myself as its my mail in this mailing list.
I am Vaibhav Gupta, I am a college student and have a good command in
C,C++, python.
I am very new to CRIU, and want to contribute in it.

I went through the start guide and could successfully build CRIU on my
system. But with 'make test', I got same error as discussed above.
The output of two commands on my system are:
.
$ make umount2
make: *** No rule to make target 'umount2'.  Stop.
.
$ make --version
GNU Make 4.2.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Vaibhav Gupta


On Fri, Mar 8, 2019 at 1:05 PM Kirill Kolyshkin <kolyshkin at gmail.com> wrote:

> On Thu, 7 Mar 2019 at 00:49, Harshavardhan Unnibhavi <hvubfoss at gmail.com>
> wrote:
>
>> Hi,
>> I have built criu. But while running tests, I get an error as follows:
>>
>> ./zdtm.py run -a --parallel 2
>> ./zdtm.py:21: DeprecationWarning: the imp module is deprecated in favour
>> of importlib; see the module's documentation for alternative uses
>>   import imp
>> make[3]: *** No rule to make target 'umount2'.  Stop.
>> Traceback (most recent call last):
>>   File "./zdtm.py", line 2304, in <module>
>>     tst.available()
>>   File "./zdtm.py", line 566, in available
>>     subprocess.check_call(["make", "umount2"])
>>   File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
>>     raise CalledProcessError(retcode, cmd)
>> subprocess.CalledProcessError: Command '['make', 'umount2']' returned
>> non-zero exit status 2.
>> Makefile:23: recipe for target 'zdtm' failed
>> make[2]: *** [zdtm] Error 1
>> Makefile:7: recipe for target 'all' failed
>> make[1]: *** [all] Error 2
>> Makefile:294: recipe for target 'test' failed
>> make: *** [test] Error 2
>>
>> Is it because of the absence of a make rule in the test/Makefile ? Will
>> adding a make target and rule for umount2 help in the Makefile?
>>
>
> make has lost of implicit rules, including something like %: %.c (meaning
> if you run "make woo" it will look for woo.c).
>
> It works for me:
>
> $ make umount2
> cc -D_GNU_SOURCE    umount2.c   -o umount2
> $ make --version
> GNU Make 4.1
> Built for x86_64-pc-linux-gnu
> Copyright (C) 1988-2014 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Can you please provide the output of the above two commands?
>
>
>>
>> Thanks,
>> Harsha
>>
>> On Thu, Mar 7, 2019 at 12:30 AM Pavel Emelianov <xemul at virtuozzo.com>
>> wrote:
>>
>>> Thank you, Radostin :) A few words from my side, inline.
>>>
>>> >> 2) Are previous contributions necessary to get selected into CRIU as
>>> >> part of GSoC?
>>> > We ask the students to have a small upstream contribution, but this is
>>> > only as a proof that you know how to clone and build CRIU, as well as
>>> > send patches or create GitHub pull requests.
>>> >
>>> > https://criu.org/Google_Summer_of_Code
>>>
>>> Yes, previous contributions are not a 'must have', but additional
>>> benefit. If you haven't played with criu previously a quick start
>>> up guide is https://criu.org/GSoC_Students_Recommendations
>>>
>>> >> 3) What are skills apart from C, are necessary for the project?
>>> > Understanding how CRIU works is an important preparation step to work
>>> on
>>> > the project. However, we do understand the complexity of the project
>>> and
>>> > the limited amount of time that contributors could invest. Thus,
>>> > reviewing the wiki pages in the "Under the hood" category might be
>>> useful.
>>> >
>>> > https://criu.org/Category:Under_the_hood
>>>
>>> Absolutely. I'd also add that knowing Linux API is often needed
>>> badly. In particular, if choosing the 'optimizing the pre-dump'
>>> task, one would need to get familiar with Linux mm API including
>>> mmap(7), contents of the /proc/{pid}/maps and pagemap.
>>>
>>> -- Pavel
>>>
>> _______________________________________________
>> CRIU mailing list
>> CRIU at openvz.org
>> https://lists.openvz.org/mailman/listinfo/criu
>>
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20190308/c6c7668b/attachment.html>