Skip to content

Conversation

eellison
Copy link
Contributor

@eellison eellison commented Apr 28, 2022

Reland of #76397 and #76493

This time I'll get it right 😢

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Apr 28, 2022

🔗 Helpful links

💊 CI failures summary and remediations

As of commit 4d46200 (more details on the Dr. CI page):

Expand to see more
  • 1/1 failures introduced in this PR

🕵️ 1 new failure recognized by patterns

The following CI failures do not appear to be due to upstream breakages

See GitHub Actions build pull / linux-xenial-py3.7-gcc7 / test (default, 1, 2, linux.2xlarge) (1/1)

Step: "Checkout PyTorch" (full log | diagnosis details | 🔁 rerun)

2022-04-28T16:52:52.8297688Z ERROR: Could not o...o 2] No such file or directory: 'requirements.txt'
2022-04-28T16:52:52.5903141Z   BUILD_ENVIRONMENT: linux-xenial-py3.7-gcc7
2022-04-28T16:52:52.5903398Z   PR_NUMBER: 76539
2022-04-28T16:52:52.5903606Z   SHA1: 4d4620011149e064492a4b3354072139ce61e808
2022-04-28T16:52:52.5903797Z   TAG: 
2022-04-28T16:52:52.5903956Z   WORKFLOW_ID: 2240685576
2022-04-28T16:52:52.5904394Z   GITHUB_TOKEN: ***
2022-04-28T16:52:52.5904583Z   GHA_WORKFLOW_JOB_ID: 
2022-04-28T16:52:52.5904772Z ##[endgroup]
2022-04-28T16:52:52.5930760Z + python3 -m pip install -r requirements.txt
2022-04-28T16:52:52.8135413Z Defaulting to user installation because normal site-packages is not writeable
2022-04-28T16:52:52.8297688Z ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'
2022-04-28T16:52:52.8757724Z ##[error]Process completed with exit code 1.
2022-04-28T16:52:52.8768703Z ##[error]Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/ec2-user/actions-runner/_work/pytorch/pytorch/.github/actions/teardown-linux'. Did you forget to run actions/checkout before running your local action?
2022-04-28T16:52:52.8797941Z Post job cleanup.
2022-04-28T16:52:52.8910464Z Cleaning up orphan processes


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@eellison eellison requested a review from davidberard98 April 28, 2022 16:43
@facebook-github-bot facebook-github-bot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Apr 28, 2022
Copy link
Contributor

@davidberard98 davidberard98 left a comment

Choose a reason for hiding this comment

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

looks good!

Copy link
Member

@osalpekar osalpekar 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 fixing!

@eellison
Copy link
Contributor Author

@pytorchbot merge this please

@github-actions
Copy link
Contributor

Hey @eellison.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

facebook-github-bot pushed a commit that referenced this pull request Apr 30, 2022
Summary:
Reland of #76397 and #76493

This time I'll get it right 😢

Pull Request resolved: #76539
Approved by: https://github.com/davidberard98, https://github.com/osalpekar

Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/e5a55af3056fb06c2f5b570b9ed818ed8fb9366c

Reviewed By: osalpekar

Differential Revision: D36042323

fbshipit-source-id: 7eefcf6cf142bbbc9509e379e6900de84d5b33e4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla signed oncall: jit Add this issue/PR to JIT oncall triage queue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants