test: check ctx in TestExecuteContextSystemTimeout instead of err#272
test: check ctx in TestExecuteContextSystemTimeout instead of err#272benhoyt merged 2 commits intobenhoyt:masterfrom
Conversation
|
Hmm, yes, I'd prefer we understand what's going on rather than removing the whole test. However, what about a compromise -- instead of removing the test, we change the err check to |
|
@benhoyt alright, I decided to fold under zero pressure and actually look into this: apparently it's a known quirk of Go, where the os/exec package will not forward the ContextDeadline as an err to the caller. Instead, the err will be something like process killed or even |
As mentioned in the comment, a return value of
nilinstead ofDeadlineExceededwill make the test fail, so we don't run the test on those platform. Sadly, this seems to be happening on Linux too (Arch Linux specifically), leading to failure to build and install from the AUR:For context, the build is failing after trying to run the following bash function:
Since it's failing to run on
linuxtoo and it's already skipped on the other platforms, I elected to remove the whole test altogether. Actually fixing the actual test is a bit out of my knowledge level and bandwidth at the moment.Lmk what you think 🙂