Error: write /dev/stdout: resource temporarily unavailable with yarn command

After running detox e2e tests with yarn the test reporter can’t write the test results to /dev/stdout

The error message we are receiving is:

Failed to run yarn command, error: write /dev/stdout: resource temporarily unavailable


  • Bitrise stack: Visual Studio for Mac, installed on macOS 10.14.4 (Mojave), set to the Stable channel.
  • Step: yarn@0.1 (exit code: 1) (version 0.1.1)


  • 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 and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : Every time
  • Does upgrading the build Step to the latest version help? : NO (it’s on latest version)
  • When did the issue start? : 22 April 2020

Local reproduction

_Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what will get when it does a git clone in the clean environment! If possible please note which sections you tried._No

Build log

  detox[14523] INFO:  [AppleSimUtils.js] launched. To watch simulator logs, run:
        /usr/bin/xcrun simctl spawn EEC0D152-AD4B-405C-A2FA-03866870004E log stream --level debug --style compact --predicate 'process == "Sampension"'
detox[14523] INFO:  Features is assigned to EEC0D152-AD4B-405C-A2FA-03866870004E {"type":"iPhone 8"}
PASS e2e/features.spec.js (44.998s)
    ✓ should open features via deeplink (5325ms)
Failed to run yarn command, error: write /dev/stdout: resource temporarily unavailable
|                                                                              |
| x | yarn@0.1 (exit code: 1)                                       | 23.2 min |
| Issue tracker:        |
| Source:                      |

Hi there @DenissB :wave:

Detox is not yet one of our core supported test frameworks, and as such we are unable to provide individualized support for it. If you are able to isolate the core issue of the failure to the Bitrise environment, we will be more than happy to ensure that a development task is created to rectify the situation.

What we can do is provide guides and best practices. The guide we have for Detox is Running Detox tests on Bitrise | Bitrise DevCenter. Other than that we have some Detox related issues and solutions on Discuss and we also have this blog post: Bitrise | Testing in React Native — Jest & Detox.

Hope this helps :wink:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.