Skip to content

[UI] Transaction Date Range: persistence added and format modified - #884

Merged
schinzelh merged 1 commit into
dashpay:v0.12.1.xfrom
crowning-:Date_Range
Jun 13, 2016
Merged

[UI] Transaction Date Range: persistence added and format modified#884
schinzelh merged 1 commit into
dashpay:v0.12.1.xfrom
crowning-:Date_Range

Conversation

@crowning-

@crowning-crowning- commented Jun 12, 2016

Copy link
Copy Markdown

Reference: #879

It's a compromise between requested functionality and overcrowded wallet-UI.

  1. - the selected option ("Range...") and the chosen dates of the range are persisted now
  2. - date format changed to standard date format

Looks like this now:
date_range

@UdjinM6

Copy link
Copy Markdown

Looks good 👍
utACK a4403eb

@schinzelh

Copy link
Copy Markdown

utACK a4403eb

@crowning-

Copy link
Copy Markdown
Author

I think, after a wallet reset, the default date range "2000-01-01 / 2000-01-01" isn't the best default.

I'll change this to currentDate / currentDate+1 tomorrow.

Comment threadsrc/qt/transactionview.cpp Outdated

@UdjinM6UdjinM6Jun 13, 2016

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: trailing spaces

@crowning-

crowning- commented Jun 13, 2016

Copy link
Copy Markdown
Author

Default value set to currentDate / currentDate+1, minor refactoring, squashed into 1 commit.

Edit: spaces? Which spaces?

whistling1

@UdjinM6

Copy link
Copy Markdown

heh, ok...
Permissions? 😉

transactionview.cpp 100644 → 100755

@crowning-

Copy link
Copy Markdown
Author

Aargh, I shouldn't use Windows programs to edit stuff...

Reverted permissions and re-squashed.

@UdjinM6

Copy link
Copy Markdown

Looks good again now :)
utACK b7546d2

@schinzelh
schinzelh merged commit 0ee1bb5 into dashpay:v0.12.1.xJun 13, 2016
@crowning-
crowning- deleted the Date_Range branch August 23, 2016 16:06
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request Jul 1, 2021
…est deterministic
f899580 tests: Make coins_tests/updatecoins_simulation_test deterministic (practicalswift)
Pull request description:
Make `coins_tests/updatecoins_simulation_test` deterministic.
Before:
```
$ contrib/devtools/test_deterministic_coverage.sh 1000
[2019-06-15 05:36:20] Measuring coverage, run #1 of 1000
[2019-06-15 05:38:05] Measuring coverage, run #2 of 1000
[2019-06-15 05:39:49] Measuring coverage, run #3 of 1000
[2019-06-15 05:41:38] Measuring coverage, run #4 of 1000
[2019-06-15 05:43:16] Measuring coverage, run #5 of 1000
...
[2019-06-16 18:25:23] Measuring coverage, run dashpay#880 of 1000
[2019-06-16 18:27:12] Measuring coverage, run dashpay#881 of 1000
[2019-06-16 18:29:33] Measuring coverage, run dashpay#882 of 1000
[2019-06-16 18:33:00] Measuring coverage, run dashpay#883 of 1000
[2019-06-16 18:35:32] Measuring coverage, run dashpay#884 of 1000
The line coverage is non-deterministic between runs. Exiting.
The test suite must be deterministic in the sense that the set of lines executed at least
once must be identical between runs. This is a necessary condition for meaningful
coverage measuring.
--- gcovr.run-1.txt 2019-06-15 05:38:05.282359029 +0200
+++ gcovr.run-884.txt 2019-06-16 18:37:23.518298374 +0200
@@ -269,7 +269,7 @@
test/bloom_tests.cpp 320 320 100%
test/bswap_tests.cpp 13 13 100%
test/checkqueue_tests.cpp 223 222 99% 169
-test/coins_tests.cpp 478 472 98% 52,68,344-345,511,524
+test/coins_tests.cpp 478 474 99% 52,68,511,524
test/compilerbug_tests.cpp 18 18 100%
test/compress_tests.cpp 27 27 100%
test/crypto_tests.cpp 268 268 100%
@@ -401,5 +401,5 @@
zmq/zmqpublishnotifier.h 5 0 0% 12,31,37,43,49
zmq/zmqrpc.cpp 23 3 13% 16,18,20,23,33-35,37,40-47,51,62,64-65
------------------------------------------------------------------------------
-TOTAL 53323 28305 53%
+TOTAL 53323 28307 53%
------------------------------------------------------------------------------
```
After:
```
$ contrib/devtools/test_deterministic_coverage.sh 1000
[2019-06-15 05:36:20] Measuring coverage, run #1 of 1000
[2019-06-15 05:38:05] Measuring coverage, run #2 of 1000
[2019-06-15 05:39:49] Measuring coverage, run #3 of 1000
[2019-06-15 05:41:38] Measuring coverage, run #4 of 1000
[2019-06-15 05:43:16] Measuring coverage, run #5 of 1000
...
$
```
ACKs for commit f89958:
MarcoFalke:
ACK f899580 (checked that the randomness state of g_insecure_rand_ctx is the same after three test runs)
Tree-SHA512: 796d362b050c5750e351de1126b62f0f2c8e2d712cf01b6e1a3e2cc6ef92fa68439a32fc24c76d34bce4d553aee4ae4ea88a036c56eb9e25979649a19c59c3e5
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request Jul 13, 2021
…est deterministic
f899580 tests: Make coins_tests/updatecoins_simulation_test deterministic (practicalswift)
Pull request description:
Make `coins_tests/updatecoins_simulation_test` deterministic.
Before:
```
$ contrib/devtools/test_deterministic_coverage.sh 1000
[2019-06-15 05:36:20] Measuring coverage, run #1 of 1000
[2019-06-15 05:38:05] Measuring coverage, run #2 of 1000
[2019-06-15 05:39:49] Measuring coverage, run #3 of 1000
[2019-06-15 05:41:38] Measuring coverage, run #4 of 1000
[2019-06-15 05:43:16] Measuring coverage, run #5 of 1000
...
[2019-06-16 18:25:23] Measuring coverage, run dashpay#880 of 1000
[2019-06-16 18:27:12] Measuring coverage, run dashpay#881 of 1000
[2019-06-16 18:29:33] Measuring coverage, run dashpay#882 of 1000
[2019-06-16 18:33:00] Measuring coverage, run dashpay#883 of 1000
[2019-06-16 18:35:32] Measuring coverage, run dashpay#884 of 1000
The line coverage is non-deterministic between runs. Exiting.
The test suite must be deterministic in the sense that the set of lines executed at least
once must be identical between runs. This is a necessary condition for meaningful
coverage measuring.
--- gcovr.run-1.txt 2019-06-15 05:38:05.282359029 +0200
+++ gcovr.run-884.txt 2019-06-16 18:37:23.518298374 +0200
@@ -269,7 +269,7 @@
test/bloom_tests.cpp 320 320 100%
test/bswap_tests.cpp 13 13 100%
test/checkqueue_tests.cpp 223 222 99% 169
-test/coins_tests.cpp 478 472 98% 52,68,344-345,511,524
+test/coins_tests.cpp 478 474 99% 52,68,511,524
test/compilerbug_tests.cpp 18 18 100%
test/compress_tests.cpp 27 27 100%
test/crypto_tests.cpp 268 268 100%
@@ -401,5 +401,5 @@
zmq/zmqpublishnotifier.h 5 0 0% 12,31,37,43,49
zmq/zmqrpc.cpp 23 3 13% 16,18,20,23,33-35,37,40-47,51,62,64-65
------------------------------------------------------------------------------
-TOTAL 53323 28305 53%
+TOTAL 53323 28307 53%
------------------------------------------------------------------------------
```
After:
```
$ contrib/devtools/test_deterministic_coverage.sh 1000
[2019-06-15 05:36:20] Measuring coverage, run #1 of 1000
[2019-06-15 05:38:05] Measuring coverage, run #2 of 1000
[2019-06-15 05:39:49] Measuring coverage, run #3 of 1000
[2019-06-15 05:41:38] Measuring coverage, run #4 of 1000
[2019-06-15 05:43:16] Measuring coverage, run #5 of 1000
...
$
```
ACKs for commit f89958:
MarcoFalke:
ACK f899580 (checked that the randomness state of g_insecure_rand_ctx is the same after three test runs)
Tree-SHA512: 796d362b050c5750e351de1126b62f0f2c8e2d712cf01b6e1a3e2cc6ef92fa68439a32fc24c76d34bce4d553aee4ae4ea88a036c56eb9e25979649a19c59c3e5
gades pushed a commit to cosanta/cosanta-core that referenced this pull request Dec 3, 2023
…est deterministic
f899580 tests: Make coins_tests/updatecoins_simulation_test deterministic (practicalswift)
Pull request description:
Make `coins_tests/updatecoins_simulation_test` deterministic.
Before:
```
$ contrib/devtools/test_deterministic_coverage.sh 1000
[2019-06-15 05:36:20] Measuring coverage, run #1 of 1000
[2019-06-15 05:38:05] Measuring coverage, run #2 of 1000
[2019-06-15 05:39:49] Measuring coverage, run #3 of 1000
[2019-06-15 05:41:38] Measuring coverage, run #4 of 1000
[2019-06-15 05:43:16] Measuring coverage, run dashpay#5 of 1000
...
[2019-06-16 18:25:23] Measuring coverage, run dashpay#880 of 1000
[2019-06-16 18:27:12] Measuring coverage, run dashpay#881 of 1000
[2019-06-16 18:29:33] Measuring coverage, run dashpay#882 of 1000
[2019-06-16 18:33:00] Measuring coverage, run dashpay#883 of 1000
[2019-06-16 18:35:32] Measuring coverage, run dashpay#884 of 1000
The line coverage is non-deterministic between runs. Exiting.
The test suite must be deterministic in the sense that the set of lines executed at least
once must be identical between runs. This is a necessary condition for meaningful
coverage measuring.
--- gcovr.run-1.txt 2019-06-15 05:38:05.282359029 +0200
+++ gcovr.run-884.txt 2019-06-16 18:37:23.518298374 +0200
@@ -269,7 +269,7 @@
test/bloom_tests.cpp 320 320 100%
test/bswap_tests.cpp 13 13 100%
test/checkqueue_tests.cpp 223 222 99% 169
-test/coins_tests.cpp 478 472 98% 52,68,344-345,511,524
+test/coins_tests.cpp 478 474 99% 52,68,511,524
test/compilerbug_tests.cpp 18 18 100%
test/compress_tests.cpp 27 27 100%
test/crypto_tests.cpp 268 268 100%
@@ -401,5 +401,5 @@
zmq/zmqpublishnotifier.h 5 0 0% 12,31,37,43,49
zmq/zmqrpc.cpp 23 3 13% 16,18,20,23,33-35,37,40-47,51,62,64-65
------------------------------------------------------------------------------
-TOTAL 53323 28305 53%
+TOTAL 53323 28307 53%
------------------------------------------------------------------------------
```
After:
```
$ contrib/devtools/test_deterministic_coverage.sh 1000
[2019-06-15 05:36:20] Measuring coverage, run #1 of 1000
[2019-06-15 05:38:05] Measuring coverage, run #2 of 1000
[2019-06-15 05:39:49] Measuring coverage, run #3 of 1000
[2019-06-15 05:41:38] Measuring coverage, run #4 of 1000
[2019-06-15 05:43:16] Measuring coverage, run dashpay#5 of 1000
...
$
```
ACKs for commit f89958:
MarcoFalke:
ACK f899580 (checked that the randomness state of g_insecure_rand_ctx is the same after three test runs)
Tree-SHA512: 796d362b050c5750e351de1126b62f0f2c8e2d712cf01b6e1a3e2cc6ef92fa68439a32fc24c76d34bce4d553aee4ae4ea88a036c56eb9e25979649a19c59c3e5
gades pushed a commit to piratecash/pirate that referenced this pull request Dec 10, 2023
…est deterministic
f899580 tests: Make coins_tests/updatecoins_simulation_test deterministic (practicalswift)
Pull request description:
Make `coins_tests/updatecoins_simulation_test` deterministic.
Before:
```
$ contrib/devtools/test_deterministic_coverage.sh 1000
[2019-06-15 05:36:20] Measuring coverage, run cosanta#1 of 1000
[2019-06-15 05:38:05] Measuring coverage, run cosanta#2 of 1000
[2019-06-15 05:39:49] Measuring coverage, run cosanta#3 of 1000
[2019-06-15 05:41:38] Measuring coverage, run cosanta#4 of 1000
[2019-06-15 05:43:16] Measuring coverage, run dashpay#5 of 1000
...
[2019-06-16 18:25:23] Measuring coverage, run dashpay#880 of 1000
[2019-06-16 18:27:12] Measuring coverage, run dashpay#881 of 1000
[2019-06-16 18:29:33] Measuring coverage, run dashpay#882 of 1000
[2019-06-16 18:33:00] Measuring coverage, run dashpay#883 of 1000
[2019-06-16 18:35:32] Measuring coverage, run dashpay#884 of 1000
The line coverage is non-deterministic between runs. Exiting.
The test suite must be deterministic in the sense that the set of lines executed at least
once must be identical between runs. This is a necessary condition for meaningful
coverage measuring.
--- gcovr.run-1.txt 2019-06-15 05:38:05.282359029 +0200
+++ gcovr.run-884.txt 2019-06-16 18:37:23.518298374 +0200
@@ -269,7 +269,7 @@
test/bloom_tests.cpp 320 320 100%
test/bswap_tests.cpp 13 13 100%
test/checkqueue_tests.cpp 223 222 99% 169
-test/coins_tests.cpp 478 472 98% 52,68,344-345,511,524
+test/coins_tests.cpp 478 474 99% 52,68,511,524
test/compilerbug_tests.cpp 18 18 100%
test/compress_tests.cpp 27 27 100%
test/crypto_tests.cpp 268 268 100%
@@ -401,5 +401,5 @@
zmq/zmqpublishnotifier.h 5 0 0% 12,31,37,43,49
zmq/zmqrpc.cpp 23 3 13% 16,18,20,23,33-35,37,40-47,51,62,64-65
------------------------------------------------------------------------------
-TOTAL 53323 28305 53%
+TOTAL 53323 28307 53%
------------------------------------------------------------------------------
```
After:
```
$ contrib/devtools/test_deterministic_coverage.sh 1000
[2019-06-15 05:36:20] Measuring coverage, run cosanta#1 of 1000
[2019-06-15 05:38:05] Measuring coverage, run cosanta#2 of 1000
[2019-06-15 05:39:49] Measuring coverage, run cosanta#3 of 1000
[2019-06-15 05:41:38] Measuring coverage, run cosanta#4 of 1000
[2019-06-15 05:43:16] Measuring coverage, run dashpay#5 of 1000
...
$
```
ACKs for commit f89958:
MarcoFalke:
ACK f899580 (checked that the randomness state of g_insecure_rand_ctx is the same after three test runs)
Tree-SHA512: 796d362b050c5750e351de1126b62f0f2c8e2d712cf01b6e1a3e2cc6ef92fa68439a32fc24c76d34bce4d553aee4ae4ea88a036c56eb9e25979649a19c59c3e5
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@crowning-@UdjinM6@schinzelh