All of lore.kernel.org
 help / color / mirror / Atom feed
From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: bpf: exercise bpf_mptcp_sock(): Tests Results
Date: Thu, 03 Mar 2022 15:57:14 +0000	[thread overview]
Message-ID: <c69094db-16d0-7dcd-431c-7dbd64f347ed@gmail.com> (raw)
In-Reply-To: <59d5dd61358bdee3d5b1a95208461e20e006b8fe.1646320786.git.geliang.tang@suse.com>

Hi Geliang,

Thank you for your modifications, that's great!

Our CI did some validations and here is its report:

- {"code":404,"message":
  - "HTTP 404 Not Found"}:
  - Task: https://cirrus-ci.com/task/5615310962163712
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/5615310962163712/summary/summary.txt

- {"code":404,"message":
  - "HTTP 404 Not Found"}:
  - Task: https://cirrus-ci.com/task/4612997229314048
  - Summary: https://api.cirrus-ci.com/v1/artifact/task/4612997229314048/summary/summary.txt

Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/c95f5f7ff117

Please note that despite all the efforts that have been already done to have a
stable tests suite when executed on a public CI like here, it is possible some
reported issues are not due to your modifications. Still, do not hesitate to
help us improve that ;-)

Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (Tessares)

  reply	other threads:[~2022-03-03 15:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 15:22 [PATCH RESEND mptcp-next v5 0/3] new bpf_mptcp_sock() Geliang Tang
2022-03-03 15:22 ` [PATCH RESEND mptcp-next v5 1/3] Squash to "bpf: add 'bpf_mptcp_sock' structure and helper" Geliang Tang
2022-03-03 15:22 ` [PATCH RESEND mptcp-next v5 2/3] bpf: implement bpf_mptcp_sock() Geliang Tang
2022-03-03 15:52   ` Matthieu Baerts
2022-03-03 15:22 ` [PATCH RESEND mptcp-next v5 3/3] selftests: bpf: exercise bpf_mptcp_sock() Geliang Tang
2022-03-03 15:57   ` MPTCP CI [this message]
2022-03-07 13:28   ` selftests: bpf: exercise bpf_mptcp_sock(): Tests Results MPTCP CI
2022-03-03 15:25 ` [PATCH RESEND mptcp-next v5 0/3] new bpf_mptcp_sock() Matthieu Baerts
2022-03-03 15:28   ` Geliang Tang
  -- strict thread matches above, loose matches on Subject: below --
2022-03-03 14:48 [PATCH mptcp-next v5 3/3] selftests: bpf: exercise bpf_mptcp_sock() Geliang Tang
2022-03-03 15:23 ` selftests: bpf: exercise bpf_mptcp_sock(): Tests Results MPTCP CI
2022-03-03 15:28   ` Matthieu Baerts
2022-03-03 15:23 ` MPTCP CI
2022-02-24 15:21 [PATCH mptcp-next] selftests: bpf: exercise bpf_mptcp_sock() Geliang Tang
2022-02-24 16:42 ` selftests: bpf: exercise bpf_mptcp_sock(): Tests Results MPTCP CI

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=c69094db-16d0-7dcd-431c-7dbd64f347ed@gmail.com \
    --to=wpasupplicant.patchew@gmail.com \
    --cc=geliang.tang@suse.com \
    --cc=mptcp@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.