[fix] [test] fix testGetMetrics in ExtensibleLoadManagerImplTest.

[thetumbled]

Fixes #22871

Motivation

As #22820 set the default value of LoadBalancerMemoryResourceWeight to 0, some behavior changes resulting into the failure of org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImplTest#testGetMetrics.

Modifications

Set the value of LoadBalancerMemoryResourceWeight to 1 to pass the test.

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository:

[thetumbled]

PTAL, thanks. @heesung-sn @Demogorgon314

[thetumbled]

/pulsarbot rerun-failure-checks

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.26%. Comparing base (bbc6224) to head (0e13c30).
Report is 355 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #22864      +/-   ##
============================================
- Coverage     73.57%   73.26%   -0.31%     
+ Complexity    32624     2511   -30113     
============================================
  Files          1877     1889      +12     
  Lines        139502   141830    +2328     
  Branches      15299    15563     +264     
============================================
+ Hits         102638   103916    +1278     
- Misses        28908    29887     +979     
- Partials       7956     8027      +71     

Flag	Coverage Δ
inttests	27.24% <ø> (+2.65%)	⬆️
systests	24.85% <ø> (+0.53%)	⬆️
unittests	72.28% <ø> (-0.56%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 381 files with indirect coverage changes

[BewareMyPower]

I'm wondering why this failed test was not detected before?

[thetumbled]

I'm wondering why this failed test was not detected before?

This is a flaky test, which can be ignored when merging.

[lhotari]

LGTM. Thanks for fixing.

[heesung-sn]

Thank you for fixing this.