From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: selftests: mptcp: print extra msg in chk_csum_nr: Tests Results
Date: Tue, 15 Mar 2022 08:08:38 +0000 [thread overview]
Message-ID: <5ca46297-e260-4e9b-9851-dcbb8f02115c@gmail.com> (raw)
In-Reply-To: <be2f8bba76fd1a74f31e23f1fd1c5fde457e5108.1647327162.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:
- KVM Validation: normal:
- Success! ✅:
- Task: https://cirrus-ci.com/task/6750472991145984
- Summary: https://api.cirrus-ci.com/v1/artifact/task/6750472991145984/summary/summary.txt
- KVM Validation: debug:
- Unstable: 1 failed test(s): selftest_mptcp_join 🔴:
- Task: https://cirrus-ci.com/task/4511867316994048
- Summary: https://api.cirrus-ci.com/v1/artifact/task/4511867316994048/summary/summary.txt
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/3d584c2de1fc
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)
next prev parent reply other threads:[~2022-03-15 8:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 6:58 [PATCH mptcp-next v5 0/6] MP_FAIL echo and retrans Geliang Tang
2022-03-15 6:58 ` [PATCH mptcp-next v5 1/6] mptcp: use mptcp_stop_timer Geliang Tang
2022-03-15 6:58 ` [PATCH mptcp-next v5 2/6] mptcp: add data lock for sk timers Geliang Tang
2022-03-15 6:58 ` [PATCH mptcp-next v5 3/6] mptcp: add MP_FAIL response support Geliang Tang
2022-03-15 6:58 ` [PATCH mptcp-next v5 4/6] mptcp: reset subflow when MP_FAIL doesn't respond Geliang Tang
2022-03-15 6:58 ` [PATCH mptcp-next v5 5/6] selftests: mptcp: check MP_FAIL response mibs Geliang Tang
2022-03-15 6:58 ` [PATCH mptcp-next v5 6/6] selftests: mptcp: print extra msg in chk_csum_nr Geliang Tang
2022-03-15 8:08 ` MPTCP CI [this message]
2022-03-17 0:20 ` [PATCH mptcp-next v5 0/6] MP_FAIL echo and retrans Mat Martineau
2022-03-18 23:19 ` Mat Martineau
2022-03-23 17:10 ` Matthieu Baerts
-- strict thread matches above, loose matches on Subject: below --
2022-03-10 8:09 [PATCH mptcp-next v4 4/4] selftests: mptcp: print extra msg in chk_csum_nr Geliang Tang
2022-03-10 9:58 ` selftests: mptcp: print extra msg in chk_csum_nr: 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=5ca46297-e260-4e9b-9851-dcbb8f02115c@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.