You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
changed the title [-][x86-64 macOS] PortSysinfoTest.sysinfo_test_sysinfo_set_limit_ADDRESS_SPACE failure[/-][+][x86-64 macOS] PortSysinfoTest sysinfo_set_limit_ADDRESS_SPACE failure[/+]on Mar 9, 2023
changed the title [-][x86-64 macOS] PortSysinfoTest sysinfo_set_limit_ADDRESS_SPACE failure[/-][+][MacOS] PortSysinfoTest sysinfo_set_limit_ADDRESS_SPACE failure[/+]on Mar 9, 2023
changed the title [-][MacOS] PortSysinfoTest sysinfo_set_limit_ADDRESS_SPACE failure[/-][+][MacOS] PortSysinfoTest sysinfo_set_limit_ADDRESS_SPACE fails[/+]on Mar 9, 2023
#6910 introduces the failure documented in this issue. @knn-k@AdamBrousseau Shall we revert #6910 until this failure is fixed? Unless we already know how to fix it.
We needed to upgrade the Azure macOS by #6910 because the macOS-10.15 environment will be removed by the end of this month.
See actions/runner-images#5583 (comment)
Can we move to macos-11 (#6930) or macos-12 (#6929)? Preferably macos-12 if both work. If neither work, we can look at the test failure. @AdamBrousseau What's the best way to debug in the Azure environment?
macos-11 (#6930) worked but the same failure was seen with macos-12 (#6929). Can we temporarily move to macos-11? Meanwhile, we can fix the failure before transitioning back to macos-latest.
Do you think it's code, or something machine side?
This machine is shared with the OpenJ9 farm. We can disable the sharing again to see if that helps? Also, we have Mac 12 and Mac 11 we could borrow to try if you think it is OS version.
Activity
[-][x86-64 macOS] PortSysinfoTest.sysinfo_test_sysinfo_set_limit_ADDRESS_SPACE failure[/-][+][x86-64 macOS] PortSysinfoTest sysinfo_set_limit_ADDRESS_SPACE failure[/+][-][x86-64 macOS] PortSysinfoTest sysinfo_set_limit_ADDRESS_SPACE failure[/-][+][MacOS] PortSysinfoTest sysinfo_set_limit_ADDRESS_SPACE failure[/+][-][MacOS] PortSysinfoTest sysinfo_set_limit_ADDRESS_SPACE failure[/-][+][MacOS] PortSysinfoTest sysinfo_set_limit_ADDRESS_SPACE fails[/+]babsingh commentedon Mar 17, 2023
The test only fails in the AZURE MacOS x86 builds: https://dev.azure.com/eclipse-omr/omr/_build?definitionId=1&_a=summary.
But, the test consistently passes in the JENKINS MacOS x86 builds: https://ci.eclipse.org/omr/job/PullRequest-osx_x86-64/.
@AdamBrousseau @0xdaryl Has there been any recent changes to the MacOS setup on AZURE which may caused this failure?
AdamBrousseau commentedon Mar 17, 2023
#6910
babsingh commentedon Mar 17, 2023
#6910 introduces the failure documented in this issue. @knn-k @AdamBrousseau Shall we revert #6910 until this failure is fixed? Unless we already know how to fix it.
knn-k commentedon Mar 17, 2023
We needed to upgrade the Azure macOS by #6910 because the macOS-10.15 environment will be removed by the end of this month.
See actions/runner-images#5583 (comment)
Change Azure x64 build to macOS-12
Change Azure x64 build to macOS-11
babsingh commentedon Mar 17, 2023
Re actions/runner-images#5583 (comment):
Can we move to macos-11 (#6930) or macos-12 (#6929)? Preferably macos-12 if both work. If neither work, we can look at the test failure. @AdamBrousseau What's the best way to debug in the Azure environment?
babsingh commentedon Mar 17, 2023
macos-11 (#6930) worked but the same failure was seen with macos-12 (#6929). Can we temporarily move to macos-11? Meanwhile, we can fix the failure before transitioning back to macos-latest.
knn-k commentedon Mar 17, 2023
I agree with switching to another macOS version that is available in Azure until we find what to do with sysinfo_set_limit_ADDRESS_SPACE.
knn-k commentedon Mar 18, 2023
@AdamBrousseau Do you have any concern for #6930?
knn-k commentedon Jul 3, 2023
This test failed in https://ci.eclipse.org/omr/job/PullRequest-osx_aarch64/89/ on mac11-aarch64-08.
knn-k commentedon Jul 5, 2023
The test failed again in https://ci.eclipse.org/omr/job/PullRequest-osx_aarch64/90/ on mac13-aarch64-08.
knn-k commentedon Jul 20, 2023
This test is failing consistently on mac13-aarch64-08 these days.
AdamBrousseau commentedon Jul 20, 2023
Do you think it's code, or something machine side?
This machine is shared with the OpenJ9 farm. We can disable the sharing again to see if that helps? Also, we have Mac 12 and Mac 11 we could borrow to try if you think it is OS version.
knn-k commentedon Jul 20, 2023
I opened PR #7069 as a fix for AArch64 macOS.
It seems 300,000 bytes is too small as the limit value on AArch64 macOS 13.
This issue was originally reported against x86-64 macOS, but I don't know what was the problem at that time.
knn-k commentedon Jul 21, 2023
PR #7069 has been merged. Running the PortSysinfoTest on mac13-aarch64-08 should be OK now.
knn-k commentedon Jul 21, 2023
The PortSysinfoTest fails on x86-64 macOS when I change the OS version in Azure build to
macOS-latest.See PR #7070 and its test output https://dev.azure.com/eclipse-omr/omr/_build/results?buildId=7815&view=logs&jobId=aa2fd561-a338-5537-45ee-49ae22aea958
I opened PR #7071 to change the limit value for the test also on x86-64 macOS.
babsingh commentedon Jul 21, 2023
Fixed by