You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I am missing key points, please add them as comments to this issue (which serves only as a way to capture notable parts of the discussion.
We can plan to meet regularly (monthly? or as needed), to discuss updates to open perf testing and tools, decisions/discussion on how best to provide control and config of certain tests that require multi-machine setup, improvements/ideas to stabilize external test targets, running tests via dynamic parallelization or any other topics that may be useful. If we do meet regularly, we can consider it an AQAvit meeting for timezones that can not comfortably attend the bi-weekly Wednesday AQAvit meetings.
The text was updated successfully, but these errors were encountered:
Create then close this issue as a record of today's discussion (with handy links to related issues). Attendees invited to add any missing notes as comments to the closed issue.
Presentation from Alibaba team on next steps:
In our subsequent discussion, the following links/issues/enhancements were noted:
“AQA You Are Soaking in It” presentation from early 2020
External tests to consider adding: Add more container-based 3rd party application tests #172 (I have added netty and spring to this list, so we do not need a separate issue, just PRs to incorporate those)
Identify and prioritize open perf benchmarks: Identify and prioritize open perf benchmarks #1112
Add external_custom target (potentially getting help from students on this item): Add external_custom target #2076
Necessary enhancement to support vendor specific tests: Add support for JDK_VENDOR in playlists TKG#115
Discussion/enhancement issue for discussing where best to contribute "unsafe checker" tool: Contribute and incorporate "unsafe checker" tool #2077
If I am missing key points, please add them as comments to this issue (which serves only as a way to capture notable parts of the discussion.
We can plan to meet regularly (monthly? or as needed), to discuss updates to open perf testing and tools, decisions/discussion on how best to provide control and config of certain tests that require multi-machine setup, improvements/ideas to stabilize external test targets, running tests via dynamic parallelization or any other topics that may be useful. If we do meet regularly, we can consider it an AQAvit meeting for timezones that can not comfortably attend the bi-weekly Wednesday AQAvit meetings.
The text was updated successfully, but these errors were encountered: