Recherche avancée

Sur d’autres sites (10949)

• Merge commit ’c4d37cd9ef6e374bb888f6273259b10fac5bd909’

  8 avril 2015, par Michael Niedermayer

  Merge commit ’c4d37cd9ef6e374bb888f6273259b10fac5bd909’
  * commit ’c4d37cd9ef6e374bb888f6273259b10fac5bd909’ :
  
    matroskadec : export cover art correctly
  Conflicts :
  
  	libavformat/matroskadec.c
  See : 511585ce7f7272e5069ef011d6be5f073d268901
  
  Merged-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavformat/matroskadec.c

• Revision bde04ce503 : Merge branch 'frame-parallel' to enable frame parallel decode in master branch.

  21 janvier 2015, par hkuang

  Changed Paths :
   Modify /test/test-data.mk

  
   Modify /test/test-data.sha1

  
   Modify /test/test.mk

  
   Modify /test/test_vector_test.cc

  
   Modify /test/test_vectors.cc

  
   Modify /test/vp9_encoder_parms_get_to_decoder.cc

  
   Modify /test/vp9_frame_parallel_test.cc

  
   Modify /vp9/common/vp9_alloccommon.c

  
   Modify /vp9/common/vp9_alloccommon.h

  
   Modify /vp9/common/vp9_entropymode.c

  
   Modify /vp9/common/vp9_mvref_common.c

  
   Modify /vp9/common/vp9_mvref_common.h

  
   Modify /vp9/common/vp9_onyxc_int.h

  
   Modify /vp9/common/vp9_reconinter.c

  
   Modify /vp9/common/vp9_reconinter.h

  
   Modify /vp9/decoder/vp9_decodeframe.c

  
   Modify /vp9/decoder/vp9_decodeframe.h

  
   Modify /vp9/decoder/vp9_decodemv.c

  
   Modify /vp9/decoder/vp9_decoder.c

  
   Modify /vp9/decoder/vp9_decoder.h

  
   Modify /vp9/decoder/vp9_dthread.c

  
   Modify /vp9/decoder/vp9_dthread.h

  
   Modify /vp9/encoder/vp9_encoder.c

  
   Modify /vp9/encoder/vp9_encoder.h

  
   Modify /vp9/encoder/vp9_firstpass.c

  
   Modify /vp9/encoder/vp9_pickmode.c

  
   Modify /vp9/encoder/vp9_rd.c

  
   Modify /vp9/encoder/vp9_rdopt.c

  
   Modify /vp9/vp9_cx_iface.c

  
   Modify /vp9/vp9_dx_iface.c

  
   Modify /vp9/vp9dx.mk

  
   Modify /vpx/vpx_frame_buffer.h

  
  
  Merge branch ’frame-parallel’ to enable frame parallel decode in master branch.

  In frame parallel decode, libvpx decoder decodes several frames on all
  cpus in parallel fashion. If not being flushed, it will only return frame
  when all the cpus are busy. If getting flushed, it will return all the
  frames in the decoder. Compare with current serial decode mode in which
  libvpx decoder is idle between decode calls, libvpx decoder is busy
  between decode calls. VP9 frame parallel decode is >30% faster than serial
  decode with tile parallel threading which will makes devices play 1080P
  VP9 videos more easily.

  * frame-parallel :
  Add error handling for frame parallel decode and unit test for that.
  Fix a bug in frame parallel decode and add a unit test for that.
  Add two test vectors to test frame parallel decode.
  Add key frame seeking to webmdec and webm_video_source.
  Implement frame parallel decode for VP9.
  Increase the thread test range to cover 5, 6, 7, 8 threads.
  Fix a bug in adding frame parallel unit test.
  Add VP9 frame-parallel unit test.
  Manually pick "Make the api behavior conform to api spec." from master branch.
  Move vp9_dec_build_inter_predictors_* to decoder folder.
  Add segmentation map array for current and last frame segmentation.
  Include the right header for VP9 worker thread.
  Move vp9_thread.* to common.
  ctrl_get_reference does not need user_priv.
  Seperate the frame buffers from VP9 encoder/decoder structure.
  Revert "Revert "Revert "Revert 3 patches from Hangyu to get Chrome to
  build :"""

  Conflicts :
  test/codec_factory.h
  test/decode_test_driver.cc
  test/decode_test_driver.h
  test/invalid_file_test.cc
  test/test-data.sha1
  test/test.mk
  test/test_vectors.cc
  vp8/vp8_dx_iface.c
  vp9/common/vp9_alloccommon.c
  vp9/common/vp9_entropymode.c
  vp9/common/vp9_loopfilter_thread.c
  vp9/common/vp9_loopfilter_thread.h
  vp9/common/vp9_mvref_common.c
  vp9/common/vp9_onyxc_int.h
  vp9/common/vp9_reconinter.c
  vp9/decoder/vp9_decodeframe.c
  vp9/decoder/vp9_decodeframe.h
  vp9/decoder/vp9_decodemv.c
  vp9/decoder/vp9_decoder.c
  vp9/decoder/vp9_decoder.h
  vp9/encoder/vp9_encoder.c
  vp9/encoder/vp9_pickmode.c
  vp9/encoder/vp9_rdopt.c
  vp9/vp9_cx_iface.c
  vp9/vp9_dx_iface.c

  Change-Id : Ib92eb35851c172d0624970e312ed515054e5ca64

• How to write unit tests for your plugin – Introducing the Piwik Platform

  17 novembre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to verify user permissions). This time you’ll learn how to write unit tests in Piwik. For this tutorial you will need to have basic knowledge of PHP, PHPUnit and the Piwik platform.

  When is a test a unit test ?

  There are many different opinions on this and it can be sometimes hard to decide. At Piwik we consider a test as a unit test if only a single method or class is being tested and if a test does not have a dependency to the filesystem, web, config, database or to any other plugin.

  If a test is slow it can be an indicator that it is not a unit test. “Slow” is of course a bit vague. We will cover how to write other type of tests, such as integration tests, in one of our next blog posts.

  Getting started

  In this post, we assume that you have already installed Piwik 2.9.0 or later via git, set up your development environment and created a plugin. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik and other Guides that help you to develop a plugin.

  Let’s create a unit test

  We start by using the Piwik Console to create a new unit test :

  ./console generate:test --testtype unit

  The command will ask you to enter the name of the plugin the created test should belong to. I will use the plugin name “Insights”. Next it will ask you for the name of the test. Here you usually enter the name of the class you want to test. I will use “Widgets” in this example. There should now be a file plugins/Insights/tests/Unit/WidgetsTest.php which contains already an example to get you started easily :

  /**
   * @group Insights
   * @group WidgetsTest
   * @group Plugins
   */
  class WidgetsTest extends \PHPUnit_Framework_TestCase
  {
   
      public function testSimpleAddition()
      {
          $this->assertEquals(2, 1+1);
      }
   
  }
  Télécharger

  We don’t want to cover how you should write your unit test. This is totally up to you. If you have no experience in writing unit tests yet, we recommend to read articles on the topic, or a book, or to watch videos or anything else that will help you learn best.

  Running a test

  To run a test we will use the command tests:run which allows you to execute a test suite, a specific file or a group of tests.

  To verify whether the created test works we will run it as follows :

  ./console tests:run WidgetsTest

  This will run all tests having the group WidgetsTest. As other tests can use the same group you might want to pass the path to your test file instead :

  ./console tests:run plugins/Insights/tests/Unit/Widgets.php

  If you want to run all tests within your plugin pass the name of your plugin as an argument :

  ./console tests:run insights

  Of course you can also define multiple arguments :

  ./console tests:run insights WidgetsTest

  This will execute all tests within the insights plugin having the group WidgetsTest. If you only want to run unit tests within your plugin you can do the following :

  ./console tests:run insights unit

  Advanced features

  Isn’t it easy to create a unit test ? We never even created a file ! You can accomplish even more if you want : You can generate other type of tests, you can run tests on Amazon’s AWS and more. Unfortunately, not everything is documented yet so we recommend to discover more features by executing the commands ./console list tests and ./console help tests:run.

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.