Open hajimehoshi opened 4 years ago
Change https://golang.org/cl/243839 mentions this issue: cmd/gomobile: skip TestWriter
Do you know since when it became flaky? How often have you seen it?
I'm not seeing many (or any) previous failures on the post-submit runs (https://build.golang.org/?repo=golang.org%2fx%2fmobile). Is the test only flaky on pre-submit runs?
Is the test only flaky on pre-submit runs?
I've seen a successful case, which was rare though.
I'm not sure whether this issue is only on pre-submit or not.
Do you know since when it became flaky?
No, I don't... As of May or July, maybe?
Oh, I was misreading the build dashboard. The linux-amd64-androidemu
builder is configured run pre-submit trybots, but not post-submit builds:
Skipping it with this issue open seems reasonable to me, but let's make the skip conditional on it being the linux-amd64-androidemu
builder, so it's not skipped unnecessarily elsewhere (unless there's a need for it to be skipped elsewhere as well). I'll post this as a comment on the CL.
It turns out it's a bug in the dashboard UI rather than intentional configuration. The linux-amd64-androidemu
builder is configured to run both on pre- and post-submit builders. There's even a test case enforcing it. I'll look into fixing the UI so we can see how long this has been failing.
a bug in the dashboard UI
I've looked into it, it's not a trivial mistake, the problem happens due to insufficient data and a more complete fix would need changes to multiple components (the build dashboard and maintner API server). That'll take longer and it'll happen as part of other work to improve the dashboard UI (see #34744, #28643, etc.). /cc @toothrot
For now, I've sent a smaller patch in CL 244137 so that existing builds aren't hidden, and consider the rest as future work.
It can be previewed to see the past TestWriter
failures here.
Change https://golang.org/cl/244137 mentions this issue: app/appengine: stop hiding some tested configurations for x repos
I often see the test failure on the try bots:
Is there an issue in the test itself or in the trybots? Can we skip this test as a tentative solution?
CC @hyangah @dmitshur