bluzi / name-db

:rocket: A multilingual collection of names from around the world
MIT License
59 stars 230 forks source link

Added ro version. #509

Closed hackmajoris closed 2 years ago

TravisBuddy commented 6 years ago

Build failed

Hey Alex, Please read the following log in order to understand the failure reason. It'll be awesome if you fix what's wrong and commit the changes.

Node.js: 8

npm test ``` > name-db@1.0.0 test /home/travis/build/bluzi/name-db > mocha name files 1) should contain valid JSON 2) should contain a lowercase name, same as the filename 3) should not have duplicate names 4) should have ISO-639-3 language codes 5) should have correct structure Translations 6) should be lowercase Sex 7) should be "m", "f" or "u" 8) should be lowercase 0 passing (51ms) 8 failing 1) name files should contain valid JSON: Error: Error in name file "alexander.json": Invalid JSON file SyntaxError: Unexpected token in JSON at position 367 at Context.it (test/test.js:16:23) 2) name files should contain a lowercase name, same as the filename: SyntaxError: Unexpected token in JSON at position 367 at JSON.parse () at Context.it (test/test.js:24:31) 3) name files should not have duplicate names: SyntaxError: Unexpected token in JSON at position 367 at JSON.parse () at Context.it (test/test.js:35:31) 4) name files should have ISO-639-3 language codes: SyntaxError: Unexpected token in JSON at position 367 at JSON.parse () at Context.it (test/test.js:47:31) 5) name files should have correct structure: Error: Error in name file "alexander.json": SyntaxError: Unexpected token in JSON at position 367 at Context.it (test/test.js:106:23) 6) Translations should be lowercase: SyntaxError: Unexpected token in JSON at position 367 at JSON.parse () at Context.it (test/test.js:116:31) 7) Sex should be "m", "f" or "u": SyntaxError: Unexpected token in JSON at position 367 at JSON.parse () at Context.it (test/test.js:131:31) 8) Sex should be lowercase: SyntaxError: Unexpected token in JSON at position 367 at JSON.parse () at Context.it (test/test.js:145:31) npm ERR! Test failed. See above for more details. ```


TravisBuddy commented 6 years ago

Hey @hackmajoris, Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: 5185f620-de94-11e8-b084-61188e6c7303
TravisBuddy commented 6 years ago

Hey @hackmajoris, Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: 80c35090-de94-11e8-b084-61188e6c7303
TravisBuddy commented 6 years ago

Hey @hackmajoris, Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: f7319cf0-de94-11e8-b084-61188e6c7303