We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
#!watchflakes post <- pkg == "runtime/trace" && test == "" && !`panic: test timed out` && date < "2023-10-01"
greplogs -l -e 'Test killed with quit: ran too long .*\nFAIL\s+runtime/trace' --since=2022-01-01 2022-08-18T13:16:21-38edd9b/linux-arm-aws 2022-06-08T21:56:02-13f6be2/linux-arm-aws
greplogs -l -e 'Test killed with quit: ran too long .*\nFAIL\s+runtime/trace' --since=2022-01-01
(Attn @golang/runtime — note that linux/arm is a first-class port.)
linux/arm
The text was updated successfully, but these errors were encountered:
It's possible this is related to #53979. I don't think it is, but since not all of the stacks are shown in either failure, it's hard to say for sure.
Sorry, something went wrong.
I suspect @aclements was right, given that we haven't seen any more failures. Closing optimistically.
mknyszek
No branches or pull requests
greplogs -l -e 'Test killed with quit: ran too long .*\nFAIL\s+runtime/trace' --since=2022-01-01
2022-08-18T13:16:21-38edd9b/linux-arm-aws
2022-06-08T21:56:02-13f6be2/linux-arm-aws
(Attn @golang/runtime — note that
linux/arm
is a first-class port.)The text was updated successfully, but these errors were encountered: