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 Community Call (March 5, 2024 edition) #5090

Closed
smlambert opened this issue Feb 22, 2024 · 3 comments
Closed

AQAvit Community Call (March 5, 2024 edition) #5090

smlambert opened this issue Feb 22, 2024 · 3 comments
Assignees

Comments

@smlambert
Copy link
Contributor

smlambert commented Feb 22, 2024

This meeting is scheduled for: March 5, 2024 at 10 am EST | 3 pm UTC
and will be recorded to share with our colleagues who may not be able to attend.

Join Zoom Meeting link

Meeting ID: 865 6128 4227
Passcode: 045388


We have shifted away from bi-weekly calls to a more doable 6 calls per year (typically 4-6 weeks after the JDK release period) which will be added to the public Adoptium community calendar, if you wish to import the calendar use this link.

The content of these AQAvit community calls is intended to summarize what new features, challenges, and changes have happened in the AQAvit project.

Proposed agenda:

@smlambert smlambert self-assigned this Feb 27, 2024
@llxia
Copy link
Contributor

llxia commented Mar 5, 2024

CRIU Portable Testing:
image

@smlambert
Copy link
Contributor Author

smlambert commented Mar 5, 2024

Minutes and additional context:

AQAvit 1.0.0 release and graduation

  • in addition to our regular Github releases we also now have done an Eclipse Foundation release, which adds in checks for things like Intellectual Property rights, proper use of Trademarks, security policy and contributor documentation, etc. These things were required in order to graduate from incubator to full-fledged project at Eclipse Foundation. Read the blog for details: https://adoptium.net/blog/2024/02/aqavit-graduation-ceremony/

New features Review

New test targets

FIPS support

CRIU support

TAP verification tools

  • Great improvement, and more to come with this feature gives more support for vendors listing in the marketplace, allows them to create jobs that can help verify the set of TAP files that they share through the marketplace API as part of their listing (as evidence that all tests were run and passed) - Related: Add TAP pipeline #4285 and Add checks in TAP file verification #5067 and work in progress example job here

pre-stage 3rd party test libs

jck_custom updates, rerun jck**_custom links

Auto-update testenv.properties file

  • if JDKxx_BRANCH -ga tag is not available fetch the latest one with the same prefix, Check testenv.properties JDKxx_BRANCH tags #5102 helps reduce the need for last minute changes during release periods and reduction in steps in the release checklist (happier release champions)

Onboarding new vendors / teams / contributors

  • In just over the past year, we have seen 29 new contributors to aqa-tests (tags v0.9.6-v1.0.1). Welcome to our new contributors who hail from universities, and from a broad range of companies including Red Hat, IBM, Microsoft, Alibaba, Loongson and Rivos (woohoo, RISC-V test plan!).
  • Welcome to new colleagues from Fujitsu who are asking great and detailed questions on AQAvit tools and pipelines usage, questions which help give us good direction on documentation improvements Add Fujitsu TKG#501

Stretch Goals for 2024

Over and above the daily deliverables that those who participate in AQAvit must prioritize, we have added a few 'wishlist' or 'stretch' goals that we intend to look at in 2024. These include, but are not limited to:

AOB

  • proper set of test metrics (and education around what 'progress' means)
    • EPIC: Provide AQA Test metrics per release #5121 - Call for participation, please read the issue and add comments if you have additional metrics you would like us to consider. We will create a table of potential metrics to gather, with a description of how to gather, and what is the main purpose of the metric (what do we hope to achieve by monitoring it)
  • Additional resources available (new docs & recordings)
    • Teaser on the Triage presentation and demo

@smlambert
Copy link
Contributor Author

Recording link on youtube

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

No branches or pull requests

2 participants