New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 899566 link

Starred by 1 user

Issue metadata

Status: Closed
Owner:
Closed: Oct 31
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

betty, betty-arcnext, .., VMTests all fail. VMs aren't reachable?

Project Member Reported by norvez@chromium.org, Oct 28

Issue description

See for example
https://ci.chromium.org/p/chromeos/builders/luci.chromeos.general/CQ/b8931397866917630480

This breaks the CQ and the Pre-CQ, CLs can't go through

Assigning to the CI bobby. Is that the right owner?
 
I have not started looking, bouncing to the new bobby.
Owner: athilenius@chromium.org
Labels: -Pri-1 Pri-2
Still looking (I'm very confused as to what I'm reading), but it looks like an Autotest issue, might still be ours though because it was in the VMTest. Need to root-cause still, but betty-arc64-paladin is passing again.
Components: -Infra>Client>ChromeOS>CI Infra>Client>ChromeOS>Test
Owner: zamorzaev@chromium.org
Alex this look to be something in either Autotest or VMTest, can you triage please. If it looks to be infra to you (I can't really find my head from my tail in the logs) feel free to bounce it back and I'll dig more.
Is it still happening? All betty paladins look healthy to me right now.
Last run was green. While many of the failed ones during the weekend are very likely caused by this issue. I annotated them with this error message:mm_send_fd: file descriptor passing not supported.
I could only find examples with "mm_send_fd: file descriptor passing not supported" from betty-arc64-paladin from Sunday. Do you have examples from other builders?

My guess is that the issue is specific to arc64.
Yes all the 5 failed runs last Sunday are on betty-arc64-paladin.
Status: Closed (was: Assigned)
Looks like betty-arc64-paladin fully recovered.

Sign in to add a comment