Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8337283

configure.log is truncated when build dir is on different filesystem

    XMLWordPrintable

Details

    • b10

    Backports

      Description

        I noticed that build/$confname/configure.log was truncated on some of my build nodes. Turns out, we are moving configure.log from tree root to that place a bit prematurely.

        We move `configure.log` here:
        https://github.com/openjdk/jdk/blob/4f194f10a1481cdc9df4e6338f6cabd07a34c84c/make/autoconf/basic.m4#L594-L618

        ...and that is called here:
        https://github.com/openjdk/jdk/blob/4bcb8f04ed3623da7c84dda28017f473cbc97e53/make/autoconf/configure.ac#L316

        Or, before we print configuration summary.

        Now, this works most of the time by accident: when root dir and build dir are on the same filesystem, the file move does not interfere with inodes/FDs, and we are still able to write to the same file _after_ we moved. But if build dir is on _another_ filesystem, then we miss writing the configuration summary when file moves away.

        Apparently, my systems fall into that trap, since build dir is on RAM disk.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8338239 configure.log is truncated when build dir is on different filesystem

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8338316 configure.log is truncated when build dir is on different filesystem

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8338317 configure.log is truncated when build dir is on different filesystem

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved
            links to

            Commit Commit(master) openjdk/jdk17u-dev/4aa7950d

            Commit Commit(master) openjdk/jdk21u-dev/bafcddd9

            Commit Commit(master) openjdk/jdk23u/677c18ef

            Commit Commit(master) openjdk/jdk/7e925d72

            Review Review(master) openjdk/jdk17u-dev/2784

            Review Review(master) openjdk/jdk21u-dev/895

            Review Review(master) openjdk/jdk23u/53

            Review Review(master) openjdk/jdk/20356

            Activity

              People

                shade Aleksey Shipilev
                shade Aleksey Shipilev
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: