Build failed in Jenkins: royale-asjs_MXTests #1088

2019-08-25 Thread Apache Royale CI Server
See 


--
[...truncated 967.07 KB...]
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: CollectionEvent
[mxmlc] scanning for overrides: CollectionEventKind
[mxmlc] scanning for overrides: LocaleSorter
[mxmlc] scanning for overrides: LocaleID
[mxmlc] scanning for overrides: LocaleRegistry
[mxmlc] scanning for overrides: ResourceBundle
[mxmlc] scanning for overrides: ArrayUtil
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: DataGroup
[mxmlc] scanning for overrides: LayoutBase
[mxmlc] scanning for overrides: BasicLayout
[mxmlc] scanning for overrides: IBinaryDataInput
  

Jenkins build is back to normal : royale-asjs_jsonly #3455

2019-08-25 Thread Apache Royale CI Server
See 




Re: Discuss of release steps preparation

2019-08-25 Thread Alex Harui
Looks like there are 130 files in the "left" folder that aren't in the "right"? 
 Or I don't understand the output of whatever tool you are using.  Post a link 
to the two zips if  you want.

HTH,
-Alex

On 8/25/19, 3:08 PM, "Piotr Zarzycki"  wrote:

Content in both zips is exactly the same. I don't see now the reason to do
not move forward with that ->  
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fibb.co%2FXzDDVfddata=02%7C01%7Caharui%40adobe.com%7C7f2eea67e96348d6d71c08d729a8b4dc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63702367690243sdata=MS4vu0MzfiFlKtNlzDq8iIaWMZKX%2B8VUzoYYlARjRKU%3Dreserved=0

pon., 26 sie 2019 o 00:01 Piotr Zarzycki 
napisał(a):

> Sorry that's not my day. It looks like my folder in Total Commander wasn't
> refreshed. Both zips exists. I will compare them and provide results.
>
> On Sun, Aug 25, 2019, 11:58 PM Piotr Zarzycki 
> wrote:
>
>> Alex,
>>
>> I just checked and I was mistake. Zip which should be inside source
>> folder is not exists at all. I'm wondering what could happen that this 
zip
>> wasn't generated.
>>
>> Thanks,
>> Piotr
>>
>> On Sun, Aug 25, 2019, 11:52 PM Alex Harui 
>> wrote:
>>
>>> The output says the -src.zip did not compare.  Expand the two zip files
>>> into different folders and compare the folders.
>>>
>>> HTH,
>>> -Alex
>>>
>>> On 8/25/19, 2:45 PM, "Piotr Zarzycki" 
>>> wrote:
>>>
>>> Hi,
>>>
>>> I have spend another hours on release. Maven artifacts are deployed
>>> to the
>>> staging without the problem. I stopped this time and the very end of
>>> the
>>> process, where I need to prepare ANT artifacts. Build on my PC
>>> failed [1] -
>>> size of compared zips are different - Step 13.
>>>
>>> During whole process I had such problem when SWC time stamp had
>>> incorrect
>>> format and in the end I did end up with fail. Maybe this time is the
>>> same
>>> story.
>>> Maybe in that case this is the same. The question is - To what step
>>> should
>>> I really back ?
>>> Should I remove branch for asjs and start from 11?
>>>
>>> My command:
>>> ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.6
>>> -Droyale.swc-date="8/25/19 9:06 -0800" -Dplayerglobal.version=11.7
>>> -Dflat.donot.ask=true -Drc=1 -DskipTests=true
>>>
>>> It is really pain to me start from scratch, cause building whole
>>> framework
>>> on my PC takes ages. Satisfying comparer is difficult.
>>>
>>> [1]
>>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fs8i7rdata=02%7C01%7Caharui%40adobe.com%7C7f2eea67e96348d6d71c08d729a8b4dc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63702367690243sdata=m5WJwGDiSsf5r76cxK7Ye04vZg18nK2Eq29Mm5tIhsw%3Dreserved=0
>>>
>>> Thanks,
>>> Piotr
>>>
>>> pt., 16 sie 2019 o 18:27 Alex Harui 
>>> napisał(a):
>>>
>>> > Piotr,
>>> >
>>> > At this point, I would definitely recommend trying the three steps
>>> without
>>> > any changes to the release_steps.xml file and use an ABSOLUTE
>>> path.  That's
>>> > the only way I tested the scripts.  I did not try a relative path,
>>> and I
>>> > highly recommend not putting all of these files in a working
>>> copy.  It is
>>> > probably less work to just have RM's specify an absolute path
>>> external to
>>> > the working copy.  Using "../.." may not work consistently so do
>>> not use
>>> > those adjustments.
>>> >
>>> > Capture the logs for all 3 steps and if there is a problem post
>>> the output.
>>> >
>>> > Thanks,
>>> > -Alex
>>> >
>>> >
>>> > On 8/16/19, 2:57 AM, "Piotr Zarzycki" 
>>> wrote:
>>> >
>>> > It looks like this is again problem with RoyaleUnit[1]. Here
>>> is the
>>> > results
>>> > of comparison. I'm not sure why left folder doesn't contains
>>> files.
>>> >
>>> > [1]
>>> >
>>> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsWnHGq.pngdata=02%7C01%7Caharui%40adobe.com%7C7f2eea67e96348d6d71c08d729a8b4dc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63702367695233sdata=WhSmR1eH1iYAJpJ5FwjkntiiW9u4%2B7w9HJruaVml%2B88%3Dreserved=0
>>> >
>>> > Thanks,
>>> > Piotr
>>> >
>>> > pt., 16 sie 2019 o 11:08 Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
>>> > napisał(a):
>>> >
>>> > > Ok I was mistake. Both zips exists, but they have different
>>> sizes! So
>>> > > comparison went fine and I 

Re: Discuss of release steps preparation

2019-08-25 Thread Piotr Zarzycki
Content in both zips is exactly the same. I don't see now the reason to do
not move forward with that ->  https://ibb.co/XzDDVfd

pon., 26 sie 2019 o 00:01 Piotr Zarzycki 
napisał(a):

> Sorry that's not my day. It looks like my folder in Total Commander wasn't
> refreshed. Both zips exists. I will compare them and provide results.
>
> On Sun, Aug 25, 2019, 11:58 PM Piotr Zarzycki 
> wrote:
>
>> Alex,
>>
>> I just checked and I was mistake. Zip which should be inside source
>> folder is not exists at all. I'm wondering what could happen that this zip
>> wasn't generated.
>>
>> Thanks,
>> Piotr
>>
>> On Sun, Aug 25, 2019, 11:52 PM Alex Harui 
>> wrote:
>>
>>> The output says the -src.zip did not compare.  Expand the two zip files
>>> into different folders and compare the folders.
>>>
>>> HTH,
>>> -Alex
>>>
>>> On 8/25/19, 2:45 PM, "Piotr Zarzycki" 
>>> wrote:
>>>
>>> Hi,
>>>
>>> I have spend another hours on release. Maven artifacts are deployed
>>> to the
>>> staging without the problem. I stopped this time and the very end of
>>> the
>>> process, where I need to prepare ANT artifacts. Build on my PC
>>> failed [1] -
>>> size of compared zips are different - Step 13.
>>>
>>> During whole process I had such problem when SWC time stamp had
>>> incorrect
>>> format and in the end I did end up with fail. Maybe this time is the
>>> same
>>> story.
>>> Maybe in that case this is the same. The question is - To what step
>>> should
>>> I really back ?
>>> Should I remove branch for asjs and start from 11?
>>>
>>> My command:
>>> ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.6
>>> -Droyale.swc-date="8/25/19 9:06 -0800" -Dplayerglobal.version=11.7
>>> -Dflat.donot.ask=true -Drc=1 -DskipTests=true
>>>
>>> It is really pain to me start from scratch, cause building whole
>>> framework
>>> on my PC takes ages. Satisfying comparer is difficult.
>>>
>>> [1]
>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fs8i7rdata=02%7C01%7Caharui%40adobe.com%7C9a4cadbaa084428b55c208d729a59446%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637023663478251633sdata=6pzbbQImsdJGBM%2B5cRaSAwgyTnQyBTqgL58CFxb8dR4%3Dreserved=0
>>>
>>> Thanks,
>>> Piotr
>>>
>>> pt., 16 sie 2019 o 18:27 Alex Harui 
>>> napisał(a):
>>>
>>> > Piotr,
>>> >
>>> > At this point, I would definitely recommend trying the three steps
>>> without
>>> > any changes to the release_steps.xml file and use an ABSOLUTE
>>> path.  That's
>>> > the only way I tested the scripts.  I did not try a relative path,
>>> and I
>>> > highly recommend not putting all of these files in a working
>>> copy.  It is
>>> > probably less work to just have RM's specify an absolute path
>>> external to
>>> > the working copy.  Using "../.." may not work consistently so do
>>> not use
>>> > those adjustments.
>>> >
>>> > Capture the logs for all 3 steps and if there is a problem post
>>> the output.
>>> >
>>> > Thanks,
>>> > -Alex
>>> >
>>> >
>>> > On 8/16/19, 2:57 AM, "Piotr Zarzycki" 
>>> wrote:
>>> >
>>> > It looks like this is again problem with RoyaleUnit[1]. Here
>>> is the
>>> > results
>>> > of comparison. I'm not sure why left folder doesn't contains
>>> files.
>>> >
>>> > [1]
>>> >
>>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsWnHGq.pngdata=02%7C01%7Caharui%40adobe.com%7C9a4cadbaa084428b55c208d729a59446%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637023663478251633sdata=xJXIQ4REkQLO7aCWgIiH%2FteP3dwMEnSfpSVMfowSGgk%3Dreserved=0
>>> >
>>> > Thanks,
>>> > Piotr
>>> >
>>> > pt., 16 sie 2019 o 11:08 Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
>>> > napisał(a):
>>> >
>>> > > Ok I was mistake. Both zips exists, but they have different
>>> sizes! So
>>> > > comparison went fine and I need to understand one sources are
>>> > different...
>>> > >
>>> > > pt., 16 sie 2019 o 10:59 Piotr Zarzycki <
>>> piotrzarzyck...@gmail.com>
>>> > > napisał(a):
>>> > >
>>> > >> I have analyzed that target (compare-src-zips) and it
>>> compares zip
>>> > file
>>> > >> in following locations:
>>> > >>
>>> > >> 1) artifacts\apache-royale-0.9.6-src.zip
>>> > >> 2) /sources/srczip/apache-royale-0.9.6-src.zip
>>> > >>
>>> > >> I have changed in that target all places where
>>> ${artifactfolder} to
>>> > >> ../../${artifactfolder} and launch that target. It looks
>>> like zip
>>> > file
>>> > >> wasn't created at all in location:
>>> > >> /sources/srczip/apache-royale-0.9.6-src.zip.
>>> > >>
>>> > >> I will try to figure out what has happened. Btw. I didn't
>>> commit my
>>> > >> changes with ../../ - those are local.
>>>

Re: Discuss of release steps preparation

2019-08-25 Thread Piotr Zarzycki
Sorry that's not my day. It looks like my folder in Total Commander wasn't
refreshed. Both zips exists. I will compare them and provide results.

On Sun, Aug 25, 2019, 11:58 PM Piotr Zarzycki 
wrote:

> Alex,
>
> I just checked and I was mistake. Zip which should be inside source folder
> is not exists at all. I'm wondering what could happen that this zip wasn't
> generated.
>
> Thanks,
> Piotr
>
> On Sun, Aug 25, 2019, 11:52 PM Alex Harui 
> wrote:
>
>> The output says the -src.zip did not compare.  Expand the two zip files
>> into different folders and compare the folders.
>>
>> HTH,
>> -Alex
>>
>> On 8/25/19, 2:45 PM, "Piotr Zarzycki"  wrote:
>>
>> Hi,
>>
>> I have spend another hours on release. Maven artifacts are deployed
>> to the
>> staging without the problem. I stopped this time and the very end of
>> the
>> process, where I need to prepare ANT artifacts. Build on my PC failed
>> [1] -
>> size of compared zips are different - Step 13.
>>
>> During whole process I had such problem when SWC time stamp had
>> incorrect
>> format and in the end I did end up with fail. Maybe this time is the
>> same
>> story.
>> Maybe in that case this is the same. The question is - To what step
>> should
>> I really back ?
>> Should I remove branch for asjs and start from 11?
>>
>> My command:
>> ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.6
>> -Droyale.swc-date="8/25/19 9:06 -0800" -Dplayerglobal.version=11.7
>> -Dflat.donot.ask=true -Drc=1 -DskipTests=true
>>
>> It is really pain to me start from scratch, cause building whole
>> framework
>> on my PC takes ages. Satisfying comparer is difficult.
>>
>> [1]
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fs8i7rdata=02%7C01%7Caharui%40adobe.com%7C9a4cadbaa084428b55c208d729a59446%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637023663478251633sdata=6pzbbQImsdJGBM%2B5cRaSAwgyTnQyBTqgL58CFxb8dR4%3Dreserved=0
>>
>> Thanks,
>> Piotr
>>
>> pt., 16 sie 2019 o 18:27 Alex Harui 
>> napisał(a):
>>
>> > Piotr,
>> >
>> > At this point, I would definitely recommend trying the three steps
>> without
>> > any changes to the release_steps.xml file and use an ABSOLUTE
>> path.  That's
>> > the only way I tested the scripts.  I did not try a relative path,
>> and I
>> > highly recommend not putting all of these files in a working copy.
>> It is
>> > probably less work to just have RM's specify an absolute path
>> external to
>> > the working copy.  Using "../.." may not work consistently so do
>> not use
>> > those adjustments.
>> >
>> > Capture the logs for all 3 steps and if there is a problem post the
>> output.
>> >
>> > Thanks,
>> > -Alex
>> >
>> >
>> > On 8/16/19, 2:57 AM, "Piotr Zarzycki" 
>> wrote:
>> >
>> > It looks like this is again problem with RoyaleUnit[1]. Here is
>> the
>> > results
>> > of comparison. I'm not sure why left folder doesn't contains
>> files.
>> >
>> > [1]
>> >
>> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsWnHGq.pngdata=02%7C01%7Caharui%40adobe.com%7C9a4cadbaa084428b55c208d729a59446%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637023663478251633sdata=xJXIQ4REkQLO7aCWgIiH%2FteP3dwMEnSfpSVMfowSGgk%3Dreserved=0
>> >
>> > Thanks,
>> > Piotr
>> >
>> > pt., 16 sie 2019 o 11:08 Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> > napisał(a):
>> >
>> > > Ok I was mistake. Both zips exists, but they have different
>> sizes! So
>> > > comparison went fine and I need to understand one sources are
>> > different...
>> > >
>> > > pt., 16 sie 2019 o 10:59 Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> > > napisał(a):
>> > >
>> > >> I have analyzed that target (compare-src-zips) and it
>> compares zip
>> > file
>> > >> in following locations:
>> > >>
>> > >> 1) artifacts\apache-royale-0.9.6-src.zip
>> > >> 2) /sources/srczip/apache-royale-0.9.6-src.zip
>> > >>
>> > >> I have changed in that target all places where
>> ${artifactfolder} to
>> > >> ../../${artifactfolder} and launch that target. It looks
>> like zip
>> > file
>> > >> wasn't created at all in location:
>> > >> /sources/srczip/apache-royale-0.9.6-src.zip.
>> > >>
>> > >> I will try to figure out what has happened. Btw. I didn't
>> commit my
>> > >> changes with ../../ - those are local.
>> > >>
>> > >> Thanks,
>> > >> Piotr
>> > >>
>> > >> pt., 16 sie 2019 o 09:29 Piotr Zarzycki <
>> piotrzarzyck...@gmail.com>
>> > >> napisał(a):
>> > >>
>> > >>> Unfortunately I don't know what is happening but signing
>> trough
>> > script
>> > >>> hang for 

Re: Discuss of release steps preparation

2019-08-25 Thread Piotr Zarzycki
Alex,

I just checked and I was mistake. Zip which should be inside source folder
is not exists at all. I'm wondering what could happen that this zip wasn't
generated.

Thanks,
Piotr

On Sun, Aug 25, 2019, 11:52 PM Alex Harui  wrote:

> The output says the -src.zip did not compare.  Expand the two zip files
> into different folders and compare the folders.
>
> HTH,
> -Alex
>
> On 8/25/19, 2:45 PM, "Piotr Zarzycki"  wrote:
>
> Hi,
>
> I have spend another hours on release. Maven artifacts are deployed to
> the
> staging without the problem. I stopped this time and the very end of
> the
> process, where I need to prepare ANT artifacts. Build on my PC failed
> [1] -
> size of compared zips are different - Step 13.
>
> During whole process I had such problem when SWC time stamp had
> incorrect
> format and in the end I did end up with fail. Maybe this time is the
> same
> story.
> Maybe in that case this is the same. The question is - To what step
> should
> I really back ?
> Should I remove branch for asjs and start from 11?
>
> My command:
> ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.6
> -Droyale.swc-date="8/25/19 9:06 -0800" -Dplayerglobal.version=11.7
> -Dflat.donot.ask=true -Drc=1 -DskipTests=true
>
> It is really pain to me start from scratch, cause building whole
> framework
> on my PC takes ages. Satisfying comparer is difficult.
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fs8i7rdata=02%7C01%7Caharui%40adobe.com%7C9a4cadbaa084428b55c208d729a59446%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637023663478251633sdata=6pzbbQImsdJGBM%2B5cRaSAwgyTnQyBTqgL58CFxb8dR4%3Dreserved=0
>
> Thanks,
> Piotr
>
> pt., 16 sie 2019 o 18:27 Alex Harui 
> napisał(a):
>
> > Piotr,
> >
> > At this point, I would definitely recommend trying the three steps
> without
> > any changes to the release_steps.xml file and use an ABSOLUTE path.
> That's
> > the only way I tested the scripts.  I did not try a relative path,
> and I
> > highly recommend not putting all of these files in a working copy.
> It is
> > probably less work to just have RM's specify an absolute path
> external to
> > the working copy.  Using "../.." may not work consistently so do not
> use
> > those adjustments.
> >
> > Capture the logs for all 3 steps and if there is a problem post the
> output.
> >
> > Thanks,
> > -Alex
> >
> >
> > On 8/16/19, 2:57 AM, "Piotr Zarzycki" 
> wrote:
> >
> > It looks like this is again problem with RoyaleUnit[1]. Here is
> the
> > results
> > of comparison. I'm not sure why left folder doesn't contains
> files.
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsWnHGq.pngdata=02%7C01%7Caharui%40adobe.com%7C9a4cadbaa084428b55c208d729a59446%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637023663478251633sdata=xJXIQ4REkQLO7aCWgIiH%2FteP3dwMEnSfpSVMfowSGgk%3Dreserved=0
> >
> > Thanks,
> > Piotr
> >
> > pt., 16 sie 2019 o 11:08 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > napisał(a):
> >
> > > Ok I was mistake. Both zips exists, but they have different
> sizes! So
> > > comparison went fine and I need to understand one sources are
> > different...
> > >
> > > pt., 16 sie 2019 o 10:59 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > > napisał(a):
> > >
> > >> I have analyzed that target (compare-src-zips) and it
> compares zip
> > file
> > >> in following locations:
> > >>
> > >> 1) artifacts\apache-royale-0.9.6-src.zip
> > >> 2) /sources/srczip/apache-royale-0.9.6-src.zip
> > >>
> > >> I have changed in that target all places where
> ${artifactfolder} to
> > >> ../../${artifactfolder} and launch that target. It looks like
> zip
> > file
> > >> wasn't created at all in location:
> > >> /sources/srczip/apache-royale-0.9.6-src.zip.
> > >>
> > >> I will try to figure out what has happened. Btw. I didn't
> commit my
> > >> changes with ../../ - those are local.
> > >>
> > >> Thanks,
> > >> Piotr
> > >>
> > >> pt., 16 sie 2019 o 09:29 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > >> napisał(a):
> > >>
> > >>> Unfortunately I don't know what is happening but signing
> trough
> > script
> > >>> hang for me. Stopped working. :(
> > >>>
> > >>>
> > >>> ant -f releasesteps.xml Release_Step_003_Sign
> > -Drelease.version=0.9.6
> > >>> Buildfile:
> d:\Work\royale-sources\royale-compiler\releasesteps.xml
> > >>>
> > >>> get-artifact-folder:
> > >>> [input] Enter the temporary folder to 

Re: Discuss of release steps preparation

2019-08-25 Thread Alex Harui
The output says the -src.zip did not compare.  Expand the two zip files into 
different folders and compare the folders.

HTH,
-Alex

On 8/25/19, 2:45 PM, "Piotr Zarzycki"  wrote:

Hi,

I have spend another hours on release. Maven artifacts are deployed to the
staging without the problem. I stopped this time and the very end of the
process, where I need to prepare ANT artifacts. Build on my PC failed [1] -
size of compared zips are different - Step 13.

During whole process I had such problem when SWC time stamp had incorrect
format and in the end I did end up with fail. Maybe this time is the same
story.
Maybe in that case this is the same. The question is - To what step should
I really back ?
Should I remove branch for asjs and start from 11?

My command:
ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.6
-Droyale.swc-date="8/25/19 9:06 -0800" -Dplayerglobal.version=11.7
-Dflat.donot.ask=true -Drc=1 -DskipTests=true

It is really pain to me start from scratch, cause building whole framework
on my PC takes ages. Satisfying comparer is difficult.

[1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fs8i7rdata=02%7C01%7Caharui%40adobe.com%7C9a4cadbaa084428b55c208d729a59446%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637023663478251633sdata=6pzbbQImsdJGBM%2B5cRaSAwgyTnQyBTqgL58CFxb8dR4%3Dreserved=0

Thanks,
Piotr

pt., 16 sie 2019 o 18:27 Alex Harui  napisał(a):

> Piotr,
>
> At this point, I would definitely recommend trying the three steps without
> any changes to the release_steps.xml file and use an ABSOLUTE path.  
That's
> the only way I tested the scripts.  I did not try a relative path, and I
> highly recommend not putting all of these files in a working copy.  It is
> probably less work to just have RM's specify an absolute path external to
> the working copy.  Using "../.." may not work consistently so do not use
> those adjustments.
>
> Capture the logs for all 3 steps and if there is a problem post the 
output.
>
> Thanks,
> -Alex
>
>
> On 8/16/19, 2:57 AM, "Piotr Zarzycki"  wrote:
>
> It looks like this is again problem with RoyaleUnit[1]. Here is the
> results
> of comparison. I'm not sure why left folder doesn't contains files.
>
> [1]
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsWnHGq.pngdata=02%7C01%7Caharui%40adobe.com%7C9a4cadbaa084428b55c208d729a59446%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637023663478251633sdata=xJXIQ4REkQLO7aCWgIiH%2FteP3dwMEnSfpSVMfowSGgk%3Dreserved=0
>
> Thanks,
> Piotr
>
> pt., 16 sie 2019 o 11:08 Piotr Zarzycki 
> napisał(a):
>
> > Ok I was mistake. Both zips exists, but they have different sizes! 
So
> > comparison went fine and I need to understand one sources are
> different...
> >
> > pt., 16 sie 2019 o 10:59 Piotr Zarzycki 
> > napisał(a):
> >
> >> I have analyzed that target (compare-src-zips) and it compares zip
> file
> >> in following locations:
> >>
> >> 1) artifacts\apache-royale-0.9.6-src.zip
> >> 2) /sources/srczip/apache-royale-0.9.6-src.zip
> >>
> >> I have changed in that target all places where ${artifactfolder} to
> >> ../../${artifactfolder} and launch that target. It looks like zip
> file
> >> wasn't created at all in location:
> >> /sources/srczip/apache-royale-0.9.6-src.zip.
> >>
> >> I will try to figure out what has happened. Btw. I didn't commit my
> >> changes with ../../ - those are local.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pt., 16 sie 2019 o 09:29 Piotr Zarzycki 
> >> napisał(a):
> >>
> >>> Unfortunately I don't know what is happening but signing trough
> script
> >>> hang for me. Stopped working. :(
> >>>
> >>>
> >>> ant -f releasesteps.xml Release_Step_003_Sign
> -Drelease.version=0.9.6
> >>> Buildfile: d:\Work\royale-sources\royale-compiler\releasesteps.xml
> >>>
> >>> get-artifact-folder:
> >>> [input] Enter the temporary folder to store the downloaded
> artifacts:
> >>> royale096
> >>>
> >>> Release_Step_003_Sign:
> >>>
> >>> sign-file:
> >>>
> >>>
> >>>
> >>> pt., 16 sie 2019 o 09:21 Piotr Zarzycki  >
> >>> napisał(a):
> >>>
>  With "../../" or without ? I just run script with
> -DskiptTests="true"
>  and it passes, but failed on "compare-src-zips" - It looks like
> it is also
>  problem with paths. :(
> 
>  

Re: Discuss of release steps preparation

2019-08-25 Thread Piotr Zarzycki
Hi,

I have spend another hours on release. Maven artifacts are deployed to the
staging without the problem. I stopped this time and the very end of the
process, where I need to prepare ANT artifacts. Build on my PC failed [1] -
size of compared zips are different - Step 13.

During whole process I had such problem when SWC time stamp had incorrect
format and in the end I did end up with fail. Maybe this time is the same
story.
Maybe in that case this is the same. The question is - To what step should
I really back ?
Should I remove branch for asjs and start from 11?

My command:
ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.6
-Droyale.swc-date="8/25/19 9:06 -0800" -Dplayerglobal.version=11.7
-Dflat.donot.ask=true -Drc=1 -DskipTests=true

It is really pain to me start from scratch, cause building whole framework
on my PC takes ages. Satisfying comparer is difficult.

[1] https://paste.apache.org/s8i7r

Thanks,
Piotr

pt., 16 sie 2019 o 18:27 Alex Harui  napisał(a):

> Piotr,
>
> At this point, I would definitely recommend trying the three steps without
> any changes to the release_steps.xml file and use an ABSOLUTE path.  That's
> the only way I tested the scripts.  I did not try a relative path, and I
> highly recommend not putting all of these files in a working copy.  It is
> probably less work to just have RM's specify an absolute path external to
> the working copy.  Using "../.." may not work consistently so do not use
> those adjustments.
>
> Capture the logs for all 3 steps and if there is a problem post the output.
>
> Thanks,
> -Alex
>
>
> On 8/16/19, 2:57 AM, "Piotr Zarzycki"  wrote:
>
> It looks like this is again problem with RoyaleUnit[1]. Here is the
> results
> of comparison. I'm not sure why left folder doesn't contains files.
>
> [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpasteboard.co%2FIsWnHGq.pngdata=02%7C01%7Caharui%40adobe.com%7Cdd67a5a447364dbbe21908d7223029d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015462571597421sdata=bvzbqWWuRT8CPIsl03qxIO8OF9n3btvCEVdfoN%2FL83c%3Dreserved=0
>
> Thanks,
> Piotr
>
> pt., 16 sie 2019 o 11:08 Piotr Zarzycki 
> napisał(a):
>
> > Ok I was mistake. Both zips exists, but they have different sizes! So
> > comparison went fine and I need to understand one sources are
> different...
> >
> > pt., 16 sie 2019 o 10:59 Piotr Zarzycki 
> > napisał(a):
> >
> >> I have analyzed that target (compare-src-zips) and it compares zip
> file
> >> in following locations:
> >>
> >> 1) artifacts\apache-royale-0.9.6-src.zip
> >> 2) /sources/srczip/apache-royale-0.9.6-src.zip
> >>
> >> I have changed in that target all places where ${artifactfolder} to
> >> ../../${artifactfolder} and launch that target. It looks like zip
> file
> >> wasn't created at all in location:
> >> /sources/srczip/apache-royale-0.9.6-src.zip.
> >>
> >> I will try to figure out what has happened. Btw. I didn't commit my
> >> changes with ../../ - those are local.
> >>
> >> Thanks,
> >> Piotr
> >>
> >> pt., 16 sie 2019 o 09:29 Piotr Zarzycki 
> >> napisał(a):
> >>
> >>> Unfortunately I don't know what is happening but signing trough
> script
> >>> hang for me. Stopped working. :(
> >>>
> >>>
> >>> ant -f releasesteps.xml Release_Step_003_Sign
> -Drelease.version=0.9.6
> >>> Buildfile: d:\Work\royale-sources\royale-compiler\releasesteps.xml
> >>>
> >>> get-artifact-folder:
> >>> [input] Enter the temporary folder to store the downloaded
> artifacts:
> >>> royale096
> >>>
> >>> Release_Step_003_Sign:
> >>>
> >>> sign-file:
> >>>
> >>>
> >>>
> >>> pt., 16 sie 2019 o 09:21 Piotr Zarzycki  >
> >>> napisał(a):
> >>>
>  With "../../" or without ? I just run script with
> -DskiptTests="true"
>  and it passes, but failed on "compare-src-zips" - It looks like
> it is also
>  problem with paths. :(
> 
>  pt., 16 sie 2019 o 09:15 Alex Harui 
>  napisał(a):
> 
> > I would also need to see the output of the other two steps
> > (Release_Step_003 and Release_Step_003_Sign)
> >
> > Thanks,
> > -Alex
> >
> > On 8/15/19, 11:14 PM, "Piotr Zarzycki" <
> piotrzarzyck...@gmail.com>
> > wrote:
> >
> > This console output is here [1], but it is version where
> script
> > failing,
> > cause there wasn't "../../". Let me know if it's enough
> actually.
> >
> > [1]
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fzvxoidata=02%7C01%7Caharui%40adobe.com%7Cdd67a5a447364dbbe21908d7223029d2%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637015462571597421sdata=cpG%2BXauXqyeesomOmZD6pH%2FVpcwzdDwzlRW9PzXfXjQ%3Dreserved=0
> >
> >  

Release Step 013 Succeeded

2019-08-25 Thread Apache Royale CI Server
>From the royale-asjs repo
1. Run ant -f releasesteps.xml Release_Step_013 -Drelease.version=0.9.6 
-Droyale.swc-date="8/25/19 9:06 -0800" -Dplayerglobal.version=11.7 
-Dflat.donot.ask=true -Drc=1
This will download the artifacts then unzip and compile the source artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_013_Sign 
-Drelease.version=0.9.6
This will PGP sign the source and convenience binary packages
4. Then run ant -f releasesteps.xml Release_Step_013_Upload 
-Drelease.version=0.9.6 -Drc=1
This will upload the signed artifacts to dist.apache.org.

Release Step 012 Succeeded

2019-08-25 Thread Apache Royale CI Server
Folder 0.9.6 already exists.  Continue to next step