Hi Guys,
Sorry, my broadband went down after 20 minutes of the meeting and by the time it recovered the meeting had finished.
Regarding TFC-29 I'll provide the information to Matteo/Shebu they need to help with the prioritisation.
Joanna
On 04/05/2021, 14:04, "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: Anton, Joanna, Glen, Ben, Don, Fathi, Shebu
Minutes:
- TFC-23: Doc is ready still need to get readthedocs front end added.
In progress
- Glen: Still planning on meeting w/ Malcolm on reproducing the
infrastructure.
- TFC-29 Joanna: Need more than QEMU support for Hafnium. Would like the
pipeline automated - another FVP model in a container?
- Glen: T-Shirt sized at 2 weeks, booked up on current work
- Need some input from Matteo/Shebu on this
- Cancel the ticket regarding maillist down. It's no longer down.
- TFC-4: Still sizing this. Could consume a person for a longer
period.
- Chromebooks. Since only one USB-C port, can't remove the battery.
Will be receiving other models for long term.
- ST Board targeted for completion next week.
- Fathi: Still need the remaining ST boards to Lab.
- Arthur will be submitting merge requests
- Shebu: MBedTLS status -
- Glen: Leonardo planned to move onto this shortly
- Glen: IP review needs to still happen.
- Shebu: Review is likely a month away - understand this isn't a
blocker. If becomes one, please escalate to Shebu
- Shebu: Note that TFC-1 and TFC-29 are both getting re-prioritized.
- Shebu: Can bring up backlog in next week's board meeting as well.
- Did some re-ordering of the backlog to bring the top few to the top of
the backlog priority
-
--
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: Anton, Joanna, Glen, Ben, Don, Fathi, Shebu
Minutes:
- TFC-23: Doc is ready still need to get readthedocs front end added.
In progress
- Glen: Still planning on meeting w/ Malcolm on reproducing the
infrastructure.
- TFC-29 Joanna: Need more than QEMU support for Hafnium. Would like the
pipeline automated - another FVP model in a container?
- Glen: T-Shirt sized at 2 weeks, booked up on current work
- Need some input from Matteo/Shebu on this
- Cancel the ticket regarding maillist down. It's no longer down.
- TFC-4: Still sizing this. Could consume a person for a longer
period.
- Chromebooks. Since only one USB-C port, can't remove the battery.
Will be receiving other models for long term.
- ST Board targeted for completion next week.
- Fathi: Still need the remaining ST boards to Lab.
- Arthur will be submitting merge requests
- Shebu: MBedTLS status -
- Glen: Leonardo planned to move onto this shortly
- Glen: IP review needs to still happen.
- Shebu: Review is likely a month away - understand this isn't a
blocker. If becomes one, please escalate to Shebu
- Shebu: Note that TFC-1 and TFC-29 are both getting re-prioritized.
- Shebu: Can bring up backlog in next week's board meeting as well.
- Did some re-ordering of the backlog to bring the top few to the top of
the backlog priority
-
Attendees: Don, Glen, Matteo, Shebu, Ben, Fathi, Joanna
- Matteo: Need to start scheduling in the Google platforms
- Don - A kickoff for this activity is already scheduled today to
start getting hardware ready
- *Action: Joanna* to create ticket for FVP version update related to
https://review.trustedfirmware.org/c/ci/tf-a-ci-scripts/+/9793
- Open CI team will then size the effort
- Move to approved at a higher priority
- An epic with 2 stories. TFC-58 - create two tickets under this.
Short term and long term.
- Don discussed TFC-88 and how to prioritize the need to validate/audit
disaster recovery. Needs a t-shirt size.
Attendees:
Minutes:
- Glen: Arthur received the two ST boards. STM32L
- Glen: Plan to meet w/ Dave on MBed TLS
- Glen: Code Coverage tooling making progress.
- Glen: Code Quality Metrics and a couple backlog issues
- TFC-82 - Adding authentication to LAVA. Has been done before, so
shouldn't be too difficult.
- Matteo - TFC-82 looks like a gap to close and would suggest putting above
code metrics.
- Glen: TFC-76, Juno errors.
- Joanna, there may be some tests that need re-worked. The board is failing
w/ a USB timeout at the Jenkins level. Needs to be more robust.
- Fathi: The fix requires a yet-to-be-used API call so a slight risk to
deploy
- TFC-45 moved to SC Approved. Don: Let's talk to Julian about getting the
Chromebooks.
- Action: Don reach out to Julius to set up a sync with him and Open CI
team to begin integrating one of his platforms into the lab. *Done*
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.
