CIDuty/SVMeetings/July25-July29
From MozillaWiki
< CIDuty | SVMeetings(Redirected from Buildduty/SVMeetings/July25-July29)
Contents
Meeting Details
- Meetings every Wednesday
- Meeting notes archive:
- https://wiki.mozilla.org/ReleaseEngineering/Buildduty/SVMeetings
Upcoming vacation/PTO:
- Alin:
- Andrei: August 5 - 19 August
- Coop: a week in August (TBD)
- Ihsiao:
- Ashiue: 7/29
- Kmoir: week at end of August tbd
Holidays:
- Canada:
- August 1
- Romania:
- August 15
- November 30
- December 1 (National Day)
- Taiwan:
- Moon Festival, 9/15-16
- National Day, 10/10
Possible bugs
- Write a tool to update bugzilla bugs for outstanding machine loans and ask if the loaner is still needed on say, a weekly basis: https://bugzilla.mozilla.org/show_bug.cgi?id=1171165
- Long Inter-Job Timing on t-yosemite-r7 https://bugzilla.mozilla.org/show_bug.cgi?id=1258480
- Create new script to setup a buildbot master for development: https://bugzil.la/1275135
From coop:
- Should all have access to release@mozilla.com email now.
- You’ll want filters: https://wiki.mozilla.org/ReleaseEngineering/Day_1_Checklist#Mail_Filtering
- #mozbuild channel access
- Q3 goals?
From kmoir:
Taipei: 2016/07/25- 2016/07/29
- Continue working on classification of treeherder
- Worked with Tomcat and KWierso for backouts
- Continue working on triage perf alerts
- Investigate perf regression issues with Joel
- bug 1289270, bug 1288994, bug 1289002, bug 1289032, bug 1289321
SV: 2016/07/25 - 2016/07/29
- Bug 1261113 - Restore firewall-tests to operational status
- would need to know if there are any network flows to add for cruncher-aws
- Needinfo on coop
- would need to know if there are any network flows to add for cruncher-aws
- [relengbot]
- Need to see the messages exchanged between Papertrail - AWS SNS and AWS SNS - Heroku app
- access to AWS CloudTrail?
- Coop to grant access
- Bug 1285483 - t-yosemite-r7 machines have high coreaudiod and launchd CPU usage
- Spoke by email with support from apple but not with the technical team ,still wait for some answer from them
- Bug 1179819 - runner tasks output on OSX goes to /dev/null
- Should we just redirect runner.out to syslog to get those output to Papertrail ?
- Continued to work on usual tasks(investigated failed jobs, restarted broken slaves,made loan requests,etc)