[FOLIO-1453] stripes-testing build failure Created: 01/Sep/18  Updated: 12/Nov/18  Resolved: 05/Sep/18

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P1
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: ci, sprint45
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Text File yarn-error.log    
Sprint:

 Description   

Error:

RUNNING HANDLER [stripes-build : Build stripes] ********************************
fatal: [10.36.1.65]: FAILED! => {"changed": true, "cmd": "yarn install", "delta": "0:00:00.506501", "end": "2018-09-01 15:02:35.199923", "failed": true, "rc": 1, "start": "2018-09-01 15:02:34.693422", "stderr": "error An unexpected error occurred: \"https://registry.yarnpkg.com/uglify-es: connect ENETUNREACH 2400:cb00:2048:1::6810:1323:443 - Local (:::0)\".", "stderr_lines": ["error An unexpected error occurred: \"https://registry.yarnpkg.com/uglify-es: connect ENETUNREACH 2400:cb00:2048:1::6810:1323:443 - Local (:::0)\"."], "stdout": "yarn install v1.9.4\ninfo No lockfile found.\n[1/4] Resolving packages...\ninfo If you think this is a bug, please open a bug report with the information provided in \"/etc/folio/stripes/yarn-error.log\".\ninfo Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.", "stdout_lines": ["yarn install v1.9.4", "info No lockfile found.", "[1/4] Resolving packages...", "info If you think this is a bug, please open a bug report with the information provided in \"/etc/folio/stripes/yarn-error.log\".", "info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command."]}


 Comments   
Comment by Wayne Schneider [ 01/Sep/18 ]

Couldn't reproduce locally, rather surprising. Yarn error log on folio-testing: yarn-error.log

Comment by Wayne Schneider [ 01/Sep/18 ]

Logging in to folio-testing, I was able to run yarn install without errors, but it continues to fail when run from Jenkins. Latest failure is a little different:

fatal: [10.36.1.65]: FAILED! => {"changed": true, "cmd": "yarn install", "delta": "0:00:12.523570", "end": "2018-09-01 16:10:18.956764", "failed": true, "rc": 1, "start": "2018-09-01 16:10:06.433194", "stderr": "error An unexpected error occurred: \"https://registry.yarnpkg.com/uglify-es: getaddrinfo ENOTFOUND registry.yarnpkg.com registry.yarnpkg.com:443\".", "stderr_lines": ["error An unexpected error occurred: \"https://registry.yarnpkg.com/uglify-es: getaddrinfo ENOTFOUND registry.yarnpkg.com registry.yarnpkg.com:443\"."], "stdout": "yarn install v1.9.4\ninfo No lockfile found.\n[1/4] Resolving packages...\ninfo There appears to be trouble with your network connection. Retrying...\ninfo There appears to be trouble with your network connection. Retrying...\ninfo There appears to be trouble with your network connection. Retrying...\ninfo There appears to be trouble with your network connection. Retrying...\ninfo If you think this is a bug, please open a bug report with the information provided in \"/etc/folio/stripes/yarn-error.log\".\ninfo Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.", "stdout_lines": ["yarn install v1.9.4", "info No lockfile found.", "[1/4] Resolving packages...", "info There appears to be trouble with your network connection. Retrying...", "info There appears to be trouble with your network connection. Retrying...", "info There appears to be trouble with your network connection. Retrying...", "info There appears to be trouble with your network connection. Retrying...", "info If you think this is a bug, please open a bug report with the information provided in \"/etc/folio/stripes/yarn-error.log\".", "info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command."]}
Comment by Wayne Schneider [ 01/Sep/18 ]

May be a transient issue, latest build seems to be OK. Leaving this issue open for the weekend in case of recurrence.

Comment by Wayne Schneider [ 02/Sep/18 ]

Issues continued 1 Sept into 2 Sept – transient build failures with the same error. Also affected the folio-snapshot build (but not any of the Vagrant builds).

Comment by Wayne Schneider [ 05/Sep/18 ]

No more errors Monday or Tuesday, closing the issue.

Generated at Thu Feb 08 23:13:26 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.