sven-lange-last commented on issue #4553: Lower minimum number of available file descriptors in action limit tests URL: https://github.com/apache/incubator-openwhisk/pull/4553#issuecomment-510047552 Running the same action container images on IBM's test system shows that we have different results here... Apparently, the number of files that can be opened (1003 or 1004) depend on the environment. ``` ibmcloud fn --apihost openwhisk.<redacted>.ibm.com --auth <redacted guest> --insecure action invoke TestFileLimitBad-Nodejs-10-nightly -p numFiles 1025 -br { "error": { "filesOpen": 1003, "filesToOpen": 1025, "message": { "code": "EMFILE", "errno": -24, "path": "/dev/zero", "syscall": "open" } } } ``` ``` ibmcloud fn --apihost openwhisk.<redacted>.ibm.com --auth <redacted guest> --insecure action invoke TestFileLimitBad-Nodejs-10-7c8461c -p numFiles 1025 -br { "error": { "filesOpen": 1003, "filesToOpen": 1025, "message": { "code": "EMFILE", "errno": -24, "path": "/dev/zero", "syscall": "open" } } } ``` ``` ibmcloud fn --apihost openwhisk.<redacted>.ibm.com --auth <redacted guest> --insecure action invoke TestFileLimitBad-Nodejs-10-16db4bb -p numFiles 1025 -br { "error": { "filesOpen": 1003, "filesToOpen": 1025, "message": { "code": "EMFILE", "errno": -24, "path": "/dev/zero", "syscall": "open" } } } ``` ``` ibmcloud fn --apihost openwhisk.<redacted>.ibm.com --auth <redacted guest> --insecure action invoke TestFileLimitBad-Nodejs-10-latest -p numFiles 1025 -br { "error": { "filesOpen": 1003, "filesToOpen": 1025, "message": { "code": "EMFILE", "errno": -24, "path": "/dev/zero", "syscall": "open" } } } ``` ``` ibmcloud fn --apihost openwhisk.<redacted>.ibm.com --auth <redacted guest> --insecure action invoke TestFileLimitBad-Nodejs-10-ac4760f -p numFiles 1025 -br { "error": { "filesOpen": 1003, "filesToOpen": 1025, "message": { "code": "EMFILE", "errno": -24, "path": "/dev/zero", "syscall": "open" } } } ```
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
