# Why is 'after\_success' stopped half way on OSX

**URL:** <https://travis-ci.community/t/why-is-after-success-stopped-half-way-on-osx/11522>\
**Category:** macOS\
**Created:** [April 28, 2021, 9:16am UTC](https://travis-ci.community/t/why-is-after-success-stopped-half-way-on-osx/11522 "2021-04-28T09:16:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sphaero](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/sphaero/32/6521_2.png) [@sphaero](https://travis-ci.community/u/sphaero)\
**Post date:** [April 28, 2021, 9:16am UTC](https://travis-ci.community/t/why-is-after-success-stopped-half-way-on-osx/11522/1 "2021-04-28T09:16:01Z")

</div>

I’m zipping my artefacts during ‘after\_success’ however on OSX this stops during the zip process. Anybody ideas why?

```
adding: gazebosc.app/Contents/Resources/python/lib/python3.8/site-packages/pip/_vendor/requests/ __version__.py (deflated 41%)
  adding: gazebosc.app/Contents/Resources/python/lib/python3.8/site-packages/pip/_vendor/requests/_internal_utils.py (deflated 51%)
  adding: gazebosc.app/Contents/Resources/python/lib/python3.8/site-packages/pip/_vendor/requests/adapters.py (deflated 76%)
  adding: gazebosc.app/Contents/Resour

```

You can see the full log here: [Travis CI - Test and Deploy Your Code with Confidence](https://travis-ci.org/github/hku-ect/gazebosc/jobs/768113467#L12600)

The travis.yml is [here](https://github.com/hku-ect/gazebosc/blob/master/.travis.yml):

Thanks in advance!

Arnaud

---

<div class="post-metadata">

**Author:** ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)\
**Post date:** [May 4, 2021, 6:33am UTC](https://travis-ci.community/t/why-is-after-success-stopped-half-way-on-osx/11522/2 "2021-05-04T06:33:56Z")

</div>

Hello @sphaero,

Try and cleanup `after_success` a bit, for example:

```auto
if [["${TRAVIS_BRANCH}" == "master"]]
then
 VERSION= # whatever
else
VERSION=git describe --abbrev=4 --dirty --always --tags
fi

```

This is just giving you an example, since I noticed `dirty`. If you need me to create the entire script for you, I can. It would be cleaner I feel.