Hi P.O.,
please forget my previous post, there was a stupid error in the test that caused the error: while
testing the single test unit the current directory was the same in which the testfiles got created,
when run under the test suite the current directory may be different hence one must always use fully
qualified file names. (A classic "pre-justice" assuming that the error had to do in this case with
employing commands which caused "complex possible causes" to be thought of that were misleading. :( )
Will fix and test and then commit.
---rony
On 10.03.2025 17:34, Rony G. Flatscher wrote:
Hi P.O.,
thanks for reporting.
I have been looking into this and it is currently a puzzle: running the tests stand-alone work,
running them with the testsuite causes these errors which appear to be awkward as long as the
reason cannot be found.
The test creates a simple Rexx file that contains "return 42" and then uses a command to compile
that Rexx program supplying a filename for the compiled version and then uses another command,
this time to compile that Rexx program but create a base64-encoded version. Then these two
compiled Rexx programs get used in r=.routine~newFile(filename) and then r~call and the result
gets fetched for tests.
It is in this step where the error occurs.
The compiled files exist at that point in time and should have content and no other statement in
the test method has opened them at that point in time.
Has anyone an idea what might be the reason for this observed behavriour, such
that one can fix this?
TIA,
---rony
P.S.: Running the entire test suite takes more than 15 minutes per run on this machine, such that
it has been taking far too much time for different variants to come by this runtime error. Will
have to stop in a short while for today.
On 10.03.2025 13:11, P. O. Jonsson wrote:
Sorry not failing builds just failing tests
Von meinem iPhone gesendet
P.O. Jonsson
Am 10.03.2025 um 09:02 schrieb P.O. Jonsson <oor...@jonases.se>:
A recent commit created failing builds on many/most platforms, here Ubuntu
Started by an SCM change
Running as SYSTEM
Building on the built-in node in workspace
/var/lib/jenkins/workspace/ooRexx-Controller-Ubuntu-test
Updating https://svn.code.sf.net/p/oorexx/code-0/test/trunk at revision '2025-03-07T02:03:11.968
+0100'
U ooRexx/API/oo/METHOD.testGroup
U ooRexx/utilities/rexxc/rexxc.testGroup
At revision 12934
[error] 20250307 02:03:42.427764
Test: TEST_REXXC_WITH_NEWROUTINE_LOADPACKAGEFROMDATA
Class: METHOD.testGroup
File: .../ooRexx/API/oo/METHOD.testGroup
Event: SYNTAX 3.1 raised unexpectedly.
Failure during initialization: File "source_program.rex_compiled" is
unreadable.
Line: 3109
*-* Compiled method "NEWFILE" with scope "Routine".
3109 *-* r=.routine~newFile(fnComp) -- create from file
*-* Compiled method "SEND" with scope "Message".
1585 *-* .message~new(self, methodName)~send
1548 *-* self~doTheTest(fName, aTestResult) -- carry out the testmethod
548 *-* test~execute(testResult, verbose)
548 *-* test~execute(testResult, verbose)
110 *-* suite~execute(testResult)
79 *-* retCode = 'worker.rex'(arguments)
[error] 20250307 02:08:50.434718
Test: TEST_REXXC_ENCODING
Class: rexxc.testGroup
File: .../ooRexx/utilities/rexxc/rexxc.testGroup
Event: SYNTAX 3.1 raised unexpectedly.
Failure during initialization: File "test_rexxc.rex_compiled" is unreadable.
Line: 166
*-* Compiled method "NEWFILE" with scope "Routine".
166 *-* r=.routine~newFile(fnComp) -- create from file
*-* Compiled method "SEND" with scope "Message".
1585 *-* .message~new(self, methodName)~send
1548 *-* self~doTheTest(fName, aTestResult) -- carry out the testmethod
548 *-* test~execute(testResult, verbose)
548 *-* test~execute(testResult, verbose)
110 *-* suite~execute(testResult)
79 *-* retCode = 'worker.rex'(arguments)
File search: 00:00:01.172921
Suite construction: 00:00:01.131249
Test execution: 00:05:29.157475
Total time: 00:05:31.462503
Build step 'Execute shell' marked build as failure
Finished: FAILURE
Please have a look if you did a commit recently
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
