New issue
Advanced search Search tips

Issue 905507 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
vapier@chromium.org
saklein@chromium.org
tcwang@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

cros tryjob -p doesn't work because of git push errors

Project Member Reported by manojgupta@chromium.org, Nov 15 
I (and my team members) were trying to use "-p" option to avoid creating bunch of CLs for testing using tryjobs. But it appears to be broken.

$ cros tryjob -p chromiumos/overlays/chromiumos-overlay:xw tael-full-tryjob 


Uploading patch chromiumos/overlays/chromiumos-overlay:xw:4cdb7c91 "xwayland: Update local sysmacros patch."
16:18:00: ERROR: cros tryjob failed before completing.
16:18:00: ERROR: return code: 1; command: git push https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay 46aadd8f1f977915137f2e34d867990f5ff45e05:refs/tryjobs/manojgupta@google.com/1542241071/xw/4cdb7c91bd170aee134496775df5bd1ab78d0f67
remote: Processing changes: refs: 1, done            
To https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay
 ! [remote rejected]         46aadd8f1f977915137f2e34d867990f5ff45e05 -> refs/tryjobs/manojgupta@google.com/1542241071/xw/4cdb7c91bd170aee134496775df5bd1ab78d0f67 (prohibited by Gerrit: not permitted: create)
error: failed to push some refs to 'https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay'

cmd=['git', 'push', u'https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay', u'46aadd8f1f977915137f2e34d867990f5ff45e05:refs/tryjobs/manojgupta@google.com/1542241071/xw/4cdb7c91bd170aee134496775df5bd1ab78d0f67'], cwd=/usr/local/google/home/manojgupta/host_migration/src/third_party/chromiumos-overlay/.git
16:18:00: ERROR: (Re-run with --debug for more details.)

Comment 1 by dgarr...@chromium.org, Nov 15

Cc: vapier@chromium.org saklein@chromium.org
Once again, I'm considering dropping -p support. It doesn't work very well, and nobody has stepped up to support it.

How much would it really impact your team to require the CLs to be uploaded to Gerrit?

Comment 2 by manojgupta@chromium.org, Nov 15 

Does not impact our work but it is often more convenient to use "-p" instead of creating multiple test CLs just to abandon them later on.

Comment 3 by dgarr...@chromium.org, Nov 15 

Well, maybe we can redo -p support at some point, make it more robust, and remove some of the limits (like no CL stacks).

Comment 4 by dgarr...@chromium.org, Nov 15

Owner: ----
Status: Untriaged (was: Assigned)

Comment 5 by vapier@chromium.org, Nov 15 

this particular failure is because we disabled the ACLs for the tryjobs ref namespace to see if anyone noticed

wrt long term prospects, i thought it was more about trying to find a way to pass metadata along to the build request.  have we ever gotten past group chats here ?  have we bounced ideas off of Chrome ops to see if they have any recommendations ?
►

Sign in to add a comment