runtime: [Arm64/Linux] Spurious failures to load libicu* symbols

Over the last few month when running regressions there have been sporadic failures to load symbols from libicuuc and/or libicui18n

// Cannot get symbol ucal_getKeywordValuesForLocale from libicui18n
// jitStressRegs0x400
CoreMangLib/cti/system/io/stream/StreamNull_PSC/StreamNull_PSC.sh

// Cannot get symbol u_getVersion from libicuuc
// forcerelocs
JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b55216/b55216/b55216.sh

// Cannot get symbol ucal_getKeywordValuesForLocale from libicui18n
// Nightly master dotnet/runtime#3858 (4/3/2018)
// gcServer
JIT/jit64/localloc/ehverify/eh13_small/eh13_small.sh

// Cannot get symbol ucal_getKeywordValuesForLocale from libicui18n
// Nightly master dotnet/runtime#3858 (4/3/2018)
// jitStressRegs0x2
JIT/Regression/CLR-x86-JIT/V1-M14-SP1/b119538/b119538b/b119538b.sh

Incidence rate is fairly low. Last nights regressions ran 305K coreclr tests (30 configs) on master and another 305K tests on release_2.1. There were two failures last night.

@janvorli @jkotas I am wondering if there is a race condition loading these libraries. Is some initialization locking needed?

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 17 (17 by maintainers)

Most upvoted comments

@tarekgh It is possible the OS on my machines is contaminated with unstable versions. When I get a chance I will try a clean install.

sdmaclea on Apr 10, 2018