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

Travis doesn't catch failing installations #20

Closed
brucellino opened this issue Nov 27, 2018 · 5 comments
Closed

Travis doesn't catch failing installations #20

brucellino opened this issue Nov 27, 2018 · 5 comments
Assignees
Labels

Comments

@brucellino
Copy link
Member

In Travis, we run the installation of a product in a container - it recently failed (see #17 ) silently. Since the installation is done in the container, Travis sees an exit 0 of docker exec, not the exit 1 of rpm -ivh

Somewhere between the python script, the rpm post we are losing the error code.

@brucellino brucellino added the bug label Nov 27, 2018
@brucellino brucellino self-assigned this Nov 27, 2018
@gwarf
Copy link
Member

gwarf commented Nov 28, 2018

@brucellino, may we try something like:
docker/compose#3379 (comment)

@gwarf
Copy link
Member

gwarf commented Nov 28, 2018

It seems it doesn't work with actual .travis.yml, need to dig more why error code is being lost.

@gwarf
Copy link
Member

gwarf commented Nov 28, 2018

So it seems that in fact the problem is that a failing postscript does not make the install fail!

[root@beeb16c596bf src]# rpm -Uvh build/RPMS/noarch/glite-info-update-endpoints-3.0.1-1.el7.noarch.rpm  ; echo $?
Preparing...                          ################################# [100%]
Updating / installing...
   1:glite-info-update-endpoints-3.0.1################################# [100%]
warning: %post(glite-info-update-endpoints-3.0.1-1.el7.noarch) scriptlet failed, exit status 1
0

@gwarf
Copy link
Member

gwarf commented Nov 28, 2018

So it's a known thing: https://bugzilla.redhat.com/show_bug.cgi?id=569930

@gwarf
Copy link
Member

gwarf commented Dec 16, 2022

Move away from Travis, not planning to hack a workaround for this right now.

@gwarf gwarf closed this as completed Dec 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants