-
Notifications
You must be signed in to change notification settings - Fork 683
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
backport a test to see if timestamps are working in aarch64 #1837
Conversation
bors try |
tryBuild failed: |
@pacak the test you're modifying currently builds for a few different platforms, but it looks like |
Those checkout failures are odd though. bors retry |
tryBuild failed: |
No, I wasn't suggesting merging this PR - I just was offering a suggestion to get rid of the other build failures to make it easier to parse the results. |
If it's important - sure, I'll see what I can do |
This seems to be passing just fine on my aarch64 target. :/ |
🤔 and the new one still fails? I guess I'll go over the new branch one more time - maybe I'm doing something stupid and just managing to get away with it on non aarch64. |
I'm going to do another clean build against your new branch just to be sure.... just to make sure something didn't get screwed up during my uptaking of your latest changes. I'll let you know shortly. |
Yeah, confirmed the other branch ( |
Hmm, it looks like AWS Graviton has a free trial right now (with a fairly high compute limit, at least for this). I wonder if you'd be able to reproduce it there? |
Probably, need to figure out what to do with it first :) |
Don't merge, this MR is to run the CI to see if we are getting the same errors as in #1744