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

Tidied up scheduling UMD API forwarding test #13533

Merged

Conversation

bvaughn
Copy link
Contributor

@bvaughn bvaughn commented Sep 1, 2018

No description provided.

Copy link
Collaborator

@gaearon gaearon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

@bvaughn bvaughn merged commit 28b9289 into facebook:master Sep 1, 2018
@bvaughn bvaughn deleted the scheduler-umd-api-forwarding-test-continued branch September 1, 2018 20:05
@pull-bot
Copy link

pull-bot commented Sep 1, 2018

Fails
🚫

node` failed.

Log

Error:  { FetchError: invalid json response body at http://react.zpao.com/builds/master/_commits/bf8aa609257894c73c2546d9f01b76a72d2bb862/results.json reason: Unexpected token < in JSON at position 0
    at /home/circleci/project/node_modules/node-fetch/lib/body.js:48:31
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
  name: 'FetchError',
  message: 'invalid json response body at http://react.zpao.com/builds/master/_commits/bf8aa609257894c73c2546d9f01b76a72d2bb862/results.json reason: Unexpected token < in JSON at position 0',
  type: 'invalid-json' }

Generated by 🚫 dangerJS

jetoneza pushed a commit to jetoneza/react that referenced this pull request Jan 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants