[Mesa-dev] postmortem: a306 job fails on db410c-1 today
Looks like in configuring the runners to do !5661's nginx for getting artifacts (.qpa xml files, particularly), I forgot that I had previously used that port for passthrough caching of fd.o access to reduce egress (which has been unused since switching off of LAVA). And, after identifying the problem this afternoon, I turned off the (also unused) caching nginx on the servo runner instead of the fastboot runner, so the problem continued into the evening. We hadn't identified it in merging !5661 by apparently not ending up with any of our 3 jobs allocated to #1/7 active runners in any of the pipelines before merging. Resolution: When enabling new runner functionality, try multiple pipelines running in parallel to try to make sure that all the runners get tested. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] postmortem: arm64_test job timeouts today
On 2020-07-18 2:11 a.m., Eric Anholt wrote: > > - https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5669 would > give us twice the -j flags for our builds on fd.o's x86 runners (such > as for the arm64_test job) Landing this should be straightforward. > However, I have no solution for the general problem of "users can > merge code that causes failing container builds for others." Could we > make ci-templates not use registry-cached containers in marge-bot > pipelines, You mean something like https://gitlab.freedesktop.org/freedesktop/ci-templates/-/issues/14#note_571088 ? > and then replicate the image up to mesa/mesa somehow? This would require ci-templates enforcing that the image in the forked registry is up to date when merging. That was my original idea for the ci-templates issue above, but there was resistance. Maybe the benefit of not having to rebuild the image in the main project as well could change things though. -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and X developer ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [XDC 2020] Virtual conference + Call for Proposals extended 2 weeks more
On 7/3/20 4:41 PM, Samuel Iglesias Gonsálvez wrote: > Hi, > > In the last meeting, X.Org Foundation board has decided that XDC 2020 > will be a virtual conference, given the uncertain COVID-19 situation in > Europe by September, including the possibility of a second wave, > outbreaks and travel restrictions, either in Poland or in other > countries. > > XDC 2020 organization team agrees on this decision and it volunteered > to organize our first virtual XDC! > > We would like to announce as well that the new CFP deadline is Sunday > July 19th 2020. Don't forget to submit your talk, demo and workshop > proposals! > As approved in last board's meeting [0], CfP is extended until two weeks before the conference, or until we fill all the slots (whichever happens first). Please submit your talk proposals early! Last two years we had lots of talks about new and fresh development and we prioritized those over other kind of talks, as they had more potential for discussions and hallway track. However, this year that doesn't make too much sense, so we encourage our community to submit any talk related to open-source graphics stack, including those that focus on project status updates. Sam [0] https://www.x.org/wiki/BoardOfDirectors/MeetingSummaries/2020/07-16/ > Thanks, > > Sam > > > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev > signature.asc Description: OpenPGP digital signature ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
