From: Mark Wielaard <mark@klomp.org>
To: Ihor Solodrai <ihor.solodrai@pm.me>
Cc: Andrew Pinski via Gcc <gcc@gcc.gnu.org>,
bpf <bpf@vger.kernel.org>,
Cupertino Miranda <cupertino.miranda@oracle.com>,
"Jose E. Marchesi" <jose.marchesi@oracle.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Manu Bretelle <chantra@meta.com>,
Eduard Zingerman <eddyz87@gmail.com>,
Mykola Lysenko <mykolal@fb.com>,
Yonghong Song <yonghong.song@linux.dev>,
David Faust <david.faust@oracle.com>,
Andrew Pinski <pinskia@gmail.com>,
fche@elastic.org
Subject: Re: Announcement: GCC BPF is now being tested on BPF CI
Date: Fri, 17 Jan 2025 14:44:34 +0100 [thread overview]
Message-ID: <20250117134434.GC29102@gnu.wildebeest.org> (raw)
In-Reply-To: <mMhcrHuvf5fyjPwMa19kug9DHQH9yYcCJXKfaFMXhfQlKIuColex7zg7G6qpPqlfF74-IqzkhpZSlzsgvgikc-u6oQp27dNzFQAAatRaEuU=@pm.me>
Hi Ihor,
On Thu, Jan 16, 2025 at 08:44:54PM +0000, Ihor Solodrai via Gcc wrote:
> An example of successful test run (you have to login to github to see
> the logs):
> https://github.com/kernel-patches/bpf/actions/runs/12816136141/job/35736973856
>
> Currently 2513 of 4340 tests pass for GCC BPF, so a bit more than a half.
Nice. Could you make the logs public so people don't have to create a
github account? Or post the results to gcc-testresults@gcc.gnu.org so
others can easily inspect them. You can also submit them to bunsen of
course.
Thanks,
Mark
next prev parent reply other threads:[~2025-01-17 13:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 20:44 Announcement: GCC BPF is now being tested on BPF CI Ihor Solodrai
2025-01-16 22:05 ` Ihor Solodrai
2025-01-16 23:58 ` Jose E. Marchesi
2025-01-17 3:32 ` Ihor Solodrai
2025-01-17 10:44 ` Jose E. Marchesi
2025-01-17 17:55 ` Ihor Solodrai
2025-01-17 18:00 ` Sam James
2025-01-17 0:01 ` Jose E. Marchesi
2025-01-16 23:59 ` Jose E. Marchesi
2025-01-17 8:33 ` Cupertino Miranda
2025-01-17 17:56 ` Andrii Nakryiko
2025-01-17 13:44 ` Mark Wielaard [this message]
2025-01-17 18:09 ` Ihor Solodrai
-- strict thread matches above, loose matches on Subject: below --
2025-01-16 21:49 Sam James
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=20250117134434.GC29102@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chantra@meta.com \
--cc=cupertino.miranda@oracle.com \
--cc=david.faust@oracle.com \
--cc=eddyz87@gmail.com \
--cc=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=ihor.solodrai@pm.me \
--cc=jose.marchesi@oracle.com \
--cc=mykolal@fb.com \
--cc=pinskia@gmail.com \
--cc=yonghong.song@linux.dev \
/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