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

Avaiga / taipy Public

Notifications You must be signed in to change notification settings
Fork 905
Star 12.3k

Code
Issues 123
Pull requests 14
Discussions
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security
Insights

Back to pull request #901

Feature - Reset threading lock at conftest #1209

Sign in to view logs

Sign in to view logs

Feature - Reset threading lock at conftest

Feature - Reset threading lock at conftest #1209

Summary
Jobs
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

1 error and 1 warning

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

Runner GitHub Actions 257 did not respond to a cancelation request with 00:05:00.

intermittent-tests (3.12, macos-latest, standalone, min)

intermittent-tests (3.12, macos-latest, standalone, min)

failed Mar 14, 2024 in 44m 59s

Loading

Re-running jobs...

You can’t perform that action at this time.