Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-4700

Buildbot tests on Wheezy are failing with parsechangelog/debian error

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Some time between June 18 and June 20 Debian Wheezy tests (both 32-bit and 64-bit) started failing like this:

      Copying distribution specific build files for Debian
      Incrementing changelog and starting build scripts
      dch warning: Recognised distributions are: unstable, testing, stable,
      oldstable, experimental, {testing-,stable-,oldstable-,}proposed-updates,
      {testing,stable,oldstable}-security, squeeze-backports and UNRELEASED.
      Using your request anyway.
      dch warning: Previous package version was Debian native whilst new version is not
      dch: Did you see that warning?  Press RETURN to continue...
      Creating package version 10.0.3+maria-1~n/a ... 
      parsechangelog/debian: warning:     debian/changelog(l29): found eof where expected first heading
      parsechangelog/debian: error: fatal error occurred while parsing input
      dpkg-buildpackage: error: changelog parser /usr/lib/dpkg/parsechangelog/debian gave error exit status 255
      Command exit 255
      + ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o LogLevel=ERROR -o ConnectTimeout=4 -p 2270 -l buildbot localhost sudo /sbin/shutdown -h now
      program finished with exit code 255
      

      It happens both on 10.0 and 5.5 (at least), and the code changes seem to be unrelated, so I assume there is something with the environment.
      Examples:

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-wheezy-x86/builds/545/steps/compile/logs/stdio
      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-wheezy-amd64/builds/1067/steps/compile/logs/stdio

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            dbart Daniel Bartholomew added a comment -

            Hmmm... sounds like Debian updated their repositories. I'll investigate and fix.

            Show
            dbart Daniel Bartholomew added a comment - Hmmm... sounds like Debian updated their repositories. I'll investigate and fix.
            Hide
            dbart Daniel Bartholomew added a comment -

            The command that I believe is tripping things up is:
            lsb_release -sc

            This command is supposed to return "wheezy" but instead the command is returning "n/a", which is obviously not correct.

            Show
            dbart Daniel Bartholomew added a comment - The command that I believe is tripping things up is: lsb_release -sc This command is supposed to return "wheezy" but instead the command is returning "n/a", which is obviously not correct.
            Hide
            dbart Daniel Bartholomew added a comment -

            In the spirit of trying to make the most minimal update possible, here's a proposed solution:

            On each wheezy build VM do:
            1. boot the VM
            2. sudo apt-get update
            3. sudo apt-get install lsb-release
            4. lsb_release -sc # to test the fix
            5. sudo /sbin/shutdown -h now

            There are a lot of packages that could be updated, but this should fix the issue with the lsb_release program not outputting the correct information. After applying, I'll test.

            Show
            dbart Daniel Bartholomew added a comment - In the spirit of trying to make the most minimal update possible, here's a proposed solution: On each wheezy build VM do: 1. boot the VM 2. sudo apt-get update 3. sudo apt-get install lsb-release 4. lsb_release -sc # to test the fix 5. sudo /sbin/shutdown -h now There are a lot of packages that could be updated, but this should fix the issue with the lsb_release program not outputting the correct information. After applying, I'll test.
            Hide
            dbart Daniel Bartholomew added a comment -

            fixed, so closing, re-open if necessary

            Show
            dbart Daniel Bartholomew added a comment - fixed, so closing, re-open if necessary

              People

              • Assignee:
                dbart Daniel Bartholomew
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h