Ok, I thought there was no interest.
Do I understand it correctly that the machine can stand here, in Germany, and
be logged on from remote by the Jenkins slave?
We can do the test with one of the available machines but I would purchase a
dedicated one, not the hottest MacPro but there are plenty of second hand Pros
or Minis that can take on the latest OS.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
> Am 28.02.2018 um 19:53 schrieb René Jansen <rvjan...@xs4all.nl>:
>
> Hi P.O.,
>
> overlooked your offer but it would be mighty handy if we could add another
> mac into the mix. The current one is mine but it runs unsupervised a few
> thousand kilometers from where I am. I must look into the Jenkins setup and
> will get back with instructions on how to add your Mac - be assured your
> offer is most welcome! It is just that I did not look into Jenkins for months
> and must re-acquaint myself a bit with it.
>
> best regards,
>
> René.
>
>> On 28 Feb 2018, at 06:38, oor...@jonases.se <mailto:oor...@jonases.se> wrote:
>>
>> Hello Erich, yes when I looked at it I saw there was an issue with
>> CamelFont, I had named the directory ooTest. When I changed to ootest
>> everything was fine.
>>
>> When I compare I can see that your machine have an older Kernel, I have (as
>> reported by the test)
>>
>> Darwin Darwin Kernel Version 16.7.0
>>
>> see also inline below, hope it helps?
>>
>> I reiterate my offer to sponsor another MAC for testing purposes
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se <mailto:oor...@jonases.se>
>> Von mein MacBookPro gesendet
>>
>>
>>
>>> Am 28.02.2018 um 09:50 schrieb Erich Steinböck <erich.steinbo...@gmail.com
>>> <mailto:erich.steinbo...@gmail.com>>:
>>>
>>> Hi P.O.
>>> as you can see this tests whether `pwd`and `directory()` return the same
>>> string.
>>> In your case `directory()` reports `/Users/po/ooTest`, but `pwd` returns
>>> the slightly different string `/Users/po/ootest`
>>>
>>> This is surprising, as we have a DARWIN machine (a Jenkins slave) building
>>> and testing successfully
>>> Interpreter: REXX-ooRexx_5.0.0(MT)_64-bit 6.05 27 Feb 2018
>>> OS Name: DARWIN
>>> SysVersion: Darwin Darwin Kernel Version 15.6.0: Sun Jun 4
>>> 21:43:07 PDT 2017; root:xnu-3248.70.3~1/RELEASE_X86_64.15.6.0
>>> Tests ran: 22318
>>> Assertions: 374693
>>> Failures: 0
>>> Errors: 0
>>>
>>> What's the correct directory name?
>>
>>
>> /Users/po/ooTest (as reported by the „information tab in the Finder, the
>> file browser on Mac)
>>
>>> Are you running on a case-insensitive file system?
>>
>> I run a standard installation of macOS Sierra (not Sierra High, the latest
>> version)
>>
>> Hardware-Übersicht:
>>
>> Modellname: MacBook Pro
>> Modell-Identifizierung: MacBookPro12,1
>> Prozessortyp: Intel Core i5
>> Prozessorgeschwindigkeit: 2,7 GHz
>> Anzahl der Prozessoren: 1
>> Gesamtanzahl der Kerne: 2
>> L2-Cache (pro Kern): 256 KB
>> L3-Cache: 3 MB
>> Speicher: 16 GB
>> Boot-ROM-Version: MBP121.0171.B00
>> SMC-Version (System): 2.28f7
>>
>> Überblick über die Systemsoftware:
>>
>> Systemversion: macOS 10.12.6 (16G1212)
>> Kernel-Version: Darwin 16.7.0
>> Startvolume: Macintosh HD
>> Startmodus: Normal
>> Gerätename: P.O.s MacBook Pro
>> Benutzername: P.O. Jonsson (po)
>> Sicherer virtueller Speicher: Aktiviert
>> Systemintegritätsschutz: Aktiviert
>> Zeit seit dem Start: 2 Tage 13:26
>>
>>
>>> Do both of these work: `chdir /Users/po/ooTest`and `chdir /Users/po/ootest`
>>> ?
>>
>> I do not have a chdir on the Mac but cd may do? This is a bit weird though.
>> Assuming the directory is named ooTest in camelFont:
>>
>> POs-MacBook-Pro:~ po$ cd /Users/po/ootest
>> POs-MacBook-Pro:ootest po$ ls
>>
>> As you can see the command line reports ootest HOWEVER on top of the
>> Terminal it reports (correctly) ooTest
>>
>> POs-MacBook-Pro:ootest po$ cd $home
>> POs-MacBook-Pro:~ po$ cd /Users/po/ooTest
>> POs-MacBook-Pro:ooTest po$
>>
>> Here it reports correctly ooTest in both places
>>
>> When I change the name to ootest the test runs through without error.
>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>>> http://sdm.link/slashdot_______________________________________________
>>> <http://sdm.link/slashdot_______________________________________________>
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net
>>> <mailto:Oorexx-devel@lists.sourceforge.net>
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org <http://slashdot.org/>!
>> http://sdm.link/slashdot_______________________________________________
>> <http://sdm.link/slashdot_______________________________________________>
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> <mailto:Oorexx-devel@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org!
> http://sdm.link/slashdot_______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
