From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw37451[dpdk-dev, v3, 03/10] bpf: add more logic into bpf_validate()
Date: 06 Jul 2018 00:51:22 -0700 [thread overview]
Message-ID: <0590c7$2382rq@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2720 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37451
_apply issues_
Submitter: Konstantin Ananyev <konstantin.ananyev@intel.com>
Date: 2018-04-06 18:49:35
DPDK git baseline:
Repo:dpdk-master, CommitID: 05e0eee0001cb19671eb7e8d3dd68680a695fea2
Repo:dpdk-next-eventdev, CommitID: aa9cbfc8cd1cae3e91e4741edc2aaf3d08056a39
Repo:dpdk-next-net, CommitID: 0b8b92e38cd55c68e4dc49dd597f62327798ec74
Repo:dpdk-next-crypto, CommitID: a5203e08a5e9b6ee9ffbbf4c150b7776de833b08
Repo:dpdk-next-virtio, CommitID: 9b954f9c455a76304601deb88e2df1549dc9e09a
*Repo: dpdk-master
Checking patch lib/librte_bpf/bpf_validate.c...
error: while searching for:
#include "bpf_impl.h"
/*
* dummy one for now, need more work.
--
else
bpf->stack_sz = stack_sz;
}
if (rc != 0)
RTE_BPF_LOG(ERR, "%s(%p) failed, error code: %d;\n",
__func__, bpf, rc);
return rc;
}
error: patch failed: lib/librte_bpf/bpf_validate.c:14
error: lib/librte_bpf/bpf_validate.c: patch does not apply
*Repo: dpdk-next-eventdev
Checking patch lib/librte_bpf/bpf_validate.c...
error: while searching for:
#include "bpf_impl.h"
/*
* dummy one for now, need more work.
--
else
bpf->stack_sz = stack_sz;
}
if (rc != 0)
RTE_BPF_LOG(ERR, "%s(%p) failed, error code: %d;\n",
__func__, bpf, rc);
return rc;
}
error: patch failed: lib/librte_bpf/bpf_validate.c:14
error: lib/librte_bpf/bpf_validate.c: patch does not apply
*Repo: dpdk-next-net
Checking patch lib/librte_bpf/bpf_validate.c...
error: while searching for:
#include "bpf_impl.h"
/*
* dummy one for now, need more work.
--
else
bpf->stack_sz = stack_sz;
}
if (rc != 0)
RTE_BPF_LOG(ERR, "%s(%p) failed, error code: %d;\n",
__func__, bpf, rc);
return rc;
}
error: patch failed: lib/librte_bpf/bpf_validate.c:14
error: lib/librte_bpf/bpf_validate.c: patch does not apply
*Repo: dpdk-next-crypto
Checking patch lib/librte_bpf/bpf_validate.c...
error: while searching for:
#include "bpf_impl.h"
/*
* dummy one for now, need more work.
--
else
bpf->stack_sz = stack_sz;
}
if (rc != 0)
RTE_BPF_LOG(ERR, "%s(%p) failed, error code: %d;\n",
__func__, bpf, rc);
return rc;
}
error: patch failed: lib/librte_bpf/bpf_validate.c:14
error: lib/librte_bpf/bpf_validate.c: patch does not apply
*Repo: dpdk-next-virtio
Checking patch lib/librte_bpf/bpf_validate.c...
error: while searching for:
#include "bpf_impl.h"
/*
* dummy one for now, need more work.
--
else
bpf->stack_sz = stack_sz;
}
if (rc != 0)
RTE_BPF_LOG(ERR, "%s(%p) failed, error code: %d;\n",
__func__, bpf, rc);
return rc;
}
error: patch failed: lib/librte_bpf/bpf_validate.c:14
error: lib/librte_bpf/bpf_validate.c: patch does not apply
DPDK STV team
next reply other threads:[~2018-07-06 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 7:51 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-06 6:51 sys_stv
2018-07-05 8:38 sys_stv
2018-07-05 8:32 sys_stv
2018-04-19 5:32 sys_stv
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='0590c7$2382rq@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@dpdk.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).