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

Jump to bottom

Add package symlinks to arm cross-runner build directory #20313

Closed
whesse opened this issue Aug 1, 2014 · 2 comments
Closed

Add package symlinks to arm cross-runner build directory #20313

whesse opened this issue Aug 1, 2014 · 2 comments
Assignees
@whesse
Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-not-planned Closed as we don't intend to take action on the reported issue type-task

Comments

@whesse
Copy link
Member

whesse commented Aug 1, 2014

The pkg tests do not run on the arm cross-runner because the symlinked package root is not part of the sdk that is downloaded.

Run the step that makes the package directory in the build directory on the vm-arm cross-compiled runner, and enable arm-vm in pkg.status.
@whesse
Copy link
Member Author

whesse commented Aug 1, 2014

Changed the title to: "Add package symlinks to arm cross-runner build directory".

@ricowind
Copy link
Contributor

ricowind commented Jun 2, 2015

we don't run pkg tests there

Added WontFix label.

@whesse whesse added type-task Priority-Medium area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. labels Jun 2, 2015
@whesse whesse self-assigned this Jun 2, 2015
@kevmoo kevmoo added closed-not-planned Closed as we don't intend to take action on the reported issue and removed resolution-wont_fix labels Mar 1, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@whesse whesse

Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-not-planned Closed as we don't intend to take action on the reported issue type-task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kevmoo @whesse @ricowind