This repository was archived by the owner on Mar 25, 2026. It is now read-only.
Fix to run benchmark on remote server#248
Merged
KotaTakahashi9320 merged 5 commits intomainfrom Jun 30, 2023
Merged
Conversation
83ea54f to
90b9e52
Compare
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Fix to run benchmark on remote server
Purpose
Because github action has a 6 hour limit and the benchmark stops in the middle of the action.
Contents
Fix github action to send only requests from github action
Add shell script to run benchmark
Sent result to Slack
Testing Methods Performed
Example of a message sent to slack
