-
Notifications
You must be signed in to change notification settings - Fork 18
Increase aarch64 timeout from 2m to 3m #283
Conversation
looks like that timed out, too: https://travis-ci.com/github/ClangBuiltLinux/continuous-integration/jobs/351058979 |
Hmmm my local builds aren’t timing out but it might be worth seeing if there is a significant regression in boot time from 5.7 to latest mainline. |
it may be one of the kselftests regressing in runtime. (maybe more tests were added; maybe there's an unexpected regression) |
This appears related to ClangBuiltLinux/boot-utils#20. I tested an arm64
With GCC 10.1.0, I see a similar slow down.
We should probably increase the timeout to 5m in that case. |
Interesting measurements, thanks for taking those. cc @broonie , as a heads up, it seems that maybe emulation of PAC+BTI is relatively expensive in QEMU. @nathanchance let me bump it to 5m for a CI run, then try to tighten it up once we have a run from TravisCI. |
Could probably get away with 4m but I would rather stick with 5m so that we can be absolutely sure we timed out. Additionally, I think that it is worth mentioning in the comments why we increased the timeout. If you disagree, let me know and I'll approve this. |
Changing -cpu to max in ClangBuiltLinux/boot-utils#20 for PAC+BTI emulation seems to have slowed our boot tests down. Fixes: https://github.com/ClangBuiltLinux/linux/issues/1058 Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
e59bfc8
to
570793a
Compare
Done. |
Fixes: https://github.com/ClangBuiltLinux/linux/issues/1058
Signed-off-by: Nick Desaulniers ndesaulniers@google.com