https://bz.mercurial-scm.org/show_bug.cgi?id=6580

            Bug ID: 6580
           Summary: test-upgrade-repo.t and other failures on s390x
                    (64-bit big endian)
           Product: Mercurial
           Version: 5.9
          Hardware: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: bug
          Priority: wish
         Component: Mercurial
          Assignee: bugzi...@mercurial-scm.org
          Reporter: jcris...@debian.org
                CC: mercurial-devel@mercurial-scm.org
    Python Version: ---

From the debian build of mercurial 5.9 on s390x:
https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=s390x&ver=5.9-1&stamp=1629766216&raw=0
a number of tests are failing.  Some of them similar to bug 6188, others I'm
not sure, but possibly endianness issues.

Failed test-censor.t#revlogv2: output changed
Failed test-clone-uncompressed.t#stream-bundle2: output changed
Failed test-clone-uncompressed.t#stream-legacy: output changed
Failed test-copies-in-changeset.t#sidedata: output changed
Failed test-generaldelta.t: output changed
Failed test-persistent-nodemap.t: output changed
Failed test-sidedata-exchange.t: output changed
Failed test-sidedata.t: output changed
Failed test-transaction-safety.t#revlogv2: output changed
Failed test-upgrade-repo.t: output changed

--- /<<PKGBUILDDIR>>/tests/test-upgrade-repo.t
+++ /<<PKGBUILDDIR>>/tests/test-upgrade-repo.t.err
@@ -1531,9 +1531,8 @@
   sparserevlog
   store
   $ hg debugsidedata -c 0
-  2 sidedata entries
-   entry-0001 size 4
-   entry-0002 size 32
+  abort: cannot read from revlog 00changelog-5e69c5d1.sda;  expected
1942585158 bytes from offset 0, data size is 90
+  [50]

 downgrade

@@ -1552,6 +1551,8 @@
     - changelog
     - manifest

+  abort: cannot read from revlog data/foo-1335303a.sda;  expected 1942585158
bytes from offset 0, data size is 0
+  [50]
   $ hg debugformat -v
   format-variant     repo config default
   fncache:            yes    yes     yes
@@ -1563,7 +1564,7 @@
   persistent-nodemap:  no     no      no (no-rust !)
   persistent-nodemap: yes    yes      no (rust !)
   copies-sdc:          no     no      no
-  revlog-v2:           no     no      no
+  revlog-v2:          yes     no      no
   changelog-v2:        no     no      no
   plain-cl-delta:     yes    yes     yes
   compression:        zlib   zlib    zlib (no-zstd !)
@@ -1571,14 +1572,16 @@
   compression-level:  default default default
   $ cat .hg/requires
   dotencode
-  fncache
+  exp-revlogv2.2
+  fncache
+  persistent-nodemap (rust !)
   generaldelta
-  persistent-nodemap (rust !)
-  revlog-compression-zstd (zstd !)
-  revlogv1
+  revlog-compression-zstd
   sparserevlog
   store
   $ hg debugsidedata -c 0
+  abort: cannot read from revlog 00changelog-5e69c5d1.sda;  expected
1942585158 bytes from offset 0, data size is 90
+  [50]

 upgrade from hgrc

@@ -1587,20 +1590,8 @@
   > revlogv2=enable-unstable-format-and-corrupt-my-data
   > EOF
   $ hg debugupgraderepo --run --no-backup --quiet
-  upgrade will perform the following actions:
-  
-  requirements
      preserved: dotencode, fncache, generaldelta, sparserevlog, store (no-zstd
!)
-     preserved: dotencode, fncache, generaldelta, revlog-compression-zstd,
sparserevlog, store (zstd no-rust !)
      preserved: dotencode, fncache, generaldelta, persistent-nodemap,
revlog-compression-zstd, sparserevlog, store (rust !)
-     removed: revlogv1
-     added: exp-revlogv2.2
-  
-  processed revlogs:
-    - all-filelogs
-    - changelog
-    - manifest
-  
   $ hg debugformat -v
   format-variant     repo config default
   fncache:            yes    yes     yes
@@ -1628,6 +1619,8 @@
   sparserevlog
   store
   $ hg debugsidedata -c 0
+  abort: cannot read from revlog 00changelog-5e69c5d1.sda;  expected
1942585158 bytes from offset 0, data size is 90
+  [50]

 Demonstrate that nothing to perform upgrade will still run all the way through


ERROR: test-upgrade-repo.t output changed
!# Ret was: 0 (test-upgrade-repo.t)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Reply via email to