CRUD CI started to fail #36
Assignees
Labels
bug
Something isn't working
Comments
DifferentialOrange
changed the title
|
It seems that it could be related to |
DifferentialOrange
added a commit
to tarantool/crud
that referenced
this issue
Dec 2, 2022
ubuntu-latest is now ubuntu-22.04 instead of 20.04 [1]. For reasons yet unknown, setup-tarantool action not works on ubuntu-22.04 runners [2]. After the issue will be fixed, we may return back to ubuntu-latest. 1. https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/ 2. tarantool/setup-tarantool#36
DifferentialOrange
added a commit
to tarantool/crud
that referenced
this issue
Dec 2, 2022
ubuntu-latest is now ubuntu-22.04 instead of 20.04 [1]. For reasons yet unknown, setup-tarantool action not works on ubuntu-22.04 runners [2]. After the issue will be fixed, we may return back to ubuntu-latest. 1. https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/ 2. tarantool/setup-tarantool#36
2 tasks
This was referenced Dec 3, 2022
|
@DifferentialOrange Thank you for the report! You're lucky man :) Let's analyze both problems. Ubuntu Jammy and Tarantool 1.10.6We're run on Ubuntu Jammy (
There is no Ubuntu Jammy build for Tarantool 1.10.6. Tarantool 1.10.14 is the first 1.10 release with Ubuntu Jammy builds (see tarantool/tarantool#7199). The problem is that the action doesn't fail when there is no requested tarantool version. I also think that we should offer a list of available Tarantool versions for given Ubuntu versions in the README. NB: Add a test that receives an error on a non-existing version. tarantoolctl on 1.10.14Yeah, another incarnation of tarantool/tarantool#5429. I have added an explanation about 1.10.14 on Debian Bullseye (11) and Ubuntu Jammy (22.04) into that issue. We should install specific tarantool-common version here: Lines 211 to 213 in 615e8f4 NB: Add a test with 1.10.14 on It seems, we also should pin origin for all three packages to prevent a next NB: Add |
To be honest, I don't get what the question is. Are there some troubles with solving this for |
oleg-jukovec
added a commit
to tarantool/go-tarantool
that referenced
this issue
Dec 5, 2022
|
I doubt that |
DifferentialOrange
added a commit
to tarantool/crud
that referenced
this issue
Dec 6, 2022
ubuntu-latest is now ubuntu-22.04 instead of 20.04 [1]. Module CI uses older versions of Tarantool in tests (like 1.10.6 and 2.2) [2]. There is no such versions in Ubuntu 22.04 repos. So until we decide to reduce our test matrix, we will use ubuntu-20.04 for tests. Since there is at least one test pipeline that should use 20.04, we use it everywhere for consistency. 1. https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/ 2. tarantool/setup-tarantool#36
DifferentialOrange
added a commit
to tarantool/crud
that referenced
this issue
Dec 8, 2022
ubuntu-latest is now ubuntu-22.04 instead of 20.04 [1]. Module CI uses older versions of Tarantool in tests (like 1.10.6 and 2.2) [2]. There is no such versions in Ubuntu 22.04 repos. So until we decide to reduce our test matrix, we will use ubuntu-20.04 for tests. Since there is at least one test pipeline that should use 20.04, we use it everywhere for consistency. 1. https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/ 2. tarantool/setup-tarantool#36
DifferentialOrange
added a commit
to tarantool/crud
that referenced
this issue
Dec 20, 2022
ubuntu-latest is now ubuntu-22.04 instead of 20.04 [1]. Module CI uses older versions of Tarantool in tests (like 1.10.6 and 2.2) [2]. There is no such versions in Ubuntu 22.04 repos. So until we decide to reduce our test matrix, we will use ubuntu-20.04 for tests. Since there is at least one test pipeline that should use 20.04, we use it everywhere for consistency. 1. https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/ 2. tarantool/setup-tarantool#36
DifferentialOrange
added a commit
to tarantool/tracing
that referenced
this issue
Mar 17, 2023
Before this patch, Github Actions relied on old installer approach. In result, it installed Tarantool 2.6.0 instead of latest 2.8 and test run failed due to [1]. See [2] about tarantoolctl not works on latest 1.10 on Ubuntu 22.04. 1. tarantool/tarantool@09aa813 2. tarantool/setup-tarantool#36
Totktonada
added a commit
to tarantool/tuple-merger
that referenced
this issue
Mar 18, 2023
The setup-tarantool action has unresolved problems with Ubuntu Jammy, which is currently a default distro on runners provided by GitHub (`runs-on: ubuntu-latest` pulls it). See [1] for details. Let's use Ubuntu Focal for a while. [1]: tarantool/setup-tarantool#36 Fixes #33
Totktonada
added a commit
to tarantool/tuple-merger
that referenced
this issue
Mar 18, 2023
The setup-tarantool action has unresolved problems with Ubuntu Jammy, which is currently a default distro on runners provided by GitHub (`runs-on: ubuntu-latest` pulls it). See [1] for details. Let's use Ubuntu Focal for a while. [1]: tarantool/setup-tarantool#36 Fixes #33
DifferentialOrange
added a commit
to tarantool/avro-schema
that referenced
this issue
Mar 20, 2023
Bump Github Action versions to use Node 16. See [1] about tarantoolctl not works on latest 1.10 on Ubuntu 22.04. 1. tarantool/setup-tarantool#36
Totktonada
added a commit
to tarantool/smtp
that referenced
this issue
Mar 21, 2023
The problem is described in [1]: `tarantoolctl rocks` from tarantool 1.10 doesn't work on Ubuntu Jammy, when it is installed by the setup-tarantool GitHub Action. Let's use Ubuntu Focal as a temporary workaround. [1]: tarantool/setup-tarantool#36
Totktonada
added a commit
to tarantool/tuple-keydef
that referenced
this issue
Mar 21, 2023
Use Ubuntu Focal for jobs, where setup-tarantool is used, because there is known unsolved problem with Ubuntu Jammy: tarantool/setup-tarantool#36
Totktonada
added a commit
to tarantool/tuple-keydef
that referenced
this issue
Mar 21, 2023
Use Ubuntu Focal for jobs, where setup-tarantool is used, because there is known unsolved problem with Ubuntu Jammy: tarantool/setup-tarantool#36
Totktonada
added a commit
to tarantool/smtp
that referenced
this issue
Mar 21, 2023
The problem is described in [1]: `tarantoolctl rocks` from tarantool 1.10 doesn't work on Ubuntu Jammy, when it is installed by the setup-tarantool GitHub Action. Let's use Ubuntu Focal as a temporary workaround. [1]: tarantool/setup-tarantool#36
DifferentialOrange
added a commit
to tarantool/avro-schema
that referenced
this issue
Mar 24, 2023
Bump Github Action versions to use Node 16. See [1] about tarantoolctl not works on latest 1.10 on Ubuntu 22.04. 1. tarantool/setup-tarantool#36
GRISHNOV
added a commit
to tarantool/ddl
that referenced
this issue
Mar 25, 2023
Use Ubuntu Focal for jobs, where setup-tarantool is used, because there is known unsolved problem with Ubuntu Jammy [1]. 1. github.com/tarantool/setup-tarantool/issues/36
AnaNek
pushed a commit
to tarantool/ddl
that referenced
this issue
Mar 27, 2023
Use Ubuntu Focal for jobs, where setup-tarantool is used, because there is known unsolved problem with Ubuntu Jammy [1]. 1. github.com/tarantool/setup-tarantool/issues/36
DifferentialOrange
added a commit
to tarantool/avro-schema
that referenced
this issue
Mar 27, 2023
Bump Github Action versions to use Node 16. See [1] about tarantoolctl not works on latest 1.10 on Ubuntu 22.04. 1. tarantool/setup-tarantool#36
Totktonada
added a commit
that referenced
this issue
Feb 26, 2024
The action installs tarantool using the following command.
```sh
sudo apt-get install -y tarantool=${version}* tarantool-dev=${version}*
```
If there is no exactly matching version, `apt-get` installs an available
one.
For example, Ubuntu Jammy (22.04) has tarantool-2.6.0 in distro's
repository and an attempt to install a non-existing tarantool version
gives tarantool-2.6.0.
This behavior makes things especially confusing when the `ubuntu-latest`
[runner label][1] changes its meaning. For example, when `ubuntu-latest`
meant Ubuntu Focal (20.04) the action successfully installs
tarantool-1.10.6. Later, `ubuntu-latest` was updated to Ubuntu Jammy
(22.04) and the same action invocation installs 2.6.0, because there is
no 1.10.6 package for Ubuntu Jammy.
After this commit such an update doesn't lead to installation of an
unexpected tarantool version: it leads to an explicit error.
Part of #36
[1]: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#choosing-github-hosted-runners
Totktonada
added a commit
that referenced
this issue
Feb 26, 2024
Before this commit the action attempts to run `tarantool --version` even after an error during its installation. It shows 'unable to locate executable file' error after the root error that makes the report less clear for a user. Part of #36
Totktonada
added a commit
that referenced
this issue
Feb 27, 2024
The action installs tarantool using the following command.
```sh
sudo apt-get install -y tarantool=${version}* tarantool-dev=${version}*
```
If there is no exactly matching version, `apt-get` installs an available
one.
For example, Ubuntu Jammy (22.04) has tarantool-2.6.0 in distro's
repository and an attempt to install a non-existing tarantool version
gives tarantool-2.6.0.
This behavior makes things especially confusing when the `ubuntu-latest`
[runner label][1] changes its meaning. For example, when `ubuntu-latest`
meant Ubuntu Focal (20.04) the action successfully installs
tarantool-1.10.6. Later, `ubuntu-latest` was updated to Ubuntu Jammy
(22.04) and the same action invocation installs 2.6.0, because there is
no 1.10.6 package for Ubuntu Jammy.
After this commit such an update doesn't lead to installation of an
unexpected tarantool version: it leads to an explicit error.
Part of #36
[1]: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#choosing-github-hosted-runners
Totktonada
added a commit
that referenced
this issue
Feb 27, 2024
Before this commit the action attempts to run `tarantool --version` even after an error during its installation. It shows 'unable to locate executable file' error after the root error that makes the report less clear for a user. Part of #36
Totktonada
added a commit
that referenced
this issue
Feb 27, 2024
The action installs tarantool using the following command.
```sh
sudo apt-get install -y tarantool=${version}* tarantool-dev=${version}*
```
If there is no exactly matching version, `apt-get` installs an available
one.
For example, Ubuntu Jammy (22.04) has tarantool-2.6.0 in distro's
repository and an attempt to install a non-existing tarantool version
gives tarantool-2.6.0.
This behavior makes things especially confusing when the `ubuntu-latest`
[runner label][1] changes its meaning. For example, when `ubuntu-latest`
meant Ubuntu Focal (20.04) the action successfully installs
tarantool-1.10.6. Later, `ubuntu-latest` was updated to Ubuntu Jammy
(22.04) and the same action invocation installs 2.6.0, because there is
no 1.10.6 package for Ubuntu Jammy.
After this commit such an update doesn't lead to installation of an
unexpected tarantool version: it leads to an explicit error.
Part of #36
[1]: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#choosing-github-hosted-runners
Totktonada
added a commit
that referenced
this issue
Feb 27, 2024
Before this commit the action attempts to run `tarantool --version` even after an error during its installation. It shows 'unable to locate executable file' error after the root error that makes the report less clear for a user. Part of #36
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tarantool/crud CI started to fail. Last success run was two weeks ago (nothing had changed since then).
Fails reproduces both on v1 and v2. Re-running with cache removed doesn't help.
CI fails are related to two reasons (they seems independent).
Wrong version
CI installs
2.6.0instead of expected version.Example:
Examples of failed arguments:
tarantool-version: 1.10.6tarantool-version: 2.2tarantool-version: 2.3tarantool-version: 2.4tarantool-version: 2.5tarantool-version: 2.6(expected latest 2.6.x)tarantool-version: 2.7tarantool-version: 2.8Works fine:
tarantool-version: 1.10tarantool-version: 2.10tarantoolctl fatal error
tarantoolctl for successfully installed latest 1.10 not works.
Example:
It is likely that this issue is not related directly to setup action. but I don't know where to start.
Workflow example: https://github.com/tarantool/crud/actions/runs/3601117234
The text was updated successfully, but these errors were encountered: