Hi Geliang,
On 13/10/2023 13:30, Geliang Tang wrote:
> On Fri, Oct 13, 2023 at 11:36:36AM +0200, Matthieu Baerts wrote:
>> Hi Geliang,
>>
>> On 13/10/2023 10:31, Matthieu Baerts wrote:
>>> Hi Geliang, Paolo,
>>>
>>> On 13/10/2023 07:46, Geliang Tang wrote:
>>>> v16:
>>>> - address Matt's comments in v15.
>>>
>>> Thank you for the new version! It looks good to me!
>>>
>>> Reviewed-by: Matthieu Baerts <matttbe@kernel.org>
>>
>> Mmh, I missed the errors reported by the CI:
>>
>> not ok 112 - mptcp_join: userspace pm add & remove address
>> not ok 113 - mptcp_join: userspace pm create destroy subflow
>> not ok 115 - mptcp_join: userspace pm remove initial subflow
>> not ok 116 - mptcp_join: userspace pm send RM_ADDR for ID 0
>>
>> Do you mind looking at that, please?
>
> I can't reproduce these errors. All tests passed on my side.
>
> I run this command on my Thinkpad laptop:
>
> docker run \
> -e INPUT_BUILD_SKIP_PERF=1 \
> -e INPUT_BUILD_SKIP_PACKETDRILL=1 \
> -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
> --pull always mptcp/mptcp-upstream-virtme-docker:latest \
> auto-debug
>
> And this is my .virtme-exec-run:
>
> run_selftest_one ./mptcp_join.sh -u
>
> Every tests passed.
Thank you for looking at that!
Maybe try to reproduce the issue in a loop using:
run_loop run_selftest_one ./mptcp_join.sh -u
> Is there a difference between my test environment and CI?
The public CI is very likely a slower environment that what you have on
your side. To help to simulate such environment, when the tests start
(because not needed before), I usually run 'stress-ng' in parallel:
nproc=$(nproc); nproc2=$((nproc * 2))
stress-ng --cpu "${nproc2}" --iomix "${nproc2}" --vm "${nproc2}"
--vm-bytes 1G --timeout 60m
If it is not enough, I also change the priority of the VM:
sudo renice 20 <pid of qemu>
I hope it will help!
Cheers,
Matt
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net