*Attendees*: Joanna, Xinyu, Matteo, Janos, Glen, Riku, Shebu, Anton, Ben, Don
*Actions*:
- Glen: Follow up on notes - Glen: Set up sync meeting to hear Riku/Leonardo/Anton/Joanna on proposing a solution on the git clone performance issue.
*Minutes*:
- Glen: TFC Kanban board review - Glen: Chromebooks stuck in customs - working paperwork now - Glen: Cypress & NXP platforms both underway - Glen: Performance issues update: (TFC-171, 172, 164) - Ben: Limited CI Number of jobs to help relieve a performance issue. - Riku: Impact - slower builds. - Anton: were we testing on staging? - Ben: No - Should we allocate resources to work on performance? - Joanna: Would work on server scaling versus Expect scripts - Riku: TF-M build, launches over 100 builds, then git clones turn into 400 simultaneous git clones - need to re-factor to do clone up front. - Riku/Leonardo - 1-2 week estimate - Anton has some ideas - sync w/ him on potential solution. Once agreed, begin the work. - Glen: Meeting set up for tomorrow to discuss code coverage state and how Arm might be able to help.
Just an FYI;
- Glen: Set up sync meeting to hear Riku/Leonardo/Anton/Joanna on proposing a solution on the git clone performance issue.
Meeting w/ Joanna, Anton, Riku, Leonardo
For TF-M: reviewed proposal(below) by Anton to resolve git check outs. For TF-A: Discussed how this should happen in TF-A This will be tested in stage before pushing to production. *Leonardo will start working on the changes for TF-A immediately.*
If there are any questions, let us know.
Thanks; -g
Anton's proposal:
Let me share my thoughts ahead of the meeting about github download optimisation.
By default TF-M build system downloads all dependent repos for each build to ensure the latest version. Each dependency has a variable, specifying a path to the repo, settled to “DOWNLOAD” by default. “DOWNLOAD” keyword means the build machine has no local copy and the repo shall be cloned. This is documented here:
https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/instru... https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/instructions/tfm_build_instruction.html#manual-dependency-management
I suggest to extend the building process by adding a preliminary CI step of downloading repos once and then specify paths to them for consequent builds via command line parameter, like for example: -DMBEDCRYPTO_PATH=<path for MbedCrypto repo>
Going further, all those build parameters could be gathered in a file and specified for a build using the option TFM_EXTRA_CONFIG_PATH.
Meeting held between Leonardo, Saul and Joanna to discuss way forward with blocking issues for TF-A and TF-M.
Way forward identified with both and Leonardo and Saul will talk as required.
Joanna
On 08/09/2021, 16:13, "Tf-openci-triage on behalf of Glen Valante via Tf-openci-triage" <tf-openci-triage-bounces@lists.trustedfirmware.org on behalf of tf-openci-triage@lists.trustedfirmware.org> wrote:
Just an FYI;
> - Glen: Set up sync meeting to hear Riku/Leonardo/Anton/Joanna on > proposing a solution on the git clone performance issue.
Meeting w/ Joanna, Anton, Riku, Leonardo
For TF-M: reviewed proposal(below) by Anton to resolve git check outs. For TF-A: Discussed how this should happen in TF-A This will be tested in stage before pushing to production. *Leonardo will start working on the changes for TF-A immediately.*
If there are any questions, let us know.
Thanks; -g
Anton's proposal:
Let me share my thoughts ahead of the meeting about github download optimisation.
By default TF-M build system downloads all dependent repos for each build to ensure the latest version. Each dependency has a variable, specifying a path to the repo, settled to “DOWNLOAD” by default. “DOWNLOAD” keyword means the build machine has no local copy and the repo shall be cloned. This is documented here:
https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/instru... https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/instructions/tfm_build_instruction.html#manual-dependency-management
I suggest to extend the building process by adding a preliminary CI step of downloading repos once and then specify paths to them for consequent builds via command line parameter, like for example: -DMBEDCRYPTO_PATH=<path for MbedCrypto repo>
Going further, all those build parameters could be gathered in a file and specified for a build using the option TFM_EXTRA_CONFIG_PATH. --
Linaro http://www.linaro.org Glen Valante | /Sr. Technical Program Manager/ T: +1.508.517.3461 tel:1617-320-5000 glen.valante@linaro.org mailto:glen.valante@linaro.org | Skype: gvalante callto:gvalante
-- Tf-openci-triage mailing list Tf-openci-triage@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.
On Wed, 8 Sept 2021 at 10:13, Glen Valante via Tf-openci-triage < tf-openci-triage@lists.trustedfirmware.org> wrote:
Just an FYI;
- Glen: Set up sync meeting to hear Riku/Leonardo/Anton/Joanna on proposing a solution on the git clone performance issue.Meeting w/ Joanna, Anton, Riku, Leonardo
For TF-M: reviewed proposal(below) by Anton to resolve git check outs. For TF-A: Discussed how this should happen in TF-A This will be tested in stage before pushing to production. *Leonardo will start working on the changes for TF-A immediately.*
A brief update before tomorrow's sync:
A Strategy for a share folder at TF-A CI has been proposed at https://review.trustedfirmware.org/c/ci/tf-a-job-configs/+/11449
Now I am moving into the TF-M CI with the same goal (reducing clones through a share folder)
Regards, lsg
If there are any questions, let us know.
Thanks; -g
Anton's proposal:
Let me share my thoughts ahead of the meeting about github download optimisation.
By default TF-M build system downloads all dependent repos for each build to ensure the latest version. Each dependency has a variable, specifying a path to the repo, settled to “DOWNLOAD” by default. “DOWNLOAD” keyword means the build machine has no local copy and the repo shall be cloned. This is documented here:
https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/instru... < https://tf-m-user-guide.trustedfirmware.org/docs/technical_references/instru...
I suggest to extend the building process by adding a preliminary CI step of downloading repos once and then specify paths to them for consequent builds via command line parameter, like for example: -DMBEDCRYPTO_PATH=<path for MbedCrypto repo>
Going further, all those build parameters could be gathered in a file and specified for a build using the option TFM_EXTRA_CONFIG_PATH. -- Linaro http://www.linaro.org Glen Valante | /Sr. Technical Program Manager/ T: +1.508.517.3461 tel:1617-320-5000 glen.valante@linaro.org mailto:glen.valante@linaro.org | Skype: gvalante callto:gvalante
-- Tf-openci-triage mailing list Tf-openci-triage@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-openci-triage
tf-openci-triage@lists.trustedfirmware.org
-
Don Harbin -
Glen Valante -
Joanna Farley -
Leonardo Sandoval