1723027 - no shell on interactive build job

Status: RESOLVED FIXED

(Taskcluster :: UI, defect)

Description

[Steve Fink [:sfink] [:s:]]

The last few times I've tried an interactive shell for a spidermonkey build job, the shell has not given me a prompt. My latest example shows in its log that the task ran normally. I didn't see anything that looked like it was trying to start an interactive shell.

The payload does have features.interactive=true fwiw.

Comment 1

[Michael Froman [:mjf]]

Attachment: interactive task with empty orange banner

Comment 2

[Michael Froman [:mjf]]

I'm also seeing this. There is an empty orange banner at the top of the page. I'll include a screen shot of that. After the clicking the link to get a shell, no prompt is ever returned in the new window, just a red square (presumably a cursor). Of course you only get about 5 minutes of time to troubleshoot before the task is no longer available. Please let me know if there is additional info I can provide. This would be nice functionality to have back.

Comment 3

[John Whitlock [:jwhitlock]]

I'm not familiar with interactive debugging, but the URL for the websocket suggests they could be impacted by an expired SSL certificate (bug 1714818). You might be able to work around the issue by:

1. Viewing the live log for the running task. If you get an error viewing the live log, you might be running a docker worker with the expired SSL certificate. Sorry, I don't have the exact error message, but it contains a URL to a subdomain of taskcluster-worker.net, like eotlojqaaaaxt4t4nhirqlel4r5hggpywlxtnhckgr52h2o5.taskcluster-worker.net.
2. Go to that URL. You'll get a security warning, and the details will be that the certificate is expired
3. Accept the certificate, and try viewing the live log again
4. Try the interactive prompt again. The web socket may also use the expired SSL certificate, and you might be able to use it now.

Comment 4

[John Whitlock [:jwhitlock]]

bug 1714818 is fixed, so I'm assuming this one is fixed as well.