-
Notifications
You must be signed in to change notification settings - Fork 683
Fix invalid assertion condition in jump opcode handlers #217
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
Conversation
09626e3
to
d59b17a
Compare
d59b17a
to
5f5b771
Compare
@@ -14,7 +14,7 @@ | |||
# See the License for the specific language governing permissions and | |||
# limitations under the License. | |||
|
|||
TIMEOUT=${TIMEOUT:=30} | |||
TIMEOUT=${TIMEOUT:=1} |
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.
Wouldn't it be too small timeout, maybe 3
or 5
for low performance targets?
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.
It can be too small, but 3
or 5
, actually, also can be too small. The scheme of infinite loops testing seems to be dependent on some random conditions, so it is better to revise it.
52a183f
to
efb1a12
Compare
Regression test is not added in the pull request, as it is |
Good to me |
lgtm |
|
efb1a12
to
5d84b17
Compare
Related issue: #120 JerryScript-DCO-1.0-Signed-off-by: Ruben Ayrapetyan r.ayrapetyan@samsung.com
5d84b17
to
89a7449
Compare
Related issue: #120