https://issues.jenkins-ci.org/browse/JENKINS-21977 documents that the HsErrPidList file is intentionally memory mapped so that hs_err_pid files can be found easily.
Unfortunately, that means there are spurious failures when running integration tests on windows (like many of the tests in git-client-plugin). Is there a technique which can allow a test to declare that it wants all (or some) AdministrativeMonitor instances to not be initialized? I see a job configuration tag disabledAdministrativeMonitors but the comments on that tag discuss not showing results in the UI, when I think I'd need the HsErrPidList constructor to not be called when running these specific integration tests. Are there other techniques which can be used to prevent the HsErrPidList constructor from being called when it is running inside one or more tests? Are there better ways to solve this problem? -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
