git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] test-progress: fix test failures on big-endian systems

From
SZEDER Gábor <szeder.dev@gmail.com>
Date
Oct 19, 2019, 23:37 UTC
Message-ID
<20191019233706.GM29845@szeder.dev>
In-Reply-To
<f1ce445e-6954-8e7b-2dca-3a566ce689a5@physik.fu-berlin.de>
On Sat, Oct 19, 2019 at 11:38:40PM +0200, John Paul Adrian Glaubitz wrote:
> The testsuite is failing again on s390x and all other big-endian targets in
> Debian. For a full build log on s390x see [1].
Gah, my progress display fixes strike again...

I think the patch below should fix it, but I could only test it on little-endian systems. Could you please confirm that it indeed works on big-endian as well?

  --- >8 ---
Subject: [PATCH] test-progress: fix test failures on big-endian systems

In 't0500-progress-display.sh' all tests running 'test-tool progress --total=<N>' fail on big-endian systems, e.g. like this:

  + test-tool progress --total=3 Working hard
  [...]
  + test_i18ncmp expect out
  --- expect	2019-10-18 23:07:54.765523916 +0000
  +++ out	2019-10-18 23:07:54.773523916 +0000
  @@ -1,4 +1,2 @@
  -Working hard:  33% (1/3)<CR>
  -Working hard:  66% (2/3)<CR>
  -Working hard: 100% (3/3)<CR>
  -Working hard: 100% (3/3), done.
  +Working hard:   0% (1/12884901888)<CR>
  +Working hard:   0% (3/12884901888), done.

The reason for that bogus value is that '--total's parameter is parsed via parse-options's OPT_INTEGER into a uint64_t variable [1], so the two bits of 3 end up in the "wrong" bytes on big-endian systems (12884901888 = 0x300000000).

Change the type of that variable from uint64_t to int, to match what parse-options expects; in the tests of the progress output we won't use values that don't fit into an int anyway.

[1] start_progress() expects the total number as an uint64_t, that's
    why I chose the same type when declaring the variable holding the
    value given on the command line.
Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
---
 t/helper/test-progress.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/t/helper/test-progress.c b/t/helper/test-progress.c
index 4e9f7fafdf..42b96cb103 100644
--- a/t/helper/test-progress.c
+++ b/t/helper/test-progress.c
@@ -29,7 +29,7 @@ void progress_test_force_update(void);
 
 int cmd__progress(int argc, const char **argv)
 {
-	uint64_t total = 0;
+	int total = 0;
 	const char *title;
 	struct strbuf line = STRBUF_INIT;
 	struct progress *progress;
-- 
2.24.0.rc0.472.ga6f06c86b4
Previous: John Paul Adrian GlaubitzNext: John Paul Adrian Glaubitz
Message 4 of 14 in “[BUG]: Testsuite failures on big-endian targets”
  1. John Paul Adrian GlaubitzJul 31, 2019
  2. Todd ZullingerJul 31, 2019
  3. John Paul Adrian GlaubitzOct 19, 2019
  4. test-progress: fix test failures on big-endian systemsSZEDER Gábor, Oct 19, 2019
  5. John Paul Adrian GlaubitzOct 19, 2019
  6. Todd ZullingerOct 20, 2019
  7. Junio C HamanoOct 21, 2019
  8. Jeff KingOct 21, 2019
  9. Junio C HamanoOct 21, 2019
  10. Jeff KingOct 21, 2019
  11. Junio C HamanoOct 23, 2019
  12. SZEDER GáborOct 24, 2019
  13. Jeff KingOct 24, 2019
  14. Todd ZullingerOct 20, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.