QNX Kernel Team Weekly Meeting for 2007-10-01#
Meeting Minutes:#
Steve Bergwerff
- The Trinity M1 sanity passed so the go ahead was given to rest of testers on September 26 to run their tests.
Shiv Nagarajan (absent)
- Working from Singapore this week
Peter Mitsis
- Last week was spent working on PR fixes
- Also some continued development work on IO-FS.
- Started work on creation of automated tests for changes/fixes that are in Trinity 2
Doug Bailey
- Working on a customer reported crash on 6.2.1 that was triggered by a msgReplyv on a stale rcvid. Have a theory to discuss with Xiaodan. (PR 51782)
- Working on an SP3 issue reported by a customer. (PR 51538).
- Resolved a PR that Colin handed over with regards to dumpifs not building on Solaris for Trinity 2.
- Finished some benchmarks for a custom engineering contract
Chris Travis
- Going through M1 test results.
- Debugging some board issues in the lab.
- Attended Thursday’s PR Review meeting and had some action items to follow up on.
- Getting a machine in order to run lint on Trinity 2
Mosa (via proxy)
- Working on benchmark tests.
- Creating test cases for fixed PRs.
Linda Deng (via proxy)
- working from home
- Went through posix test suite results for Trinity 2. Raised one showstopper PR.
- Went through file system test results for Trinity 2. Raised 3 new PRs.
Colin Burgess
- Delivered a customer source drop this week for Trinity 2 plus some additional source. Still need to create a readme of fixed issues.
- Memory Partitioning code inspects.
- Plan to investigate a crash seen during compile.
Marion Koss
- Writing test documentation for memory partitioning and making changes to tests at the same time.
- Tested new memory partitioning drop from Mike. Results improved significantly.
Gordon Rice
- Was on a drivers course last week
- Looking into an issue with tracelogger.
Mike Kisel
- Had two code inspection sessions last week for memory partitioning.
- Fixed a number of memory partitioning bugs
Attilla Danko
- most of week spent investigating async messaging PRs and what will be done for Trinity 2.
Brian Stecher.
- Working with Colin on customer drop of Trinity 2.
- Lot of time spent on memory partitioning code inspects
- Working with customer to resolve some integration issues with Trinity 2