Hey Giacomo, Yes, it's intended.
We're still planning to replace Kokoro with the GCB system (I'd actually like to call it Kokoro v2, as I'm rather fond of the name :) ). We treated the time GCB was on Gerrit as an experiment to see if it did what we wanted. By and large, it does. The outstanding problem is it'd trigger on every patchset submitted to Gerrit. Most of the patchsets submitted to Gerrit are just things like trivial changes due to rebases, and contributors altering code in response to reviewer comments. It's a really inefficient way to do it (not to mention costly), so we turned it off and fell back on Kokoro for the time being . It's currently on my TODO list to write a better trigger that works the same way as Kokoro does (triggering on a Maintainer+1 vote), but that's on the back-burner until gem5-20 is out the door. Hopefully I will return to this soon. Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Tue, May 12, 2020 at 7:10 AM Giacomo Travaglini < [email protected]> wrote: > Hi Bobby, > > > > It seems like we are just using kokoro now as CI platform. Is this > intended? > > (What happened with GCB?) > > > > Kind Regards > > > > Giacomo > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > _______________________________________________ gem5-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
