Skip to content
Snippets Groups Projects

execute

Failed Started by
Sarah Yasonik
@syasonik
1Running with gitlab-runner 15.9.0~beta.212.g8ccc65e7 (8ccc65e7)
2 on green-2.private.runners-manager.gitlab.com/gitlab.com/gitlab-org GaSD-S1F, system ID: s_5651e5b5643b
3 feature flags: FF_NETWORK_PER_BUILD:true, FF_USE_IMPROVED_URL_MASKING:true
4 Resolving secrets 00:00
5 Preparing the "docker+machine" executor 00:18
6Using Docker executor with image ruby:2.7.5 ...
7Pulling docker image ruby:2.7.5 ...
8Using docker image sha256:e7c13114124cf17427e1f909e20aea6abc62b0037c3b382908b16cadb568a956 for ruby:2.7.5 with digest ruby@sha256:365df8a52b0cb34939e59c69136f7488aa8d7a8f4c2711af0a1bc25b8e8e6471 ...
9 Preparing environment 00:03
10Running on runner-gasd-s1f-project-15926775-concurrent-0 via runner-gasd-s1f-private-1682037941-4265694a...
11 Getting source from Git repository 00:01
12$ eval "$CI_PRE_CLONE_SCRIPT"
13Fetching changes with git depth set to 50...
14Initialized empty Git repository in /builds/gitlab-org/monitor/respond/.git/
15Created fresh repository.
16Checking out 070050c3 as detached HEAD (ref is master)...
17Skipping Git submodules setup
18$ git remote set-url origin "${CI_REPOSITORY_URL}"
19 Executing "step_script" stage of the job script 00:58
20Using docker image sha256:e7c13114124cf17427e1f909e20aea6abc62b0037c3b382908b16cadb568a956 for ruby:2.7.5 with digest ruby@sha256:365df8a52b0cb34939e59c69136f7488aa8d7a8f4c2711af0a1bc25b8e8e6471 ...
21$ gem install bundler
22Successfully installed bundler-2.4.12
231 gem installed
24$ bundle install
25Fetching gem metadata from https://rubygems.org/...........
26Using bundler 2.4.12
27Fetching mini_mime 1.1.2
28Fetching multi_xml 0.6.0
29Installing multi_xml 0.6.0
30Installing mini_mime 1.1.2
31Fetching unicode-display_width 2.4.2
32Fetching racc 1.6.2
33Installing unicode-display_width 2.4.2
34Fetching httparty 0.21.0
35Installing racc 1.6.2 with native extensions
36Installing httparty 0.21.0
37Fetching terminal-table 3.0.2
38Installing terminal-table 3.0.2
39Fetching gitlab 4.19.0
40Installing gitlab 4.19.0
41Fetching nokogiri 1.14.2 (x86_64-linux)
42Installing nokogiri 1.14.2 (x86_64-linux)
43Bundle complete! 2 Gemfile dependencies, 9 gems now installed.
44Use `bundle info [gemname]` to see where a bundled gem is installed.
45Post-install message from httparty:
46When you HTTParty, you must party hard!
47$ bundle exec ruby create_issues.rb
48Connecting to GitLab...
49Connection successful. Connected user email: project15926775_bot2@noreply.gitlab.com
50Loading content from config/issues.yml
51Content loaded successfully.
52Walking issues to create...
53Run Complete.
54$ bundle exec ruby weekly_update/generate.rb
55Running weekly update for 2023-04-21 - W16
56Connecting to GitLab...
57Connection successful - API: authenticated as project_15926775_bot2
58Skipping sections: .
59Found issue Draft: Monitor:Respond Weekly Update - W16 - Apr-17-2023: #126645524 - https://gitlab.com/gitlab-org/monitor/respond/-/issues/232
60<!-- REPLACE-WITH-NAVIGATION-START:UPDATE -->
61
62| [< previous update](https://gitlab.com/gitlab-org/monitor/respond/-/issues/230) |
63| --- |
64<!-- REPLACE-WITH-NAVIGATION-END:UPDATE -->
65## Highlights
66- <!-- REPLACE-WITH-HIGHLIGHTS:UPDATE -->
67#### Going into the week
68<details><summary>Capacity: 83% (80% of ~frontend, 85% of ~backend)</summary>
69 _For the week of Monday, 2023-04-17._
70 - ~frontend: max of 2 engineers, 5 days in week
71 - $`8(days) = 10(days) - 2(PTO)`$
72 - ~backend: max of 4 engineers, 5 days in week
73 - $`17(days) = 20(days) - 3(PTO)`$
74 _Data from: [Monitor:Respond Group Calendar](https://calendar.google.com/calendar/u/0?cid=Z2l0bGFiLmNvbV8xbGMyZHFpbjFoMXQ2MHFoNnJmcjJjZTE5OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t),
75 via [Google App Scripts](https://script.google.com/macros/library/d/1LWrYPmjD-leQqLJlKmtuS8Nxyf62vWV-__XKguJyB6SSOW9W7LQSIOhW/9)_
76 ---
77</details>
78<details><summary>Error budget: 99.99% 🟢</summary>
79 <!-- If not 🟢, add detail (related issues, ongoing investigations, remediations, etc). -->
80 _Data from: [Respond error budget dashboard](https://dashboards.gitlab.net/d/stage-groups-respond/stage-groups-respond-group-dashboard?orgId=1), [Respond error budget detail](https://dashboards.gitlab.net/d/stage-groups-detail-respond/stage-groups-respond-group-error-budget-detail?orgId=1&from=now-28d&to=now)_
81 ---
82</details>
83<details><summary>28 Rollover issues from %"15.11", %"15.9"</summary><br/>
84**%"15.11" rollover:**
85- https://gitlab.com/gitlab-org/gitlab/-/issues/393926+ `tristan.read`
86- https://gitlab.com/gitlab-org/gitlab/-/issues/360009+ `tristan.read`
87- https://gitlab.com/gitlab-org/gitlab/-/issues/399248+ `psjakubowska`
88- https://gitlab.com/gitlab-org/gitlab/-/issues/399231+ `psjakubowska`
89- https://gitlab.com/gitlab-org/gitlab/-/issues/391068+ `psjakubowska`
90- https://gitlab.com/gitlab-org/gitlab/-/issues/391022+ `psjakubowska`
91- https://gitlab.com/gitlab-org/gitlab/-/issues/390979+ `psjakubowska`
92- https://gitlab.com/gitlab-org/gitlab/-/issues/391020+ `psjakubowska`
93- https://gitlab.com/gitlab-org/gitlab/-/issues/387079+ `psjakubowska`
94- https://gitlab.com/gitlab-org/gitlab/-/issues/226995+ `rkadam3`
95- https://gitlab.com/gitlab-org/gitlab/-/issues/389822+ `splattael`
96- https://gitlab.com/gitlab-org/gitlab/-/issues/389247+ `splattael`
97- https://gitlab.com/gitlab-org/gitlab/-/issues/384530+ `splattael`
98- https://gitlab.com/gitlab-org/gitlab/-/issues/381882+ `splattael`
99- https://gitlab.com/gitlab-org/ruby/gems/gitlab-styles/-/issues/46+ `splattael`
100- https://gitlab.com/gitlab-org/gitlab/-/issues/372301+ `splattael`
101- https://gitlab.com/gitlab-org/monitor/respond/-/issues/230+ `syasonik`
102- https://gitlab.com/gitlab-org/gitlab/-/issues/397137+ `syasonik`
103- https://gitlab.com/gitlab-org/gitlab/-/issues/397136+ `syasonik`
104- https://gitlab.com/gitlab-org/gitlab/-/issues/394998+ `rkadam3`
105- https://gitlab.com/gitlab-org/gitlab/-/issues/394992+ `rkadam3`
106- https://gitlab.com/gitlab-org/gitlab/-/issues/394991+ `rkadam3`
107- https://gitlab.com/gitlab-org/gitlab/-/issues/394989+ `rkadam3`
108- https://gitlab.com/gitlab-org/gitlab/-/issues/394987+ `rkadam3`
109- https://gitlab.com/gitlab-org/gitlab/-/issues/394986+ `rkadam3`
110- https://gitlab.com/gitlab-org/gitlab/-/issues/384530+ `splattael`
111- https://gitlab.com/gitlab-org/gitlab/-/issues/226995+ `rkadam3`
112**%"15.9" rollover:**
113- https://gitlab.com/gitlab-org/gitlab/-/issues/389079+ `splattael`
114_Data from: GitLab REST API. Contains open issues which are
115in a prior milestone & assigned to a ~"group::respond" engineer._
116---
117</details>
118<details><summary>16.0 focus area distribution</summary>
119 | 44% ~"type::maintenance" | 22% ~"type::feature" | 22% ~"type::bug" | 11% w/o type |
120| ----- | ----- | ----- | ----- |
121| 50% w/o sub-type<br/> 25% ~"maintenance::pipelines"<br/> 25% ~"maintenance::refactor" | 100% ~"feature::consolidation" | 100% w/o sub-type | 100% w/o sub-type |
122 | 44% w/o epic | 33% gitlab-org&7783+ | 11% gitlab-org&9635+ | 11% gitlab-org&7895+ |
123| ----- | ----- | ----- | ----- |
124| 75% w/o eng label<br/> 25% ~"frontend" | 67% w/o eng label<br/> 33% ~"backend" ~"frontend" | 100% w/o eng label | 100% w/o eng label |
125</details>
126#### End of week progress snapshot
127<!-- REPLACE-WITH-PROGRESS-SUMMARY:UPDATE -->
128<details><summary>More info...</summary>
129<!-- REPLACE-WITH-PROGRESS-DETAIL:UPDATE -->
130</details>
131<!-- REPLACE-WITH-TEAM-ACTIVITY:UPDATE -->
132### Relevant links
133- [Current Planning Issue](https://gitlab.com/gitlab-org/monitor/respond/-/issues/207)
134- [Async Retrospectives](https://gitlab.com/gl-retrospectives/monitor/respond/-/issues/)
135- Internal dogfooding adoption ([chart](https://app.periscopedata.com/app/gitlab/737489/Respond-Group-Working-Dashboard?widget=c-79&widget=13920751&udv=0))
136- Dogfooding by feature ([table](https://about.gitlab.com/direction/monitor/debugging_and_health/incident_management/#incident-management-features-the-infrastructure-team-is-currently-dogfooding))
137- [Support Help Requests](https://gitlab.com/groups/gitlab-com/ops-sub-department/-/issues/?label_name%5B%5D=Help%20group%3A%3Arespond)
138- [Ops Department Status Updates](https://gitlab.com/gitlab-com/ops-sub-department/ops-status-updates/-/issues)
139cc @kbychu @broncato
140---
141_This update was generated by the [weekly_update](https://gitlab.com/gitlab-org/monitor/respond/-/tree/master/weekly_update) script in [gitlab-org/monitor/respond](https://gitlab.com/gitlab-org/monitor/respond). Highlights are manually curated._
142<details><summary><em>How does it work?</em></summary>
143#### Where does the content come from?
144Highlights are added manually; everything else is pulled from GitLab, Google, Grafana, etc.
145#### How does it get there?
1461. Every Friday, a scheduled pipeline creates the issue for the next week, and it updates the issue for the current week.
1471. When a new issue is created, only a few details are included in the description about what might be expected for the week. A comment thread is added where highlights can be collected to be autofilled into the description later in the week.
1481. When the issue is updated, the highlights thread will be collected as a list and added to the issue description. An detailed overview of progress on the milestone will also be included.
149#### How do I make changes?
150##### To this specific issue
151This specific issue: Add content directly to the issue description, or you can add highlights by commenting on the highlights thread.
152##### Format
153Static content: Update [weekly-update.md](https://gitlab.com/gitlab-org/monitor/respond/-/blob/master/.gitlab/issue_templates/weekly-update.md). Add any static content to the file to include it in the issue description when the issue is created.
154Dynamic content: Rearrange the `REPLACE-ME` placeholder HTML comments. Placeholder comments can be either singleline or multiline. The placeholders are replaced by script-aggregated content.
155- Required attributes:
156 - `section`: all-caps name given to a chunk of markdown generated by the [weekly_update](https://gitlab.com/gitlab-org/monitor/respond/-/tree/master/weekly_update) script.
157 - `NAVIGATION` -> Link to previous/next update issue
158 - `CAPACITY` -> PTO breakdown for Monitor:Respond team for the week
159 - `ERROR-BUDGET` -> Current state of respond error budget
160 - `ISSUE-DISTRIBUTION` -> Breakdown of team's focus by type label & epic
161 - `PROGRESS-SUMMARY` -> Estimated % completion of scheduled issues by epic
162 - `PROGRESS-DETAIL` -> Estimated % completion of each individual scheduled issue
163 - `TEAM-ACTIVITY` -> Aggregated contributions for each team member over the last week
164 - `ROLLOVER` -> Issues assigned to team members in expired milestones
165 - `TEAM-LINKS` -> Link to planning issue & other team-specifics that change week to week
166 - `QUICK-ACTIONS` -> Assigns milestone & other team-specifics that change week to week
167 - `HIGHLIGHTS` -> List of comments from highlight thread (oldest thread to include the word "highlight" in the first comment)
168 - `action`: determines when the comment will be replaced in the issue description.
169 - `CREATE` - replaced when the issue is created
170 - `UPDATE` - replaced at the end of the week
171- Singleline format:
172 - `<!-- REPLACE-WITH-<section>:<action> -->`
173- Multiline format:
174 - ```html
175 <!-- REPLACE-WITH-<section>-START:<action> -->
176 Anything here will also be replaced when the script runs.
177 <!-- REPLACE-WITH-<section>-END:<action> -->
178 ```
179Adding threads: Add a multiline placeholder with `section` of `THREAD`. Content inside the block will be added as a thread on the issue, and it can include other placeholders.
180##### Content
181Run the [`Generate detailed weekly update issue`](https://gitlab.com/gitlab-org/monitor/respond/-/pipeline_schedules) to trigger an update. Once an update has run, the pipeline can be run many
182times without consequence to the existing issue. Refer to `Format > Dynamic content` for the syntax needed
183to regenerate sections of the issue.
184To modify how the content itself is generated, refer to [`weekly_update/README.md`](https://gitlab.com/gitlab-org/monitor/respond/-/blob/master/weekly_update/README.md).
185</details>
186Starting generation for NAVIGATION section...
187Starting generation for CAPACITY section...
188Starting generation for ERROR-BUDGET section...
189Starting generation for ISSUE-DISTRIBUTION section...
190Fetching related MRs for issue #126975176...
191Fetching related MRs for issue #125734110...
192Fetching related MRs for issue #125693133...
193Fetching related MRs for issue #125690168...
194Fetching related MRs for issue #125579437...
195Fetching related MRs for issue #125578602...
196Fetching related MRs for issue #125578467...
197Fetching related MRs for issue #125466497...
198Fetching related MRs for issue #125466491...
199Fetching related MRs for issue #125466490...
200Fetching related MRs for issue #125466488...
201Fetching related MRs for issue #125466484...
202Fetching related MRs for issue #124945625...
203Fetching related MRs for issue #124943669...
204Fetching related MRs for issue #124943655...
205Fetching related MRs for issue #124943588...
206Fetching related MRs for issue #124943307...
207Fetching related MRs for issue #124942970...
208Fetching related MRs for issue #124891830...
209Fetching related MRs for issue #124700950...
210Starting generation for PROGRESS-SUMMARY section...
211Starting generation for PROGRESS-DETAIL section...
212Starting generation for TEAM-ACTIVITY section...
213Starting generation for ROLLOVER section...
214Starting generation for TEAM-LINKS section...
215Starting generation for QUICK-ACTIONS section...
216Starting generation for HIGHLIGHTS section...
217Created issue Draft: Monitor:Respond Weekly Update - W17 - Apr-24-2023: #127013295 - https://gitlab.com/gitlab-org/monitor/respond/-/issues/233
218<!-- REPLACE-WITH-NAVIGATION-START:UPDATE -->
219
220| [< previous update](https://gitlab.com/gitlab-org/monitor/respond/-/issues/232) |
221| --- |
222<!-- REPLACE-WITH-NAVIGATION-END:UPDATE -->
223## Highlights
224- <!-- REPLACE-WITH-HIGHLIGHTS:UPDATE -->
225#### Going into the week
226<details><summary>Capacity: 77% (40% of ~frontend, 95% of ~backend)</summary>
227 _For the week of Monday, 2023-04-24._
228 - ~frontend: max of 2 engineers, 5 days in week
229 - $`4(days) = 10(days) - 6(PTO)`$
230 - ~backend: max of 4 engineers, 5 days in week
231 - $`19(days) = 20(days) - 1(PTO)`$
232 _Data from: [Monitor:Respond Group Calendar](https://calendar.google.com/calendar/u/0?cid=Z2l0bGFiLmNvbV8xbGMyZHFpbjFoMXQ2MHFoNnJmcjJjZTE5OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t),
233 via [Google App Scripts](https://script.google.com/macros/library/d/1LWrYPmjD-leQqLJlKmtuS8Nxyf62vWV-__XKguJyB6SSOW9W7LQSIOhW/9)_
234 ---
235</details>
236<details><summary>Error budget: 🟢 100.0%</summary>
237 <!-- If not 🟢, add detail (related issues, ongoing investigations, remediations, etc). -->
238 _Data from: [Respond error budget dashboard](https://dashboards.gitlab.net/d/stage-groups-respond/stage-groups-respond-group-dashboard?orgId=1), [Respond error budget detail](https://dashboards.gitlab.net/d/stage-groups-detail-respond/stage-groups-respond-group-error-budget-detail?orgId=1&from=now-28d&to=now)_
239 ---
240</details>
241<details><summary>0 Rollover issues from </summary><br/>
242_Data from: GitLab REST API. Contains open issues which are
243in a prior milestone & assigned to a ~"group::respond" engineer._
244---
245</details>
246<details><summary>16.0 focus area distribution</summary>
247 | 90% ~"type::maintenance" | 5% ~"type::feature" | 5% ~"type::bug" |
248| ----- | ----- | ----- |
249| 78% ~"maintenance::removal"<br/> 22% ~"maintenance::refactor" | 100% ~"feature::addition" | 100% w/o sub-type |
250 | 45% gitlab-org&10107+ | 30% gitlab-org&10030+ | 15% gitlab-org&10127+ | 10% w/o epic |
251| ----- | ----- | ----- | ----- |
252| 56% ~"backend"<br/> 22% ~"frontend"<br/> 11% ~"backend" ~"frontend"<br/> 11% w/o eng label | 50% ~"backend" ~"frontend"<br/> 33% ~"backend"<br/> 17% w/o eng label | 67% w/o eng label<br/> 33% ~"backend" ~"frontend" | 50% w/o eng label<br/> 50% ~"backend" ~"frontend" |
253</details>
254#### End of week progress snapshot
255<!-- REPLACE-WITH-PROGRESS-SUMMARY:UPDATE -->
256<details><summary>More info...</summary>
257<!-- REPLACE-WITH-PROGRESS-DETAIL:UPDATE -->
258</details>
259<!-- REPLACE-WITH-TEAM-ACTIVITY:UPDATE -->
260### Relevant links
261- [Current Planning Issue](https://gitlab.com/gitlab-org/monitor/respond/-/issues/207)
262- [Async Retrospectives](https://gitlab.com/gl-retrospectives/monitor/respond/-/issues/)
263- Internal dogfooding adoption ([chart](https://app.periscopedata.com/app/gitlab/737489/Respond-Group-Working-Dashboard?widget=c-79&widget=13920751&udv=0))
264- Dogfooding by feature ([table](https://about.gitlab.com/direction/monitor/debugging_and_health/incident_management/#incident-management-features-the-infrastructure-team-is-currently-dogfooding))
265- [Support Help Requests](https://gitlab.com/groups/gitlab-com/ops-sub-department/-/issues/?label_name%5B%5D=Help%20group%3A%3Arespond)
266- [Ops Department Status Updates](https://gitlab.com/gitlab-com/ops-sub-department/ops-status-updates/-/issues)
267cc @kbychu @broncato
268---
269_This update was generated by the [weekly_update](https://gitlab.com/gitlab-org/monitor/respond/-/tree/master/weekly_update) script in [gitlab-org/monitor/respond](https://gitlab.com/gitlab-org/monitor/respond). Highlights are manually curated._
270<details><summary><em>How does it work?</em></summary>
271#### Where does the content come from?
272Highlights are added manually; everything else is pulled from GitLab, Google, Grafana, etc.
273#### How does it get there?
2741. Every Friday, a scheduled pipeline creates the issue for the next week, and it updates the issue for the current week.
2751. When a new issue is created, only a few details are included in the description about what might be expected for the week. A comment thread is added where highlights can be collected to be autofilled into the description later in the week.
2761. When the issue is updated, the highlights thread will be collected as a list and added to the issue description. An detailed overview of progress on the milestone will also be included.
277#### How do I make changes?
278##### To this specific issue
279This specific issue: Add content directly to the issue description, or you can add highlights by commenting on the highlights thread.
280##### Format
281Static content: Update [weekly-update.md](https://gitlab.com/gitlab-org/monitor/respond/-/blob/master/.gitlab/issue_templates/weekly-update.md). Add any static content to the file to include it in the issue description when the issue is created.
282Dynamic content: Rearrange the `REPLACE-ME` placeholder HTML comments. Placeholder comments can be either singleline or multiline. The placeholders are replaced by script-aggregated content.
283- Required attributes:
284 - `section`: all-caps name given to a chunk of markdown generated by the [weekly_update](https://gitlab.com/gitlab-org/monitor/respond/-/tree/master/weekly_update) script.
285 - `NAVIGATION` -> Link to previous/next update issue
286 - `CAPACITY` -> PTO breakdown for Monitor:Respond team for the week
287 - `ERROR-BUDGET` -> Current state of respond error budget
288 - `ISSUE-DISTRIBUTION` -> Breakdown of team's focus by type label & epic
289 - `PROGRESS-SUMMARY` -> Estimated % completion of scheduled issues by epic
290 - `PROGRESS-DETAIL` -> Estimated % completion of each individual scheduled issue
291 - `TEAM-ACTIVITY` -> Aggregated contributions for each team member over the last week
292 - `ROLLOVER` -> Issues assigned to team members in expired milestones
293 - `TEAM-LINKS` -> Link to planning issue & other team-specifics that change week to week
294 - `QUICK-ACTIONS` -> Assigns milestone & other team-specifics that change week to week
295 - `HIGHLIGHTS` -> List of comments from highlight thread (oldest thread to include the word "highlight" in the first comment)
296 - `action`: determines when the comment will be replaced in the issue description.
297 - `CREATE` - replaced when the issue is created
298 - `UPDATE` - replaced at the end of the week
299- Singleline format:
300 - `<!-- REPLACE-WITH-<section>:<action> -->`
301- Multiline format:
302 - ```html
303 <!-- REPLACE-WITH-<section>-START:<action> -->
304 Anything here will also be replaced when the script runs.
305 <!-- REPLACE-WITH-<section>-END:<action> -->
306 ```
307Adding threads: Add a multiline placeholder with `section` of `THREAD`. Content inside the block will be added as a thread on the issue, and it can include other placeholders.
308##### Content
309Run the [`Generate detailed weekly update issue`](https://gitlab.com/gitlab-org/monitor/respond/-/pipeline_schedules) to trigger an update. Once an update has run, the pipeline can be run many
310times without consequence to the existing issue. Refer to `Format > Dynamic content` for the syntax needed
311to regenerate sections of the issue.
312To modify how the content itself is generated, refer to [`weekly_update/README.md`](https://gitlab.com/gitlab-org/monitor/respond/-/blob/master/weekly_update/README.md).
313</details>/builds/gitlab-org/monitor/respond/weekly_update/description.rb:266:in `block (2 levels) in format_contributions': undefined method `title' for nil:NilClass (NoMethodError)
314 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:259:in `each'
315 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:259:in `block in format_contributions'
316 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:256:in `each'
317 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:256:in `format_contributions'
318 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:231:in `block in team_activities_markdown'
319 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:207:in `each'
320 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:207:in `map'
321 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:207:in `team_activities_markdown'
322 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:36:in `block in render'
323 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:31:in `each'
324 from /builds/gitlab-org/monitor/respond/weekly_update/description.rb:31:in `render'
325 from /builds/gitlab-org/monitor/respond/weekly_update/weekly_update.rb:79:in `description'
326 from /builds/gitlab-org/monitor/respond/weekly_update/weekly_update.rb:44:in `update!'
327 from weekly_update/generate.rb:84:in `update'
328 from weekly_update/generate.rb:69:in `generate!'
329 from weekly_update/generate.rb:42:in `run'
330 from weekly_update/generate.rb:121:in `<main>'
331Starting generation for NAVIGATION section...
332Starting generation for CAPACITY section...
333Starting generation for ERROR-BUDGET section...
334Starting generation for ISSUE-DISTRIBUTION section...
335Starting generation for PROGRESS-SUMMARY section...
336Fetching related MRs for issue #126975176...
337Fetching related MRs for issue #125734110...
338Fetching related MRs for issue #125693133...
339Fetching related MRs for issue #125690168...
340Fetching related MRs for issue #125579437...
341Fetching related MRs for issue #125578602...
342Fetching related MRs for issue #125578467...
343Fetching related MRs for issue #125466497...
344Fetching related MRs for issue #125466491...
345Fetching related MRs for issue #125466490...
346Fetching related MRs for issue #125466488...
347Fetching related MRs for issue #125466484...
348Fetching related MRs for issue #124945625...
349Fetching related MRs for issue #124943669...
350Fetching related MRs for issue #124943655...
351Fetching related MRs for issue #124943588...
352Fetching related MRs for issue #124943307...
353Fetching related MRs for issue #124942970...
354Fetching related MRs for issue #124891830...
355Fetching related MRs for issue #124700950...
356Starting generation for PROGRESS-DETAIL section...
357Starting generation for TEAM-ACTIVITY section...
358Collecting activity for date range: Fri 2023-04-14 - Sat 2023-04-22
359Collecting activity for tristan.read.
360--- Page 0, starting from 2023-04-17
361--- Page 1, starting from 2023-04-17
362Collecting activity for psjakubowska.
363--- Page 0, starting from 2023-04-17
364--- Page 1, starting from 2023-04-18
365Collecting activity for splattael.
366--- Page 0, starting from 2023-04-17
367--- Page 1, starting from 2023-04-20
368--- Page 2, starting from 2023-04-19
369--- Page 3, starting from 2023-04-18
370--- Page 4, starting from 2023-04-17
371--- Page 5, starting from 2023-04-14
372Collecting activity for syasonik.
373--- Page 0, starting from 2023-04-17
374Collecting activity for ck3g.
375--- Page 0, starting from 2023-04-17
376Collecting activity for rkadam3.
377--- Page 0, starting from 2023-04-17
378--- Page 1, starting from 2023-04-18
379Collecting activity for francoisrose.
380--- Page 0, starting from 2023-04-17
381Fetching merge_requests detail for iids ["117619", "117082", "115714", "117486", "117823", "115463", "117658", "117342", "118218", "118077", "118068", "117905", "117149", "115984", "115867", "117649", "117631", "117429", "117993", "118213", "118019", "117897", "118035", "117766", "118167", "118039", "117776", "93137", "108895", "117818", "117694", "117759", "117847", "117871", "117762", "117487", "117783", "117133", "117758", "117767", "117765", "117763", "117760", "117598", "116189", "117659", "117660", "116651", "116919", "116650", "112889", "117640", "117517", "117603", "117533", "117433", "109335", "116191", "117529", "118184", "118158", "118024", "118028", "117784", "117273", "117568", "117715", "117248", "117301"] in project gitlab-org/gitlab...
382Fetching merge_requests detail for iids ["765", "763"] in project gitlab-org/status-page...
383Fetching issues detail for iids ["407588", "384239", "390979", "399231", "387079", "399189", "398202", "408232", "408228", "408225", "408216", "408201", "408200", "407877", "386731", "407862", "406761", "381882", "407634", "389822", "372301", "379033", "404923", "406838", "389247", "406626", "407331", "407329", "407328", "389477", "406571", "226995", "218041", "381282", "389079", "372287", "360009", "367856", "360005", "343237", "383160", "403059", "406550", "406668"] in project gitlab-org/gitlab...
384Fetching issues detail for iids ["14"] in project gitlab-org/ci-cd/section-showcases...
385Fetching issues detail for iids ["2146"] in project gitlab-org/opstrace/opstrace...
386Fetching issues detail for iids ["12087", "12085", "11420"] in project gitlab-org/quality/triage-reports...
387Fetching issues detail for iids ["56"] in project gitlab-org/ruby/gems/gitlab-styles...
388Fetching merge_requests detail for iids ["122898", "123084"] in project gitlab-com/www-gitlab-com...
389Fetching issues detail for iids ["1798"] in project gitlab-org/gitlab-development-kit...
390Fetching issues detail for iids ["23"] in project splattael/mwps...
391Fetching merge_requests detail for iids ["41"] in project gitlab-org/monitor/respond...
392Fetching merge_requests detail for iids ["2140"] in project gitlab-org/quality/triage-ops...
393Fetching issues detail for iids ["230", "206", "232", "214"] in project gitlab-org/monitor/respond...
394NoMethodError: undefined method `title' for nil:NilClass
395/builds/gitlab-org/monitor/respond/weekly_update/description.rb:266:in `block (2 levels) in format_contributions'
396/builds/gitlab-org/monitor/respond/weekly_update/description.rb:259:in `each'
397/builds/gitlab-org/monitor/respond/weekly_update/description.rb:259:in `block in format_contributions'
398/builds/gitlab-org/monitor/respond/weekly_update/description.rb:256:in `each'
399/builds/gitlab-org/monitor/respond/weekly_update/description.rb:256:in `format_contributions'
400/builds/gitlab-org/monitor/respond/weekly_update/description.rb:231:in `block in team_activities_markdown'
401/builds/gitlab-org/monitor/respond/weekly_update/description.rb:207:in `each'
402/builds/gitlab-org/monitor/respond/weekly_update/description.rb:207:in `map'
403/builds/gitlab-org/monitor/respond/weekly_update/description.rb:207:in `team_activities_markdown'
404/builds/gitlab-org/monitor/respond/weekly_update/description.rb:36:in `block in render'
405/builds/gitlab-org/monitor/respond/weekly_update/description.rb:31:in `each'
406/builds/gitlab-org/monitor/respond/weekly_update/description.rb:31:in `render'
407/builds/gitlab-org/monitor/respond/weekly_update/weekly_update.rb:79:in `description'
408/builds/gitlab-org/monitor/respond/weekly_update/weekly_update.rb:44:in `update!'
409weekly_update/generate.rb:84:in `update'
410weekly_update/generate.rb:69:in `generate!'
411weekly_update/generate.rb:42:in `run'
412weekly_update/generate.rb:121:in `<main>'
413 Cleaning up project directory and file based variables 00:01
414ERROR: Job failed: exit code 1