Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gevent
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
gevent
Commits
e4f2f8a9
Commit
e4f2f8a9
authored
Jan 28, 2010
by
Denis Bilenko
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
testrunner: limit the output stored in the db to 100kb
parent
18c93893
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
1 deletion
+6
-1
greentest/testrunner.py
greentest/testrunner.py
+6
-1
No files found.
greentest/testrunner.py
View file @
e4f2f8a9
...
...
@@ -35,9 +35,12 @@ one will be selected if not provided.
# Known issues:
# - screws up warnings location, causing them to appear as originated from testrunner.py
# the number of seconds each test script is allowed to run
DEFAULT_TIMEOUT
=
20
# the number of bytes of output that is recorded; the rest is thrown away
OUTPUT_LIMIT
=
100
*
1024
import
sys
import
os
import
glob
...
...
@@ -281,6 +284,8 @@ def spawn_subprocesses(options, args):
row_id
=
store_record
(
options
.
db
,
'test'
,
params
)
params
[
'id'
]
=
row_id
retcode
,
output
=
run_subprocess
(
arg
,
options
)
if
len
(
output
)
>
OUTPUT_LIMIT
:
output
=
output
[:
OUTPUT_LIMIT
]
+
'<AbridgedOutputWarning>'
if
retcode
:
sys
.
stdout
.
write
(
output
)
print
'%s failed with code %s'
%
(
arg
,
retcode
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment