14 Nov, 2019

2 commits

  • fixes: 8ab452d5877638a97e5bdd521d119403b70b45f5

    When compiling list of cover letter cc addresses, using null as a
    separater, then encoding to utf-8 results in lots of "\x00" as
    separators. patman then doesnt understand that when it comes to
    repoting the list to send-email.

    Fix this by not encoding to utf-8, as done for the other patch files.

    Signed-off-by: Robert Beckett
    Reviewed-by: Simon Glass

    Robert Beckett
     
  • s/Subprocress/Subprocess/
    s/easiler/easier/
    s/repositiory/repository/
    s/rangem/range/
    s/Retruns/Returns/

    Signed-off-by: Anatolij Gustschin
    Reviewed-by: Simon Glass

    Anatolij Gustschin
     

05 Nov, 2019

3 commits


28 Oct, 2019

1 commit

  • There is a contributor in Linux kernel with a comma in their name, which
    confuses patman and results in invalid to- or cc- addresses on some
    patches. To avoid this, let's use \0 as a separator when generating cc
    file.

    Signed-off-by: Dmitry Torokhov
    Reviewed-by: Simon Glass

    Dmitry Torokhov
     

15 Oct, 2019

4 commits

  • As per the centithread on ksummit-discuss [1], there are folks who
    feel that if a Change-Id is present in a developer's local commit that
    said Change-Id could be interesting to include in upstream posts.
    Specifically if two commits are posted with the same Change-Id there's
    a reasonable chance that they are either the same commit or a newer
    version of the same commit. Specifically this is because that's how
    gerrit has trained people to work.

    There is much angst about Change-Id in upstream Linux, but one thing
    that seems safe and non-controversial is to include the Change-Id as
    part of the string of crud that makes up a Message-Id.

    Let's give that a try.

    In theory (if there is enough adoption) this could help a tool more
    reliably find various versions of a commit. This actually might work
    pretty well for U-Boot where (I believe) quite a number of developers
    use patman, so there could be critical mass (assuming that enough of
    these people also use a git hook that adds Change-Id to their
    commits). I was able to find this git hook by searching for "gerrit
    change id git hook" in my favorite search engine.

    In theory one could imagine something like this could be integrated
    into other tools, possibly even git-send-email. Getting it into
    patman seems like a sane first step, though.

    NOTE: this patch is being posted using a patman containing this patch,
    so you should be able to see the Message-Id of this patch and see that
    it contains my local Change-Id, which ends in 2b9 if you want to
    check.

    [1] https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2019-August/006739.html

    Signed-off-by: Douglas Anderson

    Douglas Anderson
     
  • Remove this file from git and instead build it using the Makefile.

    Update tools.GetInputFilename() to support reading files from an absolute
    path, so that we can read the Elf test files easily. Also make sure that
    the temp directory is report in ELF tests as this was commented out.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • At present tools are not expected to fail. If they do an exception is
    raised but there is no detail about what went wrong. This makes it hard
    to debug if something does actually go wrong.

    Fix this by outputting both stderr and stdout on failure.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • Since cros_subprocess use bytestrings now, this feature not needed. Drop
    it.

    Signed-off-by: Simon Glass

    Simon Glass
     

29 Jul, 2019

5 commits

  • At present outdir remains set ever after the output directory has been
    removed. Fix this to avoid trying to access it when it is not present.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • At present binman cannot replace data within a CBFS since it does not
    allow rewriting of the files in that CBFS. Implement this by using the
    new WriteData() method to handle the case.

    Add a header to compressed data so that the amount of compressed data can
    be determined without reference to the size of the containing entry. This
    allows the entry to be larger that the contents, without causing errors in
    decompression. This is necessary to cope with a compressed device tree
    being updated in such a way that it shrinks after the entry size is
    already set (an obscure case). It is not used with CBFS since it has its
    own metadata for this. Increase the number of passes allowed to resolve
    the position of entries, to handle this case.

    Add a test for this new logic.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • Use the new logging feature to log information about progress with
    packing. This is useful to see how binman is figuring things out.

    Also update elf.py to use the same feature.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • Use the debug level constants instead of open-coding them in the file.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • At present tout writes directly to stdout. This is not necessary and it
    prevents tests from redirecting output. Change it to use print() for the
    non-progress output.

    Signed-off-by: Simon Glass

    Simon Glass
     

25 Jul, 2019

4 commits


24 Jul, 2019

3 commits


11 Jul, 2019

16 commits


08 Oct, 2018

2 commits

  • At present the tests run one after the other using a single CPU. This is
    not very efficient. Bring in the concurrencytest module and run the tests
    concurrently, using one process for each CPU by default. A -P option
    allows this to be overridden, which is necessary for code-coverage to
    function correctly.

    This requires fixing a few tests which are currently not fully
    independent.

    At some point we might consider doing this across all pytests in U-Boot.
    There is a pytest version that supports specifying the number of processes
    to use, but it did not work for me.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • At present calling Uninit() always called ClearProgress() which outputs
    a \r character as well as spaces to remove any progress information on the
    line. This can mess up the normal output of binman and other tools. Fix
    this by outputing this only when progress information has actually been
    previous written.

    Signed-off-by: Simon Glass

    Simon Glass