-
Notifications
You must be signed in to change notification settings - Fork 38.8k
appveyor: Script improvement part II #14665
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
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
|
quick review ACK, but will test tomorrow. |
|
tACK 99d33a6 First build with the updated yaml file failed on the |
99d33a6 appveyor: Script improvement part II (Chun Kuan Lee) Pull request description: - decrease clone depth to 5 - Upgrade to python 3.7 that we can use `PYTHONUTF8` from PEP540. - Set clcache version to `v4.2.0` - Do not fetch the latest vcpkg package (The issue does not exist anymore) - Set test_bitcoin report sink and log sink to stdout and redirect stderr to NUL to drop confusing error messages that introduced by bitcoin#14146 - discard vcpkg, bench_bitcoin output - Set functional test `--failfast` flag - Make the log be as clear as possible. (Only ~100 lines) Tree-SHA512: e7e1f5c2698e8a5d15394edfb4b574508081e99ef4a353995f55657cb51e642567a128d6432a899ecae6f742494c143ac16e2e64df6c26e1e575421ee4a1df50
| - cmd: src\test_bitcoin.exe | ||
| - ps: src\bench_bitcoin.exe -evals=1 -scaling=0 | ||
| - cmd: src\test_bitcoin.exe -k stdout -e stdout 2> NUL | ||
| - cmd: src\bench_bitcoin.exe -evals=1 -scaling=0 > NUL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will hide precious debug information in case of failure?
See for example 1a7cebc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MarcoFalke No, it doesn't seem to. -k stdout is supposed to send the output to stdout anyway. I was just making sure that wasn't the problem.
PYTHONUTF8from PEP540.v4.2.0--failfastflag