xapi-project / sm

39%

master: 47%

LAST BUILD ON BRANCH v2.20.0

branch: v2.20.0

CHANGE BRANCH

x

Reset

• v2.20.0
• CA-240718
• CA-247723
• CA-255945
• CA-257740
• CA-263084
• CA-264210
• CA-267032
• CA-267460
• CA-270011
• CA-273731
• CA-274584
• CA-276601
• CA-277346
• CA-292103
• CP-24279
• CP-24548
• cp-24893
• feature/REQ-562/master
• feature/REQ-718
• feature/nbd
• feature/req488/master
• marksy/CA-315152
• master
• pre-1.18
• pre-1.19.0
• pre_1.20.0
• private/bensi/CA-329841
• private/bensi/CA-329845
• private/bensi/CA-331453
• private/bensi/CA-332806
• private/bensi/CA-335178
• private/bensi/CA-335721
• private/bensi/CP-31856
• private/bensi/CP-32204
• private/bensi/CP-32988
• private/bensi/CP-33629
• private/bensi/XSI-654
• private/bensi/XSI-915
• private/bensi/XSI_570
• private/bensi/pathRefreshFix
• release/naples/lcm
• release/quebec/lcm
• team/ring0/linux-upstream
• update-ut-dependencies
• v1.10.0
• v1.11.1
• v1.11.2
• v1.11.3
• v1.13.0
• v1.14.0
• v1.14.1
• v1.16.1
• v1.18.0
• v1.19.0
• v1.20.0
• v1.21.0
• v1.22.0
• v1.23.0
• v1.24.0
• v1.25.0
• v1.26.0
• v1.27.0
• v1.28.0
• v1.29.0
• v1.30.0
• v1.31.0
• v1.32.0
• v1.33.0
• v1.34.0
• v1.35.0
• v1.36.0
• v1.37.0
• v2.0.0
• v2.1.0
• v2.10.0
• v2.11.0
• v2.12.0
• v2.13.0
• v2.14.0
• v2.15.0
• v2.16.0
• v2.16.1
• v2.17.0
• v2.18.0
• v2.19.0
• v2.2.0
• v2.2.1
• v2.2.2
• v2.2.3
• v2.21.0
• v2.22.0
• v2.23.0
• v2.24.0
• v2.25.0
• v2.26.0
• v2.27.0
• v2.28.0
• v2.29.0
• v2.29.1
• v2.3.0
• v2.30.0
• v2.31.0
• v2.32.0
• v2.33.0
• v2.34.0
• v2.35.0
• v2.36.0
• v2.37.0
• v2.38.0
• v2.39.0
• v2.4.0
• v2.40.0
• v2.5.0
• v2.6.0
• v2.7.0
• v2.8.0
• v2.9.0

Build # 923

Build Type

push

travis-ci

Committed by MarkSymsCtx

Commit Message

CA-332890: evaluate multipath on device change as well as add.

It seems that whilst in a large majority of cases a device add event
will also have all the kernel mulitpath data setup it sometimes doesn't
and we need to look at the data when we get a subsequent device change
event.

In order to not trigger the count script unneccessarily we

  * Read the CH_MULTIPATH value from the udev data, this can only have
    been set by a previous device add/change. If this is set and we are
    removing the device we need to count. If it is set for any other
    event, then we have already performed a path count so skip to end.
  * If a device add/change event is received, check the DM table to
    see if this is a multipath device. If it is then set the CH_MULTIPATH
    variable and count.

Signed-off-by: Mark Syms <mark.syms@citrix.com>

Run Details

1015 of 6313 branches covered (16.08%)

8619 of 21947 relevant lines covered (39.27%)

0.39 hits per line