Attendees: Matteo, Anton, Shebu, Glen, Fathi, Karl
Minutes:
- Matteo: TFC-5
- Recommend to put on hold. Licensing / Versioing problem. Arm CI
using a version that Linaro uses, but require an Arm license. New version
are license free. But the free version not used. Need to use
License free
version inside Arm to validate it first.
- Moved to Blocker
- Matteo: TFC-69
- Want to see this resolved.
- Glen: A patch is available
- Leonardo reviewing all the Gap issues today
- TFC-4 MBedTLS
- Team has some questions on how to break down and details on order.
- A sync will be planned for this
- TFC-23
- Updating docs. Like to keep it at the top of the list
- Want to get the initial platform going. Currently ST.
- TFC-27 Jobs failed.
- Karl list failed jobs. Occurred last time on March 8.
- Glen: Fathi proposed instrumenting the code. Was that done?
- Karl: Not sure, will check.
- Ask: Karl instrument code to understand why failing
- Fathi: Log not detailed the issue.
- Anton: Low priority and can overcome the issue
- Fathi: Need to instrument the code. Print more details.
- Anton: After release will add debug messages to see if will help.
Hi Guys,
Sorry I could not make the call today
Regarding https://projects.linaro.org/secure/RapidBoard.jspa?rapidView=300&projectKey… if the Linaro team want to have a chat with me I can help clarify some of the details, especially around the gerrit labels updates needed to invoke the OpenCI and ArmCI separately. I've added though some comments in the ticket to help clarify what's needed in this space for now.
Joanna
On 16/03/2021, 14:07, "Tf-openci-triage on behalf of Glen Valante via Tf-openci-triage" <tf-openci-triage-bounces(a)lists.trustedfirmware.org on behalf of tf-openci-triage(a)lists.trustedfirmware.org> wrote:
Thanks Don, I will be following up with the team later today and will
have a plan for TFC-31.
-g
On 3/16/2021 9:53 AM, Don Harbin via Tf-openci-triage wrote:
> Attendees: Karl, Don, Anton
>
> Minutes:
>
> - Quick meeting due to Don's last minute time change - sorry about that.
> - ACTION: Don - determine good meeting time. Things really bad on the
> Linaro side in that 2 hour window. Seems bad on Arm side as well.
> - Propose moving back to 5:30am Don's time, but Don may only attend
> optionally.
> - Matteo notes shared with Don prior to meeting:
> - I see some in-progresses which I assume are new (urgent?) stuff
> like 39, 49 and 50.
> - TFC-5 has been picked...that's ok but the most important prio thing
> is TFC-31 to deploy TF-A CI so if TFC-5 is small and quick,
> OK..if it turns
> into huge work, I say park it and progress TFC-31 instead which is on the
> critical path...we need to deploy live TF_A even with tests disabled
> (becasue of TF-5)
> - TFC-25 is also not closed yet...but looking at Glen' last comment,
> there seems to be some minor things still open...I'd use the same
> rationale..if small fixes OK...else park them (and we can re-check with
> Joanna team afterwards)
> - We should really plan to deploy TF-A before the next Board meeting,
> as per Julius and general request (That means closing TFC-31 in the next
> 2-3 weeks...considering easter break!)
>
>
> - Karl: OpenCI running more stable - ran 800 jobs and all passed.
> - Don: Which tickets are critical to TF-M?
> - Karl: TFC-50 is a really strong candidate to reduce risk.
> - Don: A nice risk mitigator, but can be put below TFC-31?
> - Karl/Anton: Agreed
> - Anton: Agreed that nothing critical for TF-M so can move the TF-A
> tasks as needed.
> - ACTION: Don to investigate with Glen how to get TFC-31 scoped and into
> the In Progress as top priority to support our commit of having TF-A
> deployed before April 14th.
>
> Don
--
Linaro <http://www.linaro.org>
Glen Valante | /Sr. Technical Program Manager/
T: +1.508.517.3461 <tel:1617-320-5000>
glen.valante(a)linaro.org <mailto:glen.valante@linaro.org> | Skype:
gvalante <callto:gvalante>
--
Tf-openci-triage mailing list
Tf-openci-triage(a)lists.trustedfirmware.org
https://lists.trustedfirmware.org/mailman/listinfo/tf-openci-triage
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Thanks Don, I will be following up with the team later today and will
have a plan for TFC-31.
-g
On 3/16/2021 9:53 AM, Don Harbin via Tf-openci-triage wrote:
> Attendees: Karl, Don, Anton
>
> Minutes:
>
> - Quick meeting due to Don's last minute time change - sorry about that.
> - ACTION: Don - determine good meeting time. Things really bad on the
> Linaro side in that 2 hour window. Seems bad on Arm side as well.
> - Propose moving back to 5:30am Don's time, but Don may only attend
> optionally.
> - Matteo notes shared with Don prior to meeting:
> - I see some in-progresses which I assume are new (urgent?) stuff
> like 39, 49 and 50.
> - TFC-5 has been picked...that's ok but the most important prio thing
> is TFC-31 to deploy TF-A CI so if TFC-5 is small and quick,
> OK..if it turns
> into huge work, I say park it and progress TFC-31 instead which is on the
> critical path...we need to deploy live TF_A even with tests disabled
> (becasue of TF-5)
> - TFC-25 is also not closed yet...but looking at Glen' last comment,
> there seems to be some minor things still open...I'd use the same
> rationale..if small fixes OK...else park them (and we can re-check with
> Joanna team afterwards)
> - We should really plan to deploy TF-A before the next Board meeting,
> as per Julius and general request (That means closing TFC-31 in the next
> 2-3 weeks...considering easter break!)
>
>
> - Karl: OpenCI running more stable - ran 800 jobs and all passed.
> - Don: Which tickets are critical to TF-M?
> - Karl: TFC-50 is a really strong candidate to reduce risk.
> - Don: A nice risk mitigator, but can be put below TFC-31?
> - Karl/Anton: Agreed
> - Anton: Agreed that nothing critical for TF-M so can move the TF-A
> tasks as needed.
> - ACTION: Don to investigate with Glen how to get TFC-31 scoped and into
> the In Progress as top priority to support our commit of having TF-A
> deployed before April 14th.
>
> Don
--
Linaro <http://www.linaro.org>
Glen Valante | /Sr. Technical Program Manager/
T: +1.508.517.3461 <tel:1617-320-5000>
glen.valante(a)linaro.org <mailto:glen.valante@linaro.org> | Skype:
gvalante <callto:gvalante>
Attendees: Karl, Don, Anton
Minutes:
- Quick meeting due to Don's last minute time change - sorry about that.
- ACTION: Don - determine good meeting time. Things really bad on the
Linaro side in that 2 hour window. Seems bad on Arm side as well.
- Propose moving back to 5:30am Don's time, but Don may only attend
optionally.
- Matteo notes shared with Don prior to meeting:
- I see some in-progresses which I assume are new (urgent?) stuff
like 39, 49 and 50.
- TFC-5 has been picked...that's ok but the most important prio thing
is TFC-31 to deploy TF-A CI so if TFC-5 is small and quick,
OK..if it turns
into huge work, I say park it and progress TFC-31 instead which is on the
critical path...we need to deploy live TF_A even with tests disabled
(becasue of TF-5)
- TFC-25 is also not closed yet...but looking at Glen' last comment,
there seems to be some minor things still open...I'd use the same
rationale..if small fixes OK...else park them (and we can re-check with
Joanna team afterwards)
- We should really plan to deploy TF-A before the next Board meeting,
as per Julius and general request (That means closing TFC-31 in the next
2-3 weeks...considering easter break!)
- Karl: OpenCI running more stable - ran 800 jobs and all passed.
- Don: Which tickets are critical to TF-M?
- Karl: TFC-50 is a really strong candidate to reduce risk.
- Don: A nice risk mitigator, but can be put below TFC-31?
- Karl/Anton: Agreed
- Anton: Agreed that nothing critical for TF-M so can move the TF-A
tasks as needed.
- ACTION: Don to investigate with Glen how to get TFC-31 scoped and into
the In Progress as top priority to support our commit of having TF-A
deployed before April 14th.
Don
Attendees: Don, Karl, Ben C, Anton, Shebu, Fathi, Joanna
Minutes:
- TF-M 1.3, Already in master.
- Review KanBan
- Glen Status:
- Leonardo - Gaps is be close to complete
- Arthur working on TFC-28
- TFC-37: LSS-2136
- Joanna: No longer seeing any issues. Should we send a post to
users to make them aware or just wait?
- Ben C: Sanitized all comments (including closed) from when it
started to when it was resolved.
- All repos?
- Yes
- Root cause - Gerrit git rep head was out of date. Came from the AWS
to Dedicated server migration.
- Joanna: Leave open one more week and then close if no more issues.
- SC Approved column
- Expect scripts is top priority. TFC-36
- Joanna: Since using a LAVA Monitor, need to be revisited.
- TFC-36 - broken into 3 parts.
- Dependent upon multiple UART. Can start but not finish.
- Joanna: Board meeting may be discussing TF-A going live.
- TFC-31 needs to be completed in order to go live
- *Action*: *Leonardo* to put time estimates in TFC-40,41, & 42
- *Action: Don* add ST Ticket to backlog. Done -
- Shebu: Anything else blocking?
- Karl: No current blockers. TFC-34 causing intermittent failures.
- Fathi: Since in backlog, not being worked.
- Shebu: recommend continuing to monitor.
Attendees: Don, Ben C, Glen, Anton, Shebu, Joanna, Fathi, Matteo
Minutes:
- Glen: Prioritize LSS-2136 <https://projects.linaro.org/browse/LSS-2136>
- TF Infrastructure.
- Comments/patches are missing. Appears out of sync Anton to check
TF-M all in sync
- Anton: TF-M March/April planning a release. Want to make sure things
are prepped. Code Freeze March 18th. Then release after testing. Any
deployment hints helpful.
- Don't want infrastructure changes during the release period.
- Reviewed Kanban board
<https://projects.linaro.org/secure/RapidBoard.jspa?rapidView=300&projectKey…>
- Discuss tasks for Leonardo and Arthur
- Joanna: Gaps filling in. Might even find new things. Sandrine may
have found something overnight
- Kanban board
<https://projects.linaro.org/secure/RapidBoard.jspa?rapidView=300&projectKey…>
requires a login to Jira. Ask Don if need one.
- What about urgent LSS issues?
- Can still create LSS urgent tickets, but then create a TFC project
ticket in parallel that points to it. This is so that the Kanban board
shows all prioritized activities.
- ACTION: Add Karl to meeting
- ACTION: Make sure Karl can create tickets
- Shebu: Still working with Eric on aligning hardware into OpenCI.
Michel is the TF-M and is the POC for defining the ST board to go in.
- Plan to move this meeting to a new slot mid-March when times change.
