Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
erp5
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
Łukasz Nowak
erp5
Commits
432dde35
Commit
432dde35
authored
Oct 25, 2012
by
Sebastien Robin
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
erp5testnode: until slapos.core is updated, handle buggy error codes
parent
90d91409
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
1 deletion
+6
-1
erp5/util/testnode/testnode.py
erp5/util/testnode/testnode.py
+6
-1
No files found.
erp5/util/testnode/testnode.py
View file @
432dde35
...
@@ -248,7 +248,12 @@ branch = %(branch)s
...
@@ -248,7 +248,12 @@ branch = %(branch)s
status_dict
=
slapos_method
(
config
,
status_dict
=
slapos_method
(
config
,
environment
=
config
[
'environment'
],
environment
=
config
[
'environment'
],
)
)
if
status_dict
[
'status_code'
]
not
in
(
0
,
2
):
acceptable_status_code_list
=
[
0
,
2
]
# 1 must not be below, but we need it until slapos.core of
# softwares built by testnode are at least version 0.32.3
if
method_name
==
"runComputerPartition"
:
acceptable_status_code_list
.
append
(
1
)
if
status_dict
[
'status_code'
]
not
in
acceptable_status_code_list
:
node_test_suite
.
retry
=
True
node_test_suite
.
retry
=
True
node_test_suite
.
retry_software_count
+=
1
node_test_suite
.
retry_software_count
+=
1
raise
SubprocessError
(
status_dict
)
raise
SubprocessError
(
status_dict
)
...
...
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