Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Spark to version 3.1.1 #247

Merged
merged 11 commits into from
May 4, 2021
Merged

Update Spark to version 3.1.1 #247

merged 11 commits into from
May 4, 2021

Commits on Apr 30, 2021

  1. Update Spark to version 3.1.1

    This skips version 3.0.2 and goes directly to 3.1.1. There are no
    compilation issues and the apache-spark benchmarks execute normally.
    lbulej committed Apr 30, 2021
    Configuration menu
    Copy the full SHA
    424b762 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    5488438 View commit details
    Browse the repository at this point in the history

Commits on May 2, 2021

  1. Tell SBT to use 2048 megs of memory

    SBT uses 1024 by default and kills memory-related JVM options in the
    `.sbtopts` file and derives its values on its own. The default memory
    size results in code cache of 128 megs, which is insufficient for a
    pristine build, where it can reach slightly over 200 megs. Raising the
    memory to 2048 increases the code cache size to 256 megs.
    lbulej committed May 2, 2021
    Configuration menu
    Copy the full SHA
    36d88c6 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    f8df99e View commit details
    Browse the repository at this point in the history
  3. Use git describe to determine Renaissance version

    This will avoid having to change the version number in multiple
    places. The current version number is determine by the latest
    (annotated) tag and the distance to it from the current commit.
    Release built from the tagged commit will have a "clean" version
    number, others will include the hash of the build commit.
    
    CI scripts will be able to determine the current version simply
    by using `git describe` and stripping the initial `v`.
    
    The only thing that needs to be updated is the git.baseVersion
    setting in renaissance-core/version.sbt, which provides a base
    (upcoming) version number for git-less situations, i.e., when
    building the sources outside the git tree.
    lbulej committed May 2, 2021
    Configuration menu
    Copy the full SHA
    f420798 View commit details
    Browse the repository at this point in the history
  4. Only include the base version in the generated README.md

    This will avoid having to update README.md with each commit.
    lbulej committed May 2, 2021
    Configuration menu
    Copy the full SHA
    190caa7 View commit details
    Browse the repository at this point in the history
  5. Update reactors to support git-less compilation

    Removes task to write out .gitprops which does not work in git-less
    mode and is not needed anyway. Also adds a proper version related to
    the upstream master and the exported dependency.
    lbulej committed May 2, 2021
    Configuration menu
    Copy the full SHA
    2b4239a View commit details
    Browse the repository at this point in the history

Commits on May 3, 2021

  1. Use git-described version and check encoding and markdown in pre-push

    These checks are also made in the CI, but it does not hurt to
    have them in the pre-push hook. The markdown check requires a
    successful build of the base JAR.
    lbulej committed May 3, 2021
    Configuration menu
    Copy the full SHA
    2b1ba5f View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    db26b9c View commit details
    Browse the repository at this point in the history
  3. Use CI actions in .travis.yml

    The goal is to use the `script` section of `.travis.yml` for
    higher-level actions instead of low-level file management.
    lbulej committed May 3, 2021
    Configuration menu
    Copy the full SHA
    6c6e563 View commit details
    Browse the repository at this point in the history

Commits on May 4, 2021

  1. Configuration menu
    Copy the full SHA
    a8199ab View commit details
    Browse the repository at this point in the history