-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Some minor CI changes #48907
Some minor CI changes #48907
Conversation
Still missing a standard benchmark to measure the real performance. Would |
@bors: r+ Nice! We'll probably at some point want to figure out the equivalent invocation for AppVeyor, but this is certainly better than before! As for a standard benchmark as well yeah I'm fine w/ that coming later. |
📌 Commit c67e553 has been approved by |
@alexcrichton The |
Oh nice! I had no idea... |
Some minor CI changes 1. On macOS, ensure crash log printing won't error, and only real crash logs are printed. This may avoid the `find` process exiting abnormally and truncated the Travis log (I guess). 2. Print `/proc/cpuinfo` and `/proc/meminfo`. To determine if there's any variation in the reported clock rate between jobs.
Some minor CI changes 1. On macOS, ensure crash log printing won't error, and only real crash logs are printed. This may avoid the `find` process exiting abnormally and truncated the Travis log (I guess). 2. Print `/proc/cpuinfo` and `/proc/meminfo`. To determine if there's any variation in the reported clock rate between jobs.
☀️ Test successful - status-appveyor, status-travis |
On macOS, ensure crash log printing won't error, and only real crash logs are printed. This may avoid the
find
process exiting abnormally and truncated the Travis log (I guess).Print
/proc/cpuinfo
and/proc/meminfo
. To determine if there's any variation in the reported clock rate between jobs.