Description of the issue
Build will suddenly fail with 1 of 2 errors at varying stages, but locally with just fastlane it will build perfectly.
For example we have 5 different schemes that are built.
Sometimes it will fail with
[!!!] (Temporary) Log Buffer Overflow - Ignoring log chunk(s). Please check what generates so much log in such a short time.
And sometimes
** ARCHIVE FAILED **
[03:58:46]: Exit status: 65
[03:58:46]: Your shell environment is not correctly configured
[03:58:46]: Instead of UTF-8 your shell uses US-ASCII
[03:58:46]: Please add the following to your '~/.bashrc':
[03:58:46]:
[03:58:46]: export LANG=en_US.UTF-8
[03:58:46]: export LANGUAGE=en_US.UTF-8
[03:58:46]: export LC_ALL=en_US.UTF-8
[03:58:46]:
[03:58:46]: You'll have to restart your shell session after updating the file.
[03:58:46]: If you are using zshell or another shell, make sure to edit the correct bash file.
[03:58:46]: For more information visit this stackoverflow answer:
[03:58:46]: https://stackoverflow.com/a/17031697/445598
Environment:
Where did the issue happen?
If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)
Which build Step causes the issue and which version of the step?
Temporary Log Overflow
+------+------------------------------------------------+-------------+
| e[32mfastlane summarye[0m |
+------+------------------------------------------------+-------------+
| Step | Action | Time (in s) |
+------+------------------------------------------------+-------------+
| 1 | Switch to setup_new_version lane | 0 |
| 2 | git status --porcelain | 0 |
| 3 | git diff | 0 |
| 4 | ensure_git_status_clean | 0 |
| 5 | increment_build_number | 6 |
| 6 | Switch to production lane | 0 |
| 7 | Switch to applications lane | 0 |
| 8 | Switch to production_deploy lane | 0 |
| 9 | Switch to build_app lane | 0 |
| 10 | match | 7 |
| 11 | Switch to provisioning_profile_specifier lane | 0 |
| 12 | gym | 430 |
| 13 | Switch to appstore_deploy lane | 0 |
| 14 | pilot | 331 |
| 15 | last_git_commit | 0 |
| 16 | slack | 0 |
| 17 | Switch to bitrise_build_test_applications lane | 0 |
| 18 | Switch to integration lane | 0 |
| 19 | Switch to applications lane | 0 |
| 20 | Switch to development_deploy lane | 0 |
| 21 | Switch to build_app lane | 0 |
| 22 | match | 6 |
| 23 | Switch to provisioning_profile_specifier lane | 0 |
| 24 | gym | 355 |
| 25 | Switch to fabric_deploy lane | 0 |
| 26 | Switch to change_log_since_last_tag lane | 0 |
| 27 | changelog_from_git_commits | 0 |
| 28 | crashlytics | 24 |
| 29 | last_git_commit | 0 |
| 30 | slack | 0 |
| 31 | Switch to beta lane | 0 |
| 32 | Switch to applications lane | 0 |
| 33 | Switch to development_deploy lane | 0 |
| 34 | Switch to build_app lane | 0 |
| 35 | match | 5 |
| 36 | Switch to provisioning_profile_specifier lane | 0 |
| đź’Ą | e[31mgyme[0m | 301 |
| 38 | slack | 0 |
+------+------------------------------------------------+-------------+
Error 65
+------+-----------------------------------------------+-------------+
| fastlane summary |
+------+-----------------------------------------------+-------------+
| Step | Action | Time (in s) |
+------+-----------------------------------------------+-------------+
| 1 | Switch to setup_new_version lane | 0 |
| 2 | git status --porcelain | 0 |
| 3 | git diff | 0 |
| 4 | ensure_git_status_clean | 0 |
| 5 | increment_build_number | 11 |
| 6 | Switch to production lane | 0 |
| 7 | Switch to applications lane | 0 |
| 8 | Switch to production_deploy lane | 0 |
| 9 | Switch to build_app lane | 0 |
| 10 | match | 8 |
| 11 | Switch to provisioning_profile_specifier lane | 0 |
| đź’Ą | gym | 374 |
| 13 | slack | 0 |
+------+-----------------------------------------------+-------------+
Reproducibility
- Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
-
Does a rebuild without caches help? (You can remove the
Cache:Pull
andCache:Push
steps temporarily to not to use the cache, or you can delete all the caches on theSettings
tab of the app. : NO - Does upgrading the build Step to the latest version help? : NO
- When did the issue start? : 2017/03/16
Other stacks
Can it be reproduced by running the build locally with our CLI ( https://www.bitrise.io/cli ), after doing a new git clone of the repository into the /tmp
directory and running the build from there with the Bitrise CLI ( https://www.bitrise.io/cli )? NO