From: Shetu Ayalew <shetu@mellanox.com>
To: backports@vger.kernel.org
Subject: generate backport error
Date: Mon, 1 Jun 2020 12:19:44 +0300 [thread overview]
Message-ID: <7318c1e5-fbe0-b941-f10e-ed00151a835f@mellanox.com> (raw)
Hi,
I'm trying to run the the gentree.py.
I use coccinelle 1.0.7 and the following tree -
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
with few different tags the last one was v5.7-rc3-1 (for backports
tree) and v5.7-rc3 (for the Linux tree).
and I get error:
Traceback (most recent call last):
File "./gentree.py", line 1107, in <module>
ret = _main()
File "./gentree.py", line 724, in _main
logwrite=logwrite)
File "./gentree.py", line 914, in process
kver = gen_version.kernelversion(bpid.project_dir)
File
"/.autodirect/swgwork/shetu/upstream/backports/lib/bpversion.py", line
40, in kernelversion
_check(process)
File
"/.autodirect/swgwork/shetu/upstream/backports/lib/bpversion.py", line
11, in _check
raise ExecutionError(process.returncode)
lib.bpversion.ExecutionError
To my understanding the source of the above error is the fail of the run
of the following command that the script executes:
"make --no-print-directory -C /swgwork/shetu/upstream/backport_vr
kernelversion"
The error I get is "you shouldn't run make in the backports tree, but
only in the generated output ...".
But the directory backport_vr is not under the backports tree. Moreover
I tried running make kernelversion
from backport_vr and I got the same error message. Do you familiar with
this probelm, any idea how to solve it ?
Thanks,
Shetu.
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next reply other threads:[~2020-06-01 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 9:19 Shetu Ayalew [this message]
2020-06-07 14:46 ` generate backport error Hauke Mehrtens
2020-06-08 8:15 ` Shetu Ayalew
2020-06-11 14:30 ` Hauke Mehrtens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7318c1e5-fbe0-b941-f10e-ed00151a835f@mellanox.com \
--to=shetu@mellanox.com \
--cc=backports@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).