generated from oracle/template-repo
-
Notifications
You must be signed in to change notification settings - Fork 18
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
[draft] CI Improvements #125
Draft
brenns10
wants to merge
12
commits into
oracle-samples:main
Choose a base branch
from
brenns10:remove_coverage
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Gitlab CI tests have intermittently failed for vmcore tests due to race conditions with the parallel execution for coverage. The fact of the matter is that the coverage information is not currently reported by any of our CI tests, and no developers use it locally. It's just more trouble than it's worth, so remove it. Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
Using "python3" runs the risk of a different python version getting used. The whole point of testing/rpm.py is to run *within* the current Python environment, so use sys.executable to make that certain. Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
There have been many releases since the annotated ones. It should be fine to unpin now. Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
Currently the only CTF-related tests for CI are the ones which run against vmcores. The heavyvm tests can easily support CTF, so run it. It should not add enough time to cause any issues with CI. Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
The CTF data for UEK4 is fully broken; we cannot support it. Skip running live tests for UEK4 CTF. Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
The test suite name was being reported as "CTF" only if the tests were run against vmcores. With heavyvm (and possibly litevm) tests running against CTF, this means that the XML test reports no longer contain the correct debuginfo in their name. Live tests also simply report "live" which makes it very difficult to understand which test suite is for which version. Report the uname in this case, which includes both UEK and OL version, though it's not as nice as simply saying "OLX UEKY". Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
The value proposition of tox is allowing you to run your tests against a lot of different Python versions at the same time. It can be really useful, but honestly it hasn't been helpful in drgn-tools. We typically only have one (maybe two) Python versions available, and frequently we can only run tests against one anyway. Testing multiple Python versions is done in Github CI, but tricking tox into only running tests for one version is actually a pain! All told, it's caused more pain than gain, so let's do away with it in testing. The tox.ini still exists and is used for generating docs, but we can eliminate that smaller issue in a subsequent commit. Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
This is a totally unnecessary dependency. We only need to have one operation: concatenating two test results. Thankfully, that can be done directly with the python XML support. Drop the dependency. Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
The coverage option has been removed from the rest of the tests. It looks like the xml option was simply never implemented. Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
oracle-contributor-agreement
bot
added
the
OCA Verified
All contributors have signed the Oracle Contributor Agreement.
label
Oct 30, 2024
brenns10
force-pushed
the
remove_coverage
branch
3 times, most recently
from
October 30, 2024 22:33
98c828b
to
6b3df3f
Compare
Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
brenns10
force-pushed
the
remove_coverage
branch
from
October 30, 2024 22:45
0bc1cf0
to
597def6
Compare
It got broken by the removal of tox. It also needs to handle CTF in the same run for some cases too. Fix it all up. Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
brenns10
force-pushed
the
remove_coverage
branch
from
October 30, 2024 23:03
597def6
to
ec0f0cd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request contains several improvements to our CI.
It's not ready. Still remaining: