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

#29060: Stop requiring bash in test-network.sh. Make it POSIX compliant #884

Merged
merged 2 commits into from Apr 16, 2019

Conversation

Labels
None yet
Projects
None yet
4 participants
@rl1987
Copy link
Contributor

@rl1987 rl1987 commented Apr 2, 2019

https://trac.torproject.org/projects/tor/ticket/29060

@coveralls
Copy link

@coveralls coveralls commented Apr 2, 2019

Pull Request Test Coverage Report for Build 4516

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 62.265%

Totals Coverage Status
Change from base Build 4506: 0.0%
Covered Lines: 46185
Relevant Lines: 74175

💛 - Coveralls

shift
done
CHUTNEY_PATH=$(echo "$@" | awk -F '--chutney-path ' '{sub(" .*","",$2); print $2}')
TOR_DIR=$(echo "$@" | awk -F '--tor-dir ' '{sub(" .*","",$2); print $2}')
Copy link
Contributor

@teor2345 teor2345 Apr 3, 2019

How do these awk commands handle quoted strings with spaces?

Copy link
Contributor Author

@rl1987 rl1987 Apr 3, 2019

They return the first thing that comes after e.g. --chutney-path until the whitespace character, so it this not handle paths with spaces in them properly. We're not losing any functionality here, as the script didn't know how to handle them previously either - further in the script we're suggesting the user to set CHUTNEY_PATH and TOR_DIR environment variables as workaround.

@torproject-pusher torproject-pusher merged commit a549e4f into torproject:master Apr 16, 2019
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment