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
c604e22a
Commit
c604e22a
authored
Jan 17, 2018
by
Jason Madden
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Folding for travis.
parent
e5b881b7
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
55 additions
and
1 deletion
+55
-1
Makefile
Makefile
+12
-1
scripts/travis.py
scripts/travis.py
+43
-0
No files found.
Makefile
View file @
c604e22a
...
...
@@ -86,28 +86,39 @@ test_prelim:
# we need a python script to do this, or possible the GNU make shell function
basictest
:
test_prelim
${PYTHON}
scripts/travis.py fold_start basictest
"Running basic tests"
cd
src/greentest
&&
GEVENT_RESOLVER
=
thread
${PYTHON}
testrunner.py
--config
known_failures.py
--quiet
${PYTHON}
scripts/travis.py fold_end basictest
alltest
:
basictest
${PYTHON}
scripts/travis.py fold_start ares
"Running c-ares tests"
cd
src/greentest
&&
GEVENT_RESOLVER
=
ares
GEVENTARES_SERVERS
=
8.8.8.8
${PYTHON}
testrunner.py
--config
known_failures.py
--ignore
tests_that_dont_use_resolver.txt
--quiet
${PYTHON}
scripts/travis.py fold_end ares
# In the past, we included all test files that had a reference to 'subprocess'' somewhere in their
# text. The monkey-patched stdlib tests were specifically included here.
# However, we now always also test on AppVeyor (Windows) which only has GEVENT_FILE=thread,
# so we can save a lot of CI time by reducing the set and excluding the stdlib tests without
# losing any coverage. See the `threadfiletest` for what command used to run.
${PYTHON}
scripts/travis.py
fold_start
thread
"Running GEVENT_FILE=thread tests"
cd
src/greentest
&&
GEVENT_FILE
=
thread
${PYTHON}
testrunner.py
--config
known_failures.py test__
*
subprocess
*
.py
--quiet
${PYTHON}
scripts/travis.py
fold_end
thread
threadfiletest
:
cd
src/greentest
&&
GEVENT_FILE
=
thread
${PYTHON}
testrunner.py
--config
known_failures.py
`
grep
-l
subprocess test_
*
.py
`
--quiet
allbackendtest
:
${PYTHON}
scripts/travis.py fold_start default
"Testing default backend"
GEVENT_CORE_CFFI_ONLY
=
make alltest
${PYTHON}
scripts/travis.py fold_end default
make cffibackendtest
cffibackendtest
:
${PYTHON}
scripts/travis.py fold_start libuv
"Testing libuv backend"
GEVENT_CORE_CFFI_ONLY
=
libuv make alltest
${PYTHON}
scripts/travis.py fold_end libuv
${PYTHON}
scripts/travis.py fold_start libev
"Testing libev CFFI backend"
GEVENT_CORE_CFFI_ONLY
=
libev make alltest
${PYTHON}
scripts/travis.py fold_end libev
leaktest
:
GEVENTSETUP_EV_VERIFY
=
3
GEVENTTEST_LEAKCHECK
=
1 make alltest
...
...
scripts/travis.py
0 → 100644
View file @
c604e22a
# -*- coding: utf-8 -*-
"""
"""
from
__future__
import
absolute_import
from
__future__
import
division
from
__future__
import
print_function
import
sys
commands
=
{}
def
command
(
func
):
commands
[
func
.
__name__
]
=
func
@
command
def
fold_start
():
name
=
sys
.
argv
[
2
]
msg
=
sys
.
argv
[
3
]
sys
.
stdout
.
write
(
'travis_fold:start:'
)
sys
.
stdout
.
write
(
name
)
sys
.
stdout
.
write
(
chr
(
0o33
))
sys
.
stdout
.
write
(
'[33;1m'
)
sys
.
stdout
.
write
(
msg
)
sys
.
stdout
.
write
(
chr
(
0o33
))
sys
.
stdout
.
write
(
'[33;0m'
)
@
command
def
fold_end
():
name
=
sys
.
argv
[
2
]
sys
.
stdout
.
write
(
"
\
n
travis_fold:end:"
)
sys
.
stdout
.
write
(
name
)
sys
.
stdout
.
write
(
"
\
r
\
n
"
)
def
main
():
cmd
=
sys
.
argv
[
1
]
commands
[
cmd
]()
if
__name__
==
'__main__'
:
main
()
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