You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2015/03/24 15:58:21 UTC
Linux CheckinTests (was Re: [VOTE] Apache Flex SDK 4.14.1 RC1)
Tom,
This is definitely that important, but BasicTests doesn’t do bitmap
compares so it shouldn’t be a matter of generating correct pictures if I
understand you correctly. What kind of failure is being reported?
-Alex
On 3/24/15, 3:08 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>+1 (binding)
>
>I can build the SDK, and use if from the (Linux) command line to build
>our core web app.
>MD5 and sig OK, and the ApproveSDK ant task runs OK (up to the
>mustellaresultsparser, which never seems to generate correct pictures on
>this Linux box, even from the checkin tests).
>
>The gpg commands were:
>gpg --import KEYS
>gpg --verify /tmp/apache-flex-sdk-4.14.1-src.tar.gz.asc
>
>But I know I already had a working gpg install (minus the imported keys,
>which is a one time command), so guess that was Mihai's issue.
>
>Tom
>
>On 23/03/15 09:46, Erik de Bruin wrote:
>> Hi,
>>
>> This is a Apache Flex 4.14.1 release candidate 1. For details on this
>> release see the RELEASE_NOTES and the README.
>>
>>
>> The release candidate can be found here;
>>
>> https://dist.apache.org/repos/dist/dev/flex/sdk/4.14.1/rc1/
>>
>>
>> The binary distributions as a convenience for the respective
>> platforms, available here:
>>
>> https://dist.apache.org/repos/dist/dev/flex/sdk/4.14.1/rc1/binaries
>>
>>
>> The most convenient way to use the binary package is to install it via
>> the Installer. You can get the Installer here:
>>
>> http://flex.apache.org/installer.html
>>
>> Run the Installer, right click anywhere, select "Show Dev Builds" and
>> choose "Apache Flex SDK 4.14.1 RC1".
>>
>>
>> Before voting please review the section, "What are the ASF
>> requirements on approving a release?", at:
>>
>> http://www.apache.org/dev/release.html#approving-a-release
>>
>> At a minimum you would be expected to check that:
>> - MD5 and signed packages are correct
>> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
>> - That you can compile from source package
>> - That the SDK can be used in your IDE of choice
>> - That the SDK can be used to make a mobile, desktop and browser
>>application
>>
>> When testing please check the md5 and asc files and make sure that the
>> source can be compiled.
>>
>>
>> Please vote to approve this release:
>>
>> +1 Approve the release (PMC members: please add " (binding)" to your
>>vote)
>> -1 Veto the release (please provide specific comments to why)
>>
>> This vote will be open for at least 72 hrs.
>>
>> The vote passes if there is:
>> - At least 3 +1 votes from the PMC
>> - More positive votes than negative votes
>>
>> If you find an issue with the release that's a "show stopper" please
>> don't hold off voting -1. If someone votes -1 please continue testing
>> we want to try and catch as many issues as we can and cut down on the
>> number of release candidates. Remember existing voters can change
>> their vote during the voting process.
>>
>> When voting please indicate what OS, IDE, Flash Player version and AIR
>> version you tested the SDK with.
>>
>> Please put all discussion about this release in the DISCUSSION thread
>> not this VOTE thread.
>>
>>
>> For your convenience, I have added an Ant script to the RC folder.
>> This ant script automates the checks a voter should perform on the RC.
>> It will:
>>
>> - download the default source package for your OS (use
>> -Dpackage.suffix to override)
>> - run md5 and gpg checks (this assumes you have gpg installed in your
>>path)
>> - uncompress the source package
>> - install and run rat
>> - display the rat report and ask you to verify
>> - display the rat report without the AL files and ask you to verify
>> the non-AL files
>> - display the README and ask you to verify
>> - display the RELEASE_NOTES and ask you to verify
>> - display the NOTICE and ask you to verify
>> - display the LICENSE and ask you to verify
>> - run the build and any tests run by the build.
>>
>> You should be able to go away for a while during the build. When it is
>> finished, it will display information to be copied into the vote
>> thread. You are not required to use this script, and more testing of
>> the packages and build results are always encouraged.
>>
>> To use this script (assuming you have Ant installed), it should be as
>>simple as:
>> - Create an empty folder
>> - Download ApproveSDK.xml into that folder from:
>>
>>
>>https://dist.apache.org/repos/dist/dev/flex/sdk/4.14.1/rc1/ApproveSDK.xml
>>
>> - Run: ant -e -f ApproveSDK.xml -Drelease.version=4.14.1 -Drc=2
>>
>> Thanks,
>>
>> EdB
>>
>>
>>
>
Re: Linux CheckinTests (was Re: [VOTE] Apache Flex SDK 4.14.1 RC1)
Posted by Alex Harui <ah...@adobe.com>.
Flashlog.txt is where the debugger player outputs trace() calls. You need
an mm.cfg file with the right settings to tell the player to write that
file. The internet was a bit confusing about where it stores it on Linux.
Maybe you can make sense of it.
On 3/24/15, 9:46 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>On 24/03/15 16:21, Alex Harui wrote:
>> The console output won’t get reflected to the flashlog.txt, but the
>> results parser is looking in flashlog.txt for output. So maybe
>> flashlog.txt will stop logging or show some other error.
>>
>>
>
>I don't have a flashlog.txt file anywhere in my home folder or in /tmp
>(where the RC is unpacked).
>Do I need to turn it on somehow ?
>
>Tom
Re: Linux CheckinTests (was Re: [VOTE] Apache Flex SDK 4.14.1 RC1)
Posted by Tom Chiverton <tc...@extravision.com>.
On 24/03/15 16:21, Alex Harui wrote:
> The console output won’t get reflected to the flashlog.txt, but the
> results parser is looking in flashlog.txt for output. So maybe
> flashlog.txt will stop logging or show some other error.
>
>
I don't have a flashlog.txt file anywhere in my home folder or in /tmp
(where the RC is unpacked).
Do I need to turn it on somehow ?
Tom
Re: Linux CheckinTests (was Re: [VOTE] Apache Flex SDK 4.14.1 RC1)
Posted by Alex Harui <ah...@adobe.com>.
The console output won’t get reflected to the flashlog.txt, but the
results parser is looking in flashlog.txt for output. So maybe
flashlog.txt will stop logging or show some other error.
-Alex
On 3/24/15, 8:40 AM, "Tom Chiverton" <tc...@extravision.com> wrote:
>On 24/03/15 14:58, Alex Harui wrote:
>> Tom,
>>
>> This is definitely that important, but BasicTests doesn’t do bitmap
>> compares so it shouldn’t be a matter of generating correct pictures if I
>> understand you correctly. What kind of failure is being reported?
>
>I've rebuilt now and the tests eventually explode with a null pointer
>exception:
>
>/tmp/apache-flex-sdk-4.14.1-src/frameworks/tests/basicTests/spark/views/He
>lloWorld.swf
>(62954 bytes)
>launching player and swf
>(flashplayerdebugger:20865): GLib-GObject-WARNING **: instance with
>invalid (NULL) class pointer
>(flashplayerdebugger:20865): GLib-GObject-CRITICAL **:
>g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
>(instance)' failed
>BUILD FAILED
>/tmp/ApproveSDK.xml:387: The following error occurred while executing
>this line:
>/tmp/apache-flex-sdk-4.14.1-src/build.xml:1570: exec returned: 1
>
>That was using the 11.2.202.394 debugger player. I upgraded to the very
>latest 11.2.202.451 and re-ran basictests (with no rebuild) and it moves
>the crash a little:
>
>(flashplayerdebugger:21111): GLib-GObject-WARNING **: instance with
>invalid (NULL) class pointer
>(flashplayerdebugger:21111): GLib-GObject-CRITICAL **:
>g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
>(instance)' failed
>
>I always though it was just me.
>Is there a way to get detailed test-by-test output for the basictests to
>see if it's one in particular that triggers it ?
>
>Tom
Re: Linux CheckinTests (was Re: [VOTE] Apache Flex SDK 4.14.1 RC1)
Posted by Tom Chiverton <tc...@extravision.com>.
On 24/03/15 14:58, Alex Harui wrote:
> Tom,
>
> This is definitely that important, but BasicTests doesn’t do bitmap
> compares so it shouldn’t be a matter of generating correct pictures if I
> understand you correctly. What kind of failure is being reported?
I've rebuilt now and the tests eventually explode with a null pointer
exception:
/tmp/apache-flex-sdk-4.14.1-src/frameworks/tests/basicTests/spark/views/HelloWorld.swf
(62954 bytes)
launching player and swf
(flashplayerdebugger:20865): GLib-GObject-WARNING **: instance with
invalid (NULL) class pointer
(flashplayerdebugger:20865): GLib-GObject-CRITICAL **:
g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
(instance)' failed
BUILD FAILED
/tmp/ApproveSDK.xml:387: The following error occurred while executing
this line:
/tmp/apache-flex-sdk-4.14.1-src/build.xml:1570: exec returned: 1
That was using the 11.2.202.394 debugger player. I upgraded to the very
latest 11.2.202.451 and re-ran basictests (with no rebuild) and it moves
the crash a little:
(flashplayerdebugger:21111): GLib-GObject-WARNING **: instance with
invalid (NULL) class pointer
(flashplayerdebugger:21111): GLib-GObject-CRITICAL **:
g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
(instance)' failed
I always though it was just me.
Is there a way to get detailed test-by-test output for the basictests to
see if it's one in particular that triggers it ?
Tom