Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-8737

Lustre upstream client tree for testing is wrong branch

Details

    • Bug
    • Resolution: Not a Bug
    • Minor
    • None
    • None
    • None
    • lustre staging tree that gerrit uses.
    • 3
    • 9223372036854775807

    Description

      Now that the upstream client is approaching the 2.8 version it is time to hook in testing setup to verify potential patches to land. When I went to check out the staging tree used for testing I noticed it is based on the wrong git tree. It needs to be based on the staging tree's staging-next branch.

      Attachments

        Issue Links

          Activity

            [LU-8737] Lustre upstream client tree for testing is wrong branch

            From Doug's latest patch that was pushed it appears that the commit message issues has been fixed. Does checkpatch run against a submitted patch. Also it looks like the test suite is run against staging-testing branch which is correct. We are making progress.

            simmonsja James A Simmons added a comment - From Doug's latest patch that was pushed it appears that the commit message issues has been fixed. Does checkpatch run against a submitted patch. Also it looks like the test suite is run against staging-testing branch which is correct. We are making progress.

            Yep Jenkins passed. Now for the checkpatch and commit message issue.

            simmonsja James A Simmons added a comment - Yep Jenkins passed. Now for the checkpatch and commit message issue.
            mdiep Minh Diep added a comment -

            I will look into the commit message being mangled; and checkpatch .

            The jenkins build links should be accessible now

            mdiep Minh Diep added a comment - I will look into the commit message being mangled; and checkpatch . The jenkins build links should be accessible now

            Minh I noticed a few oddities with the pushed patch. The Intel-bug-id: url seems to have gotten mangled. The jenkins build links is also invalid. Lastly do you think it would be possible to get linux/scripts/checkpatch to run against the patch and report the result.

            Thanks Peter

            simmonsja James A Simmons added a comment - Minh I noticed a few oddities with the pushed patch. The Intel-bug-id: url seems to have gotten mangled. The jenkins build links is also invalid. Lastly do you think it would be possible to get linux/scripts/checkpatch to run against the patch and report the result. Thanks Peter
            pjones Peter Jones added a comment -

            Don't be so hard on yourself James

            pjones Peter Jones added a comment - Don't be so hard on yourself James

            You are right. I'm a idiot. I just pushed the patch. It works:

            http://review.whamcloud.com/#/c/23382

            simmonsja James A Simmons added a comment - You are right. I'm a idiot. I just pushed the patch. It works: http://review.whamcloud.com/#/c/23382
            mdiep Minh Diep added a comment -

            I would think you should use HEAD:refs/for/staging-testing to push for review; and which will trigger a build and test

            mdiep Minh Diep added a comment - I would think you should use HEAD:refs/for/staging-testing to push for review; and which will trigger a build and test

            People

              mdiep Minh Diep
              simmonsja James A Simmons
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: