-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Add broken tags to FW's that haven't started/stopped correctly in last 3 full runs + script for detecting failing frameworks #8255
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prologue is fixed in #8254
@@ -18,7 +18,8 @@ | |||
"database_os": "Linux", | |||
"display_name": "Prologue", | |||
"notes": "", | |||
"versus": "httpbeast" | |||
"versus": "httpbeast", | |||
"tags": ["broken"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in #8254
Please don't close frameworks, without inform their developers. |
The script is a very good start, like a new useful helper. Please add another method to show also the URL to see the error. |
These are some good ideas. Let's iterate on that when we have time. |
…t 3 full runs + script for detecting failing frameworks (TechEmpower#8255) * Web scraper for detecting failing frameworks * Mark tests that have issues starting as broken * Add broken tag to frameworks that fail all tests * remove prologue broken tag * Cherrypy fix attempt
Python web scraper to detect any frameworks that have failed the past 3 completed runs with the same error
USAGE:
python tfb-fail-detector.py