slang: modify an array test
PATCH v2 1/1 slang: modify an array test
One array test attempts to create an array that is far too large to exist. Different exceptions are thrown for 32 and 64 bit machines, so we account for that when catching them.
--- meta/recipes-extended/slang/slang/array_test.patch | 20 ++++++++++++++++++++ meta/recipes-extended/slang/slang_2.3.2.bb | 1 + 2 files changed, 21 insertions(+) create mode 100644 meta/recipes-extended/slang/slang/array_test.patch
meta/recipes-extended/slang/slang/array_test.patch new file +20 -0
@@ -0,0 +1,20 @@ +slang: modify array test + +One array test tries to create an array that is far too large and anticipates an exception. +IndexError will only be thrown for 64 bit machines, so we add InvalidParmError for 32 bit ones. + +Upstream-Status: Submitted [jedsoft.org] + +Signed-off-by: Joe Slater <[email protected]> + +--- a/src/test/array.sl ++++ b/src/test/array.sl +@@ -165,7 +165,7 @@ try + { + SS = Long_Type[10000,10000,10000,10000,10000,10000]; + } +-catch IndexError; ++catch IndexError,InvalidParmError; + + private define array_map2_func () + {
meta/recipes-extended/slang/slang_2.3.2.bb +1 -0
@@ -19,6 +19,7 @@ SRC_URI = "http://www.jedsoft.org/releases/${BPN}/${BP}.tar.bz2 \ file://dont-link-to-host.patch \ file://test-add-output-in-the-format-result-testname.patch \ file://terminfo_fixes.patch \ + file://array_test.patch \ file://run-ptest \ "
Signature · 1 line
2.7.4
✗ patchtest: failure for [v2] slang: modify an array test
== Series Details ==
Series: [v2] slang: modify an array test
Revision: 1
URL : https://patchwork.openembedded.org/series/18029/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:
* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch master (currently at 666f6192aa)
If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).
---
Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe