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

Added missing period in README. #32723

Closed
wants to merge 1 commit into from
Closed

Conversation

mlacayo
Copy link

@mlacayo mlacayo commented Jan 28, 2020

No description provided.

Copy link
Contributor

@driazati driazati left a comment

Choose a reason for hiding this comment

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

Thanks for the fix!

Copy link
Contributor

@facebook-github-bot facebook-github-bot left a comment

Choose a reason for hiding this comment

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

@mlacayo has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@kostmo
Copy link
Member

kostmo commented Jan 28, 2020

💊 CircleCI build failures summary and remediations

As of commit 33438d8:

  • 1/2 broken upstream at merge base 9de3208 since Jan 28

    Please rebase on the viable/strict branch (expand for instructions)

    If your commit is newer than viable/strict, you can try basing on an older, stable commit:

    git fetch origin viable/strict
    git rebase --onto viable/strict $(git merge-base origin/master HEAD)
    

    If your commit is older than viable/strict:

    git fetch origin viable/strict
    git rebase viable/strict
    

    Check out the recency history of this "viable master" tracking branch.

  • 1/2 failures introduced in this PR

Detailed failure analysis

One may explore the probable reasons each build failed interactively on the Dr. CI website.

🕵️ 1 new failure recognized by patterns

The following build failures do not appear to be due to upstream breakage:

See CircleCI build pytorch_macos_10_13_py3_test (1/1)

Step: "Test" (full log | pattern match details)

Jan 28 13:45:26 RuntimeError: test_autograd failed!
Jan 28 13:45:26 Ran 1046 tests in 300.225s 
Jan 28 13:45:26  
Jan 28 13:45:26 FAILED (errors=1, skipped=13, expected failures=1) 
Jan 28 13:45:26  
Jan 28 13:45:26 Generating XML reports... 
Jan 28 13:45:26 Traceback (most recent call last): 
Jan 28 13:45:26   File "test/run_test.py", line 456, in <module> 
Jan 28 13:45:26     main() 
Jan 28 13:45:26   File "test/run_test.py", line 449, in main 
Jan 28 13:45:26     raise RuntimeError(message) 
Jan 28 13:45:26 RuntimeError: test_autograd failed! 
Jan 28 13:45:27 + cleanup 
Jan 28 13:45:27 + retcode=1 
Jan 28 13:45:27 + set +x 

🚧 1 upstream failure recognized by patterns:

These builds matched patterns, but were probably caused by upstream breakages:


This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions on the GitHub issue tracker.

This comment has been revised 1 time.

@facebook-github-bot
Copy link
Contributor

@mlacayo merged this pull request in 9922808.

wuhuikx pushed a commit to wuhuikx/pytorch that referenced this pull request Jan 30, 2020
Summary: Pull Request resolved: pytorch#32723

Differential Revision: D19607256

Pulled By: mlacayo

fbshipit-source-id: 2993014d4d90fa26acd5bc01ed7494cc43a29a62
ttumiel pushed a commit to ttumiel/pytorch that referenced this pull request Mar 4, 2020
Summary: Pull Request resolved: pytorch#32723

Differential Revision: D19607256

Pulled By: mlacayo

fbshipit-source-id: 2993014d4d90fa26acd5bc01ed7494cc43a29a62
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants