Thanks alistair.
Yes I saw and I’m going over pr to flush the pipe. 

Stef

> On 28 Jan 2019, at 19:33, Alistair Grant <[email protected]> wrote:
> 
> Hi Stef,
> 
> The "unbound variable" error has been fixed in
> https://github.com/pharo-project/pharo/pull/2368 (at least no one has
> complained in the last 8 hours :-)).
> 
> Cheers,
> Alistair
> 
> On Sun, 27 Jan 2019 at 20:35, ducasse <[email protected]> wrote:
>> 
>> Hi
>> 
>> There are several problems with the build:
>> 
>> First
>> 
>> 
>> [32] load : Refactoring2-Transformations-Tests-tonel.1
>> 
>> 
>> [32] postload : baseline [BaselineOfIDE] >> postload:package:
>> 
>> 
>> [32] load : Deprecated70-tonel.1
>> 
>> 
>> [32] postload : baseline [BaselineOfPharo] >> postload:package:
>> 
>> 
>> [32] + 
>> /builds/workspace/uest_and_branch_Pipeline_PR-2362/32/bootstrap-cache/vmtarget/pharo
>>  --headless Pharo7.0-PR-32bit-67f8280.image --no-default-preferences eval 
>> --save 'FFIMethodRegistry resetAll. PharoSourcesCondenser 
>> condenseNewSources. Smalltalk garbageCollect'
>> 
>> 
>> [32] pthread_setschedparam failed: Operation not permitted
>> 
>> 
>> [32] This VM uses a separate heartbeat thread to update its internal clock
>> 
>> 
>> [32] and handle events.  For best operation, this thread should run at a
>> 
>> 
>> second
>> 
>> 
>> [32] + . 
>> /builds/workspace/uest_and_branch_Pipeline_PR-2362/32/bootstrap/scripts/envversion.sh
>> 
>> 
>> [32] + set_version_variables
>> 
>> 
>> [32] 
>> /builds/workspace/uest_and_branch_Pipeline_PR-2362/32/bootstrap/scripts/envversion.sh:
>>  line 89: BOOTSTRAP_REPOSITORY: unbound variable
>> 
>> 
>> [Pipeline] [32] }
>> 
>> 
>> [Pipeline] [32] // dir
>> 
>> 
>> [Pipeline] [32] }
>> 
>> 
>> [Pipeline] [32] // stage
>> 
>> 
>> [Pipeline] [32] archiveArtifacts
>> 
>> 
>> [32] Archiving artifacts
>> 
>> 
>> [32] Recording fingerprints
>> 
>> 
>> [Pipeline] [32] cleanWs
>> 
>> 
>> [32] [WS-CLEANUP] Deleting project workspace...
>> 
>> 
>> [32] [WS-CLEANUP] Deferred wipeout is used...
>> 
>> 
>> [32] [WS-CLEANUP] done
>> 
>> 
>> [Pipeline] [32] }
>> 
>> 
> 



Reply via email to