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

chore : do not generate sed backup file while generating release info #4530

Merged

Conversation

rohanKanojia
Copy link
Contributor

@rohanKanojia rohanKanojia commented Dec 27, 2024

Description

While working on windows, I observed that make test always generates two temporary files after execution:

        sed9zmH5g
        sedOFQN7I

Their content was similar to release-info.json. On further debugging I found out they are getting created as backup files for sed replacement in Makefile.

crc/Makefile

Lines 273 to 274 in 6e99137

@sed -i'' -e s/@GIT_COMMIT_SHA@/$(COMMIT_SHA)/ $(RELEASE_INFO)
@sed -i'' -e s/@OPENSHIFT_VERSION@/$(OPENSHIFT_VERSION)/ $(RELEASE_INFO)

We had the option to not add any backup file, but somehow that option doesn't seem to work on windows.

Relates to: 2636e4a

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change
  • Chore (non-breaking change which doesn't affect codebase;
    test, version modification, documentation, etc.)

Proposed changes

Replace '' with "" to instruct sed to not generate a backup file while performing the inline replacement. For some reason '' is not getting picked up on powershell and backup files are being generated.

Testing

make test should no longer generate additional files after execution on Windows. I have only verified this on Linux and Windows, it might be possible that these changes break make test on macOS

Contribution Checklist

  • I Keep It Small and Simple: The smaller the PR is, the easier it is to review and have it merged
  • I have performed a self-review of my code
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Which platform have you tested the code changes on?
    • Linux
    • Windows
    • MacOS

While working on windows, I observed that `make test` always generates
two temporary files after execution:
```
        sed9zmH5g
        sedOFQN7I
```
Their content was similar to release-info.json. On further debugging I
found out they are getting created as backup files for sed replacement
in Makefile.

Signed-off-by: Rohan Kumar <[email protected]>
Copy link

openshift-ci bot commented Dec 27, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link

openshift-ci bot commented Dec 27, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign cfergeau for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rohanKanojia rohanKanojia marked this pull request as ready for review December 30, 2024 06:17
@openshift-ci openshift-ci bot requested review from anjannath and gbraad December 30, 2024 06:17
Copy link

openshift-ci bot commented Dec 30, 2024

@rohanKanojia: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/integration-crc edbc0ad link true /test integration-crc
ci/prow/e2e-crc edbc0ad link true /test e2e-crc

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@praveenkumar praveenkumar merged commit e09b37a into crc-org:main Dec 31, 2024
31 of 36 checks passed
@rohanKanojia rohanKanojia deleted the pr/sed-generating-backup branch December 31, 2024 05:48
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