Reviewed Kanban,
- Glen: TFC-31 and 25: Patches out and waiting for validation.
- TFC-23: User Guide ported to markdown
- TF-4: Enable mbedTLS. Meetings planned to break the task down.
- TFC-46: Once ST boards received, have Arthur verifying locally, then
move to LAVA lab.
- Sending first two boards. ST will send the final three soon.
- Joanna: Any TF-A boards?
- No, but Chromebooks next in board enablement queue
- Glen: Working to provide multiple tasks to the team to prevent idle
time
- TFC-36 - Support expect Logic, making progress now but could be a few
weeks.
- TFC-7: Code Coverage.
- Joanna, OK with priorities, but TF-A would like TFC-36 first if
doesn't create issues with other teams.
- Joanna: Tech Forum from last week. Might see server load pickup as
teams begin to leverage the OpenCI. Another MISRA tool was mentioned
- Regarding small tasks. Let's plan to make tickets for that. Now that
tickets coming thru TFC, need to have a quick way to process these and hand
off to infrastructure team.
- Agreed that no OpenCI mail list exists, so will create one.
- Anton: TF-M release last Friday - went very smooth.
Don
sure, makes sense, I do not plan to start the coverage code task. My hands
are now on the expect-to-lava migration work.
lsg
On Wed, 7 Apr 2021 at 10:36, Glen Valante via Tf-openci-triage <
tf-openci-triage(a)lists.trustedfirmware.org> wrote:
>
> Lets confirm gaps are completed - delivered and accepted by ARM, before
> going on. :)
> -g
>
>
> On 4/7/2021 11:24 AM, Leonardo Sandoval via Tf-openci-triage wrote:
> > Thanks Joanna.
> >
> > I have not fully read the documentation from the qa-tools project but
> does
> > it mean that we start at some point
> https://projects.linaro.org/browse/TFC-7
> > ?
> >
> > lsg
> >
> > On Wed, 7 Apr 2021 at 04:33, Joanna Farley via Tf-openci-triage <
> > tf-openci-triage(a)lists.trustedfirmware.org> wrote:
> >
> >> I promised to send a link to code coverage tooling on
> >> https://gitlab.arm.com/tooling/qa-tools
> >>
> >> Joanna
> >>
> >>
> >> On 06/04/2021, 23:08, "Tf-openci-triage on behalf of Don Harbin via
> >> Tf-openci-triage" <tf-openci-triage-bounces(a)lists.trustedfirmware.org
> on
> >> behalf of tf-openci-triage(a)lists.trustedfirmware.org> wrote:
> >>
> >> Attendees: Fathi, Glen, Joanna, Matteo, Shebu, Don
> >>
> >> Minutes:
> >>
> >> - Discuss a way for people to ask questions and submit issues
> found
> >> for
> >> OpenCI.
> >> - Start with a dedicated mail list
> >> - Shebu: Also need to revisit the Roles and Responsibilities
> >> email
> >> Shebu sent last week.
> >> - Action: Glen, determine who needs to create tickets in TFC.
> >> - Joanna, Anton
> >> - Action: Create maillist for OpenCI comments from
> users/subscribers
> >> - Glen: Code coverage tool ticket status discussed
> >> - OpenCI team needs to follow up w/ ST on a kick off meeting for
> >> getting
> >> their board into OpenCI.
> >> --
> >> 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.
> >> --
> >> Tf-openci-triage mailing list
> >> Tf-openci-triage(a)lists.trustedfirmware.org
> >> https://lists.trustedfirmware.org/mailman/listinfo/tf-openci-triage
> >>
>
> --
>
> 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
>
Lets confirm gaps are completed - delivered and accepted by ARM, before
going on. :)
-g
On 4/7/2021 11:24 AM, Leonardo Sandoval via Tf-openci-triage wrote:
> Thanks Joanna.
>
> I have not fully read the documentation from the qa-tools project but does
> it mean that we start at some point https://projects.linaro.org/browse/TFC-7
> ?
>
> lsg
>
> On Wed, 7 Apr 2021 at 04:33, Joanna Farley via Tf-openci-triage <
> tf-openci-triage(a)lists.trustedfirmware.org> wrote:
>
>> I promised to send a link to code coverage tooling on
>> https://gitlab.arm.com/tooling/qa-tools
>>
>> Joanna
>>
>>
>> On 06/04/2021, 23:08, "Tf-openci-triage on behalf of Don Harbin via
>> Tf-openci-triage" <tf-openci-triage-bounces(a)lists.trustedfirmware.org on
>> behalf of tf-openci-triage(a)lists.trustedfirmware.org> wrote:
>>
>> Attendees: Fathi, Glen, Joanna, Matteo, Shebu, Don
>>
>> Minutes:
>>
>> - Discuss a way for people to ask questions and submit issues found
>> for
>> OpenCI.
>> - Start with a dedicated mail list
>> - Shebu: Also need to revisit the Roles and Responsibilities
>> email
>> Shebu sent last week.
>> - Action: Glen, determine who needs to create tickets in TFC.
>> - Joanna, Anton
>> - Action: Create maillist for OpenCI comments from users/subscribers
>> - Glen: Code coverage tool ticket status discussed
>> - OpenCI team needs to follow up w/ ST on a kick off meeting for
>> getting
>> their board into OpenCI.
>> --
>> 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.
>> --
>> Tf-openci-triage mailing list
>> Tf-openci-triage(a)lists.trustedfirmware.org
>> https://lists.trustedfirmware.org/mailman/listinfo/tf-openci-triage
>>
--
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>
Thanks Joanna.
I have not fully read the documentation from the qa-tools project but does
it mean that we start at some point https://projects.linaro.org/browse/TFC-7
?
lsg
On Wed, 7 Apr 2021 at 04:33, Joanna Farley via Tf-openci-triage <
tf-openci-triage(a)lists.trustedfirmware.org> wrote:
> I promised to send a link to code coverage tooling on
> https://gitlab.arm.com/tooling/qa-tools
>
> Joanna
>
>
> On 06/04/2021, 23:08, "Tf-openci-triage on behalf of Don Harbin via
> Tf-openci-triage" <tf-openci-triage-bounces(a)lists.trustedfirmware.org on
> behalf of tf-openci-triage(a)lists.trustedfirmware.org> wrote:
>
> Attendees: Fathi, Glen, Joanna, Matteo, Shebu, Don
>
> Minutes:
>
> - Discuss a way for people to ask questions and submit issues found
> for
> OpenCI.
> - Start with a dedicated mail list
> - Shebu: Also need to revisit the Roles and Responsibilities
> email
> Shebu sent last week.
> - Action: Glen, determine who needs to create tickets in TFC.
> - Joanna, Anton
> - Action: Create maillist for OpenCI comments from users/subscribers
> - Glen: Code coverage tool ticket status discussed
> - OpenCI team needs to follow up w/ ST on a kick off meeting for
> getting
> their board into OpenCI.
> --
> 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.
> --
> Tf-openci-triage mailing list
> Tf-openci-triage(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tf-openci-triage
>
I promised to send a link to code coverage tooling on https://gitlab.arm.com/tooling/qa-tools
Joanna
On 06/04/2021, 23:08, "Tf-openci-triage on behalf of Don Harbin via Tf-openci-triage" <tf-openci-triage-bounces(a)lists.trustedfirmware.org on behalf of tf-openci-triage(a)lists.trustedfirmware.org> wrote:
Attendees: Fathi, Glen, Joanna, Matteo, Shebu, Don
Minutes:
- Discuss a way for people to ask questions and submit issues found for
OpenCI.
- Start with a dedicated mail list
- Shebu: Also need to revisit the Roles and Responsibilities email
Shebu sent last week.
- Action: Glen, determine who needs to create tickets in TFC.
- Joanna, Anton
- Action: Create maillist for OpenCI comments from users/subscribers
- Glen: Code coverage tool ticket status discussed
- OpenCI team needs to follow up w/ ST on a kick off meeting for getting
their board into OpenCI.
--
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.
Attendees: Fathi, Glen, Joanna, Matteo, Shebu, Don
Minutes:
- Discuss a way for people to ask questions and submit issues found for
OpenCI.
- Start with a dedicated mail list
- Shebu: Also need to revisit the Roles and Responsibilities email
Shebu sent last week.
- Action: Glen, determine who needs to create tickets in TFC.
- Joanna, Anton
- Action: Create maillist for OpenCI comments from users/subscribers
- Glen: Code coverage tool ticket status discussed
- OpenCI team needs to follow up w/ ST on a kick off meeting for getting
their board into OpenCI.
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
