fix: use correct ticker for all peers ping

[iurimatias]

Description

PR to trigger build to test status-im/status-go#5798

[status-im-auto]

Jenkins Builds

Click to see older builds (5)

❔	Commit	#️⃣	Finished (UTC)	Duration	Platform	Result
❌	72ccd84	#1	2024-09-04 14:08:02	~4 min	macos/aarch64	📄log
❌	72ccd84	#1	2024-09-04 14:08:29	~4 min	linux-nix/x86_64	📄log
❌	72ccd84	#1	2024-09-04 14:09:11	~5 min	linux/x86_64	📄log
✔️	72ccd84	#1	2024-09-04 14:09:56	~6 min	tests/nim	📄log
❌	72ccd84	#1	2024-09-04 14:12:30	~8 min	macos/x86_64	📄log

❔	Commit	#️⃣	Finished (UTC)	Duration	Platform	Result
✔️	14a408b	#2	2024-09-04 14:20:12	~6 min	tests/nim	📄log
✔️	14a408b	#2	2024-09-04 14:20:21	~6 min	macos/aarch64	🍎dmg
✔️	14a408b	#2	2024-09-04 14:27:22	~13 min	tests/ui	📄log
✔️	14a408b	#2	2024-09-04 14:29:20	~15 min	linux-nix/x86_64	📦tgz
✔️	14a408b	#2	2024-09-04 14:29:30	~15 min	macos/x86_64	🍎dmg
✔️	14a408b	#2	2024-09-04 14:30:35	~16 min	linux/x86_64	📦tgz
✔️	14a408b	#2	2024-09-04 14:39:32	~25 min	windows/x86_64	💿exe
✔️	a9a7e71	#3	2024-09-06 16:06:25	~6 min	tests/nim	📄log
✔️	a9a7e71	#3	2024-09-06 16:09:44	~9 min	macos/aarch64	🍎dmg
✔️	a9a7e71	#3	2024-09-06 16:10:59	~10 min	macos/x86_64	🍎dmg
❌	a9a7e71	#3	2024-09-06 16:13:27	~13 min	tests/ui	📄log
✔️	a9a7e71	#3	2024-09-06 16:16:15	~16 min	linux-nix/x86_64	📦tgz
✔️	a9a7e71	#3	2024-09-06 16:17:45	~17 min	linux/x86_64	📦tgz
✔️	a9a7e71	#3	2024-09-06 16:26:19	~26 min	windows/x86_64	💿exe

[anastasiyaig]

status go cant be built

17:07:59  + make status-go
17:07:59  �[92mBuilding:�[39m status-go
17:07:59  ln: /Users/jenkins/workspace/s_macos_aarch64_package_PR-16268/vendor/status-go//.git/hooks: Not a directory
17:07:59  go: inconsistent vendoring in /Users/jenkins/workspace/s_macos_aarch64_package_PR-16268/vendor/status-go:
17:07:59  	github.com/waku-org/go-waku@v0.8.1-0.20240904134226-49eb64a27dc4: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
17:07:59  	github.com/waku-org/go-waku@v0.8.1-0.20240808103513-b96582a30bc5: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
17:07:59  
17:07:59  	To ignore the vendor directory, use -mod=readonly or -mod=mod.
17:07:59  	To sync the vendor directory, run:
17:07:59  		go mod vendor
17:07:59  make[1]: *** [statusgo-shared-library] Error 1
17:07:59  make: *** [vendor/status-go/build/bin/libstatus.dylib] Error 2

@iurimatias

[iurimatias]

@anastasiyaig yeah I need to update, will do shortly

[chaitanyaprem]

status go cant be built

17:07:59  + make status-go
17:07:59  �[92mBuilding:�[39m status-go
17:07:59  ln: /Users/jenkins/workspace/s_macos_aarch64_package_PR-16268/vendor/status-go//.git/hooks: Not a directory
17:07:59  go: inconsistent vendoring in /Users/jenkins/workspace/s_macos_aarch64_package_PR-16268/vendor/status-go:
17:07:59  	github.com/waku-org/go-waku@v0.8.1-0.20240904134226-49eb64a27dc4: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
17:07:59  	github.com/waku-org/go-waku@v0.8.1-0.20240808103513-b96582a30bc5: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod
17:07:59  
17:07:59  	To ignore the vendor directory, use -mod=readonly or -mod=mod.
17:07:59  	To sync the vendor directory, run:
17:07:59  		go mod vendor
17:07:59  make[1]: *** [statusgo-shared-library] Error 1
17:07:59  make: *** [vendor/status-go/build/bin/libstatus.dylib] Error 2

@iurimatias

i have pushed updates to status-go PR. can you take in the new version?
status-im/status-go@b2886ef

[iurimatias]

@anastasiyaig now it's updated

[anastasiyaig]

it works to me, no reconnections within 30 minutes, peers count is around 19-28 , stable

[virginiabalducci]

Looks good to me, peer count has been increasing until reaching 21-23 and remaining stable during the 30 minutes of testing

[jrainville]

I'm currently running this build as my main account to check if maybe this issue was related to the memory issue discussed here: #16214

I've been running the build for almost an hour and the memory used is around 1.9GB, which is standard.

I have seen spikes where it went up to 4GB, but it went back down.

I'll keep monitoring, but this is promising. It would make sense that the memory problem was related, because each time peers are reset, we do a new store node fetch, and considering we have a hundred channels, that's a lot of data being received and parsed.

[jrainville]

It's now been running for about 4 hours and the memory is stable around 3.4GB. It's still pretty high, but it used to be "stable" around 5GB before.
It has spiked once when I came back from lunch, but that's because the laptop went to sleep.
Before, it could get up to 7GB and more

I would then recommmend to ship it!!!