CI build succeeds despite failure to upload
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 258
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
I've observed that [a build](https://travis-ci.org/mapbox/mason/jobs/304965873) succeeded despite the upload step failing with
```
Required library file /Users/travis/build/mapbox/mason/mason_packages/osx-x86_64/swiftshader/2017-11-20/lib/libGLESv2.dylib doesn't exist.
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Travis CI build (job 304965873) and the reported missing libGLESv2.dylib path. Trace how the upload failure is handled and why the build remains successful. Done means the CI result correctly reflects an upload failure; the payload names no source files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100