Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] changing sleep time + order of travis steps #413

Closed
wants to merge 14 commits into from

Conversation

benkeen
Copy link
Member

@benkeen benkeen commented May 13, 2015

There's a problem with the travis config in that sometimes the mocha tests fail, e.g.
https://travis-ci.org/apache/couchdb-fauxton/builds/62419139
https://travis-ci.org/apache/couchdb-fauxton/builds/62403433

I can reproduce this locally when Fauxton isn't running when mocha is started. This PR is trying out some different configurations like increasing the sleep time and changing the order to ensure tests run after the server has been started.

@robertkowalski
Copy link
Member

./node_modules/grunt-cli/bin/grunt dev & means the process is forked into the background and running there.

running the tests while running the other process in the background builds a special test release which will overwrite the release created by grunt dev

what are you trying to archive, the commit message does not mention the problem...?

@benkeen
Copy link
Member Author

benkeen commented May 13, 2015

Hey @robertkowalski - this is just a test PR. I'll add [WIP].

Yes, I know the & runs it in the background - I just added a comment above explaining what I'm doing.

@benkeen benkeen changed the title changing sleep time + order of travis steps [WIP] changing sleep time + order of travis steps May 13, 2015
@benkeen
Copy link
Member Author

benkeen commented May 13, 2015

Results:

  1. First attempt yields build error -npm ERR! EEXIST, symlink '../esprima/bin/esparse.js'' possibly caused by Spurious issue running tests on travis. jscs-dev/node-jscs#883. Re-running.
  2. Second runs + passes all mocha tests. So issue in 1 doesn't always occur. All NW tests are failing.
  3. Third time, there was a new error right off the bat: W: Failed to fetch http://us.archive.ubuntu.com/ubuntu/dists/precise-updates/universe/source/Sources Hash Sum mismatch
  4. Fourth: success! builds, runs fauxton, runs mocha tests, runs NW tests (which may or may not all succeed - the failing NW tests will be addressed separately)
    5: success.

@benkeen benkeen closed this May 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants