-
Notifications
You must be signed in to change notification settings - Fork 9
Revive CI #49
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
Comments
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Removed EOL distros, added new ones. Updated tarantool rpm/deb repositories to deploy to. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
It is invoked by packpack to set a version of a package. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Before this commit a debug build fails due to -Werror for me on GCC 9.1.0. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Aside of that switched from bash to sh, because we have nothing bash specific in test.sh. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
I have got the following error in Travis-CI for tarantool-1.6 repository: | The following packages have unmet dependencies: | tarantool : Depends: tarantool-common (>= 1.6.9) but it is not going to be installed | Conflicts: libtarantool-dev (< 1.6~) but 1.5.1.218.g1a69fd6-1ubuntu1 is to be installed | E: Unable to correct problems, you have held broken packages. Our 1.6 repository lack of libtarantool-dev (but have tarantool-dev) packages, don't sure why and whether it is expected. Anyway it worth to move to 1.10. Updated .tarantoolctl to reflect box.cfg option names changes between 1.6 and 1.10. Updated text/multiversioning.test.py result file, but to be honest I don't sure what is the reason of SELECT statistics change. At least those values are the same before and after the test, so I guess they are correct. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
It is invoked by packpack to set a version of a package. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Before this commit a debug build fails due to -Werror for me on GCC 9.1.0. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Aside of that switched from bash to sh, because we have nothing bash specific in test.sh. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Removed EOL distros, added new ones. Updated tarantool rpm/deb repositories to deploy to. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
I have got the following error in Travis-CI for tarantool-1.6 repository: | The following packages have unmet dependencies: | tarantool : Depends: tarantool-common (>= 1.6.9) but it is not going to be installed | Conflicts: libtarantool-dev (< 1.6~) but 1.5.1.218.g1a69fd6-1ubuntu1 is to be installed | E: Unable to correct problems, you have held broken packages. Our 1.6 repository lack of libtarantool-dev (but have tarantool-dev) packages, don't sure why and whether it is expected. Anyway it worth to move to 1.10. Updated .tarantoolctl to reflect box.cfg option names changes between 1.6 and 1.10. Updated text/multiversioning.test.py result file, but to be honest I don't sure what is the reason of SELECT statistics change. At least those values are the same before and after the test, so I guess they are correct. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
It is invoked by packpack to set a version of a package. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Before this commit a debug build fails due to -Werror for me on GCC 9.1.0. Part of #49.
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Totktonada
added a commit
that referenced
this issue
Jul 29, 2019
Aside of that switched from bash to sh, because we have nothing bash specific in test.sh. Part of #49.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: