Yes that is what I found.
I can't confirm it was ever different :)

Actually I think I understand what you're saying, but I'm not positive it ever worked like you expect, but maybe it did.

I can't reproduce this locally nor on this install. What steps can I take to reproduce the issue you are seeing?

I have been trying very hard to run arcanist / pharbicator /libphutil unforked until now so I would strongly prefer not to edit any of the source code. The second issue is that this is being run as an external command since it's a drydock build step.

IIRC, the "right" thing to do here (According to that article), is to exit with 0 in all non-exception cases - i.e., even for failing / unsound / broken tests - basically, remove https://secure.phabricator.com/diffusion/ARC/browse/master/scripts/arcanist.php;ccbaee585e1a350d1ff970c30481079dc8471a7c$399 and expect exceptions whenever something is wrong.

Sorry to be a bother on this again. Today we almost got bitten bad by this again since the unsound test returns an exit code of 1 and the failure was actually a class not being loaded because the user had not upgraded arc on the machine.

Since that sounds possibly plausible, I'll confirm that timeouts end up looking like this in the UI, and repurpose this for "make timeouts readable to humans" if they do. I can dig into it some more if that turns out to be a dead end.

It should not require more than 60 seconds, but rather less than 1 second. Only the Jenkins instance running inside a Windows VM has this intermittent bug though. So it still sounds like a reasonable explanation: maybe Jenkins in Windows gets suspended if not used for some time or the VM itself is paged out on the host HW and takes forever to become responsive, who knows...

Also known as the far more hilarious CURLE_OPERATION_TIMEOUTED.

This may be cURL 28, CURLE_OPERATION_TIMEDOUT. We have a 60-second timeout on this build step. Is it possible your server requires more than 60s to acknowledge the initial request?

Awesome; thank you!

This is on a daily cron, I think you missed the update by a couple of hours. Link works OK for me now.

Hi! How can we reproduce this behavior?

Ah, makes sense.

That's because the symbols db on this install aren't always up-to-date; utils.php was updated recently, but the db still points to the old location...

Oups used ref txxx instead of fix txxxx

Thanks for the report! This was a bug.

I think that'll fix it. Thanks for the report!

we have a project that I am a member of that we are using to ensure that one of our "owners" approves the cl. We do this by using herald to automatically add that project to the reviewers. The project is a blocking reviewer.

@swisspol, the duplicate bug is already fixed by rP58cea0714bff

T10479: Harbormaster build steps are duplicated in the UI

BTW I realized I forgot to specify in the description of the task that what I'd like to know is why do the logs look like this and what is error 28? Does this come from Phabricator? Is there a lower-level log one could look at?

Actually all build plans show these duplicate steps. Is this an (unrelated) bug?

OK I just noticed this build plan as 2 duplicate steps (with the same 1.1 identifier)? That certainly shouldn't be the case. Did something get corrupted?

This is correct. It is not an available filter for logged out users.

I accidentally stumbled across the root cause for this and I think the fix is a one-liner, so it should work better after D15391.

Ok thanks. I found it very confusing.

(See also T6007). There should be a download button on lightboxed images as a workaround.

This is expected behavior, isn't it?

It's mainly the projects that I want to see as well. Although there has been talk of priorities etc. as well

In T10493#162973, @epriestley wrote:

It looks like the root problem in all of the downstream reports is that projects, specifically, are no longer readily available (although they previously weren't on emails deeper in the thread, either).

"implement Gmail in Phabricator"

asdasdasd

Well, sort of. Projects don't get set correctly with explicit column.