/everware

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

Already on GitHub? Sign in to your account

Master is red #93

Closed
betatim opened this Issue Mar 22, 2016 · 4 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@betatim
@betatim
Owner

betatim commented Mar 22, 2016

Does someone understand the error in https://travis-ci.org/everware/everware/builds/117581374?

It looks like the build for #79 was green but when travis then built master it went red.
@betatim
Owner

betatim commented Mar 22, 2016

/cc @anaderi @astiunov
@betatim
Owner

betatim commented Mar 22, 2016

I suspect it is some kind of timeout issue or similar as #78 is now green again even though master is red.
@betatim
Owner

betatim commented Mar 22, 2016

Somewhat related, keeping hte test and hub output for the same test together would be easier if we started and stopped the hub as part of each test. For the tests in everware/tests this happens "for free" (because upstream did the work), can we add something like this to the frontend tests? Would also mean an earlier test that screws up the state of the hub doesn't effect a later one. Maybe best to create a new issue?

This was referenced Mar 23, 2016

Open
Closed
@betatim
Owner

betatim commented Mar 30, 2016

Closing this.

betatim closed this Mar 30, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment