Skip to content

Navigation Menu

Explore
By size
By industry
By use case
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

missionpinball / mpf Public

Notifications You must be signed in to change notification settings
Fork 143
Star 216

Code
Issues 100
Pull requests 18
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Test on all platforms

Gracefully handle startup crashes without trigger downstream errors #677

Sign in to view logs

Sign in to view logs

Gracefully handle startup crashes without trigger downstream errors

Gracefully handle startup crashes without trigger downstream errors #677

Summary
Jobs
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

2 errors

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

The operation was canceled.

Test Python 3.9 on macos-latest

Test Python 3.9 on macos-latest

failed Oct 12, 2024 in 6h 0m 15s

Loading

Re-running jobs...

You can’t perform that action at this time.