CIDuty/SVMeetings/August1-August5
From MozillaWiki
< CIDuty | SVMeetings(Redirected from Buildduty/SVMeetings/August1-August5)
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: 8/12
- 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/08/01- 2016/08/05
- Continue working on triage perf alerts
- Investigate perf regression issues
- bug 1290808
- Continue working on classification of treeherder
- Worked with Tomcat and KWierso for backouts
- Land check-in needed patches to repos
SV: 2016/08/01 - 2016/08/05
- Bug 1273249 - Missing SNS alerts from papertrail
- deployed the latest changes, did some tests
- relengbot seems to work fine (alerts appear in #buildduty)
- need to fix one minor issue with the timestamp displayed
- Bug 1261113 - Restore firewall-tests to operational status
- atm, we do have network flows from cruncher-aws to AWS slaves
- 2 solutions that I see here:
- file a bug to remove those network flow, then update test_slave_vlans_cruncher() to check they don’t exist
- simply don’t test for their existence (remove test_slave_vlans_cruncher())
- Bug 1259491 - Set root password based on node security level
- Amy suggested going on with the groupings suggested by Coop
- currently adding the corresponding gpg keys to the new password files