Skip to content

Updated CONTRIBUTING.MD for new package name and environment variables #930

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

Merged
merged 4 commits into from
Oct 26, 2020

Conversation

DevJPM
Copy link
Contributor

@DevJPM DevJPM commented Oct 17, 2020

When I tried to execute the instructions in CONTRIBUTING.MD I noticed that they actually don't work out of the box.

First, apparently the coresimd package had been renamed at some point but the contributing.md was not updated, I fixed that.

Additionally apparently since this documentation was written there was an update on how tests are invoked now requiring specific environment variables. I have added text to explain which those are and what they need to say to make cargo and rustc happy.

The on-boarding test instructions were out of date and pointed to the wrong package which no longer is called `coresimd` but rather `core_arch`.

Additionally added text to explain how to handle the environment variables. The source for them was [this issue](rust-lang#875).
@rust-highfive
Copy link

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Amanieu (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

Fixed the name of the flags environment variable name and added quotation marks as they are necessary
@Amanieu
Copy link
Member

Amanieu commented Oct 18, 2020

I would actually recommend using TARGET=<target> ci/run.sh to run the tests instead, it tends to work better in practice.

Rewrote the introduction to mainly talk about ci/run.sh and moved the prior instructions for "manual" test execution to the end for those unable to run ci/run.sh or wanting to run only specific tests
Added a reference to issue 931 to explain why the manual codegen tests may fail
@Amanieu Amanieu merged commit ece43e9 into rust-lang:master Oct 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants