Skip to content

fix(ci): Fixes for liblsan0 packages in Bazell base image#15315

Merged
tapasmishra merged 7 commits intomagma:masterfrom
akhilamoyila9:topic/akhilamoyila9/testtprr
Oct 12, 2023
Merged

fix(ci): Fixes for liblsan0 packages in Bazell base image#15315
tapasmishra merged 7 commits intomagma:masterfrom
akhilamoyila9:topic/akhilamoyila9/testtprr

Conversation

@akhilamoyila9
Copy link
Copy Markdown
Contributor

@akhilamoyila9 akhilamoyila9 commented Oct 4, 2023

fix(ci): Fixes for liblsan0 packages in Bazel base image

Summary

LTE integration tests are failing

  1. The Magma Vagrant images used for LTE integration tests contain the latest version of GCC along with the liblsan0 package.
  2. However, the container image used to build the Magma Debian package contains an older version of GCC along with the liblsan0 package.
  3. This inconsistency is causing the MME service of Magma to crash during the integration test

Test Plan

  1. To resolve this issue, we need to upgrade the GCC and liblsan0 package on the base container image used to build the Debian package.
  2. This upgrade will ensure compatibility between the test environment and the package building environment, preventing the MME service from crashing during tests.

Additional Information

  • This change is backwards-breaking

Security Considerations

Signed-off-by: akhilamoyila9 <[email protected]>
@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines. label Oct 4, 2023
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Oct 4, 2023

Thanks for opening a PR! 💯

A couple initial guidelines

Howto

  • Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
  • Checks. All required CI checks must pass before merge.
  • Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

If this is your first Magma PR, also consider reading

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Oct 4, 2023

✔️ The Semantic PR check ended with status success. See instructions on formatting your commit and pull request titles.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Oct 4, 2023

DP Lint & Test

0 tests   0 ✔️  0s ⏱️
0 suites  0 💤
0 files    0

Results for commit 3bc3bf9.

♻️ This comment has been updated with latest results.

@akhilamoyila9 akhilamoyila9 changed the title fix(ci) fix(ci):added new line for testing Oct 4, 2023
changes:
	1) changed the push to registry condition to true

Signed-off-by: akhilamoyila9 <[email protected]>
@akhilamoyila9 akhilamoyila9 force-pushed the topic/akhilamoyila9/testtprr branch from 6fc0a33 to e38d824 Compare October 4, 2023 11:00
@akhilamoyila9 akhilamoyila9 requested a review from a team as a code owner October 4, 2023 11:00
@github-actions github-actions bot added the component: ci All updates on CI (Jenkins/CircleCi/Github Action) label Oct 4, 2023
changes:
	1) Added if block in build_dockerfile_bazel_base and build_dockerfile_devcontainer jobs
	2) Chnaged the PUSH_TO_REGISTRY condition to true

Signed-off-by: akhilamoyila9 <[email protected]>
@pull-request-size pull-request-size bot added size/S Denotes a PR that changes 10-29 lines. and removed size/XS Denotes a PR that changes 0-9 lines. labels Oct 9, 2023
@tapasmishra tapasmishra changed the title fix(ci):added new line for testing fix(ci): Fixes for liblsan0 packages in Bazell base image Oct 9, 2023
@tapasmishra tapasmishra self-requested a review October 9, 2023 09:45
@tapasmishra
Copy link
Copy Markdown

LGTM!

Copy link
Copy Markdown

@tapasmishra tapasmishra left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Copy Markdown
Contributor

@mohinali mohinali left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link
Copy Markdown
Contributor

@panyogesh panyogesh left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Copy Markdown
Contributor

@mohinali66 mohinali66 left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Copy Markdown
Member

@maxhbr maxhbr left a comment

Choose a reason for hiding this comment

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

  • This PR lacks a description
  • some commits just have the description fix(ci)
  • as this moves the guard to an earlier place in the pipeline, it stops the container to be built on PRs and in forks and therefore reduces test coverage

Comment thread .devcontainer/bazel-base/Dockerfile Outdated
Comment thread .github/workflows/docker-builder-devcontainer.yml Outdated
@tapasmishra
Copy link
Copy Markdown

  • This PR lacks a description
  • some commits just have the description fix(ci)
  • as this moves the guard to an earlier place in the pipeline, it stops the container to be built on PRs and in forks and therefore reduces test coverage

@maxhbr - I have asked to the engineer to update the description. Intentionally we have moved the guard to the earlier place to skip execution during the PR. It will fail pushing the image during the PR hence we can't merge the PR in the normal way. As this is a temporary arrangement and will be reverted back as soon as after the bazel-base image update I don't see any risk. Let me know your thoughts.

@tapasmishra
Copy link
Copy Markdown

  • This PR lacks a description
  • some commits just have the description fix(ci)
  • as this moves the guard to an earlier place in the pipeline, it stops the container to be built on PRs and in forks and therefore reduces test coverage

@maxhbr - I have asked to the engineer to update the description. Intentionally we have moved the guard to the earlier place to skip execution during the PR. It will fail pushing the image during the PR hence we can't merge the PR in the normal way. As this is a temporary arrangement and will be reverted back as soon as after the bazel-base image update I don't see any risk. Let me know your thoughts.

LTE Integration tests are in red on the CI dashboard and this temporary arrangement will help fixing the LTE integration issue.

changes:
  1.reverted the temporary changes in the Dockerfile

Signed-off-by: akhilamoyila9 <[email protected]>
@akhilamoyila9 akhilamoyila9 force-pushed the topic/akhilamoyila9/testtprr branch from ef8274e to 9696c6e Compare October 11, 2023 16:27
changes:
  1. Modified the condition of githib.event_ name

Signed-off-by: akhilamoyila9 <[email protected]>
@akhilamoyila9 akhilamoyila9 force-pushed the topic/akhilamoyila9/testtprr branch from 9acb9ec to 2dc106e Compare October 12, 2023 06:49
changes:
 1. Modified the condition of github.event_name

Signed-off-by: akhilamoyila9 <[email protected]>
@akhilamoyila9 akhilamoyila9 force-pushed the topic/akhilamoyila9/testtprr branch from 41a61ef to 2dc106e Compare October 12, 2023 06:56
@tapasmishra tapasmishra requested a review from maxhbr October 12, 2023 09:20
Copy link
Copy Markdown
Member

@maxhbr maxhbr left a comment

Choose a reason for hiding this comment

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

LGTM

@tapasmishra tapasmishra merged commit 0a7c8d4 into magma:master Oct 12, 2023
lucasgonze pushed a commit to lucasgonze/magma that referenced this pull request Feb 29, 2024
Temporary fixes to update the bazel-base image.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component: ci All updates on CI (Jenkins/CircleCi/Github Action) size/S Denotes a PR that changes 10-29 lines.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants