Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

medic / cht-core Public

Notifications You must be signed in to change notification settings
Fork 219
Star 473

Code
Issues 617
Pull requests 40
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Scalability Workflow

chore(#9730): bump version (#9744) (#9745) #354

Sign in to view logs

Sign in to view logs

chore(#9730): bump version (#9744) (#9745)

chore(#9730): bump version (#9744) (#9745) #354

Summary
Jobs
- Set up Medic on EC2 and Execute Jmeter on another EC2
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

2 errors

The job running on runner GitHub Actions 43 has exceeded the maximum execution time of 360 minutes.

Start EC2 and CHT

The operation was canceled.

Set up Medic on EC2 and Execute Jmeter on another EC2

Set up Medic on EC2 and Execute Jmeter on another EC2

failed Jan 15, 2025 in 6h 0m 13s

Loading

Re-running jobs...

You can’t perform that action at this time.