Hi, > : It was just a try with newer build. And no, the machine has no hardware > : failure, happens all the time with JDK 9 L - and only with Java 9 b67+ > > Uwe: perhaps you could change your JDK9 jenkins job to run but not send > emails on failures?
Unfortunately this is not so easy. It is always the same Jenkins Job, the randomization is part of the dynamic JAVA_HOME. So the mail is always sent. The only way to filter this would be to redirect it to /dev/null on the mailserver of my company, if the subject contains "-ea-" and goes to dev@lao. I already thought about that. > then at least we can still generate reports, and test new JDK builds as > they are available, but not spam the list with false errors? Maybe I have an idea. For now I reverted the JDK to 9b60 (the last working one which I still have installed). In addition, I updated the virtualization software (now VirtualBOX 5.0.0). This should speed up Windows builds because of enabled paravirtualization (HyperV; that is detected by the Windows7-Kernel) and to keep the clock more constant on MacOSX (no virtualization support in OSX, neither KVM nor HyperV - of course; we all know why!). In addition, the Windows builds can now use AVX and AVX2 (it is passed-through). Uwe --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
