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

Undesired performance with update-only setting at first run #111

Open
Betristor opened this issue Sep 28, 2023 · 0 comments
Open

Undesired performance with update-only setting at first run #111

Betristor opened this issue Sep 28, 2023 · 0 comments

Comments

@Betristor
Copy link

I had a workflow which will check a summary file after tests.
The logs are as follows:

Run mshick/add-pr-comment@v2
  with:
    update-only: true
    preformatted: true
    message-path: benchmark/summary.txt
......
  env:
    ARTIFACTS_PATH: ~/.julia/artifacts
    PACKAGES_PATH: ~/.julia/packages
    REGISTRIES_PATH: ~/.julia/registries
    PRECOMPILATION_CACHE_PATH: 
    JULIA_PKG_SERVER_REGISTRY_PREFERENCE: eager
no existing comment found and update-only is true, exiting

I desire that at the first run of this workflow, if the summary file exists, then a comment should be created to notify me and then in later runs, the comments should be updated if the condition still holds. But it seems that update-only setting could not statisfy both.

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

No branches or pull requests

1 participant