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

test: update packages on security status test #3300

Merged
merged 1 commit into from
Sep 11, 2024
Merged

Conversation

lucasmoura
Copy link
Contributor

Why is this needed?

For the Noble securitu-status test, we need one package with an upgrade from security and another for updates. The past packages now both have candidates on the security pocket. We are now updating the package to have that distinction again

Test Steps

Run the modified integration test to see that it works


  • (un)check this to re-run the checklist action

For the Noble securitu-status test, we need one package
with an upgrade from security and another for updates.
The past packages now both have candidates on the security
pocket. We are now updating the package to have that distinction
again
Copy link

PR Checklist

How to use this checklist

How to use this checklist

PR Author

For each section, check a box when it is true.
Uncheck a box if it becomes un-true.
Then check the box at the bottom of the PR description to re-run the action that creates this checklist.
The action that creates and updates this comment will retain your edits.
The action will fail if the checklist is not completed.

PR Reviewer

Check that the PR checklist action did not fail.
Double check that the author filled out the checklist accurately.
If you disagree with a checklist item, start a conversation.
For example, the author may say they don't think integration tests are necessary, but you may disagree.

Bug References

None.

Confirm

  • I've properly referenced all bugs that this PR fixes
How to properly reference fixed bugs
  • If this PR is related to a Jira item, include an SC-1234 reference in the PR title
  • If this PR is fixes a GitHub issue, include a Fixes: #1234 reference in the commit that fixes the issue
  • If this PR is fixes a Launchpad bug, include a LP: #12345678 reference in the commit that fixes the issue

Test Updates

Unit Tests

  • I have updated or added any unit tests accordingly
  • No unit test changes are necessary for this change

Integration Tests

  • I have updated or added any integration tests accordingly
  • No integration test changes are necessary for this change

Documentation

  • Changes here need to be documented and I have referenced the docs PR in the description
  • No documentation updates are necessary for this change

Does this PR require review from someone outside the core ubuntu-pro-client team?

  • Yes, and I have requested those reviews via GitHub
  • No

| noble | lxd-container | xxd=2:9.1.0016-1ubuntu7 | less=590-2ubuntu2 |
| release | machine_type | pkg_in_updates | pkg_in_security |
| xenial | lxd-container | base-files=9.4ubuntu4 | wget=1.17.1-1ubuntu1 |
| noble | lxd-container | xz-utils=5.6.1+really5.4.5-1 | less=590-2ubuntu2 |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we can pick a package which has less chance of getting security updates at least soon, and xz scares me a bit.
However, I picked xxd and now here we are.
I think this is good and we fix the test again when needed.

@renanrodrigo renanrodrigo merged commit cdf5ba3 into next-v35 Sep 11, 2024
20 of 24 checks passed
@renanrodrigo renanrodrigo deleted the fix-tests branch September 11, 2024 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants