Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AQAvit Meeting: Feb 22, 2023 #4321

Closed
smlambert opened this issue Feb 8, 2023 · 1 comment
Closed

AQAvit Meeting: Feb 22, 2023 #4321

smlambert opened this issue Feb 8, 2023 · 1 comment

Comments

@smlambert
Copy link
Contributor

smlambert commented Feb 8, 2023

Join Zoom Meeting link

Meeting ID: 865 6128 4227
Passcode: 045388

This meeting is part of the public Adoptium community calendar, if you wish to import the calendar use this link

Proposed Agenda:

@smlambert
Copy link
Contributor Author

smlambert commented Feb 23, 2023

Meeting recording link: https://youtu.be/Vd5fdzBQ-oU

Minutes:

  • run-aqa & aqafer Github actions enhancements for AQAvit verification
    Joe shared what updates he has been working on in https://github.com/microsoft/aqafer (based from a smlambert/aqafer). To make aqafer more useful to vendors, the updates include:
    • ability to use internal runners (pool of machines)
    • run in parallel in docker (paralleltest-docker.yml)
      Joe posed some questions/challenges that include:
    • how to verify at the end of the run that the binary under test is the one that also has been TCKed, and the one to publish, or does this AQAvit verification have to happen after publish. We mentioned the audit script that Lan recently added and also that this can happen prior to uploading the TAP artifacts near the end of the workflow.
    • Also, a question around how to hook the aqafer workflow into other workflows (pass a build artifact off to it), similar to the SDK_RESOURCE parameter in Jenkins (which I believe is supported by run-aqa, but has subtle differences, which we should attempt to resolve)
    • Let's define a standard naming convention or guidelines for vendors to follow, if they want to use their own runners for testing using Github actions
    • Action: Shelley to raise an aqa-tests issue to communally resolve some of the questions posed by Joe and also plan to bring aqafer under the EF adoptium Github org eventually
  • Last topics, very quickly mention the use of 2 week iterations in the 1Q project plan, to better communicate who is focused on what, and what is upcoming. Also a big update to https://github.com/adoptium/aqa-tests/wiki/How-to-Run-a-Grinder-Build-on-Jenkins with more to follow very soon (under EPIC: Centralize and update test documentation #1558)

Link to next meeting: #4362

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Done
Development

No branches or pull requests

1 participant