On Sunday, 26 April 2020 at 22:05:20 UTC, aliak wrote:
On Saturday, 25 April 2020 at 19:00:55 UTC, Anonymouse wrote:
On Saturday, 25 April 2020 at 09:38:59 UTC, aliak wrote:
Then I run this dub dustmite command:
dub dustmite -b unittest ../dubdust --compiler-regex="never
matches"
have to pass the configuration `unittest` to
`dub dustmite` too.
Kind regards
André
Ah ok. Yes I was passing the unittest confit to dub dustmite.
In the logs above I can see you pass only the build type but not
the configuration (just to make you aware, there is a difference).
Kind regards
Andre
the -b or -c flag if that's what you
mean?
[...]
Yeah, that's a good tip. This output is because of a static
assert in the sumtype library.
Yes, that was my question. `dub test` will use configuration
`unittest`,
therefore you have to pass the configuration `unittest` to `dub
dustm
od tip. This output is because of a static
assert in the sumtype library.
Yes, that was my question. `dub test` will use configuration
`unittest`,
therefore you have to pass the configuration `unittest` to `dub
dustmite` too.
Kind regards
André
he sumtype library.
I also wonder whether dub Dustmite should be enhanced to search
for a plain text too. Because while using regex search there
might be characters which have a regex meaning while user just
want a simple text search. This could also cause issues.
Kind regards
Andre
On Saturday, 25 April 2020 at 19:00:55 UTC, Anonymouse wrote:
On Saturday, 25 April 2020 at 09:38:59 UTC, aliak wrote:
Then I run this dub dustmite command:
dub dustmite -b unittest ../dubdust --compiler-regex="never
matches"
I have had zero luck with dustmite via dub. I woul
On Saturday, 25 April 2020 at 09:38:59 UTC, aliak wrote:
Then I run this dub dustmite command:
dub dustmite -b unittest ../dubdust --compiler-regex="never
matches"
I have had zero luck with dustmite via dub. I would honestly
recommend that you create a shell script that does `dub
On Saturday, 25 April 2020 at 09:38:59 UTC, aliak wrote:
Trying to get dub dustmite to work, but I keep getting "initial
test fails"
This is the error from a vanilla dub test:
```
result ~wip: building configuration "result-test-unittest"...
inout(SumType!(int, FailureCo
Trying to get dub dustmite to work, but I keep getting "initial
test fails"
This is the error from a vanilla dub test:
```
result ~wip: building configuration "result-test-unittest"...
inout(SumType!(int, FailureContainer))
../../.dub/packages/sumtype-0.9.4/sumtype/
On Monday, 20 January 2020 at 15:04:32 UTC, Andre Pany wrote:
In general dub Dustmite works fine, I used it several times.
Maybe it has to do s.th. with your project structure. Please
create a dub issue with an example zip.
I've created a minimal nested project with a similar stru
owing test script:
cd example
dub 2>&1 | grep -F "ScrollView6__initZ+0xd8): undefined
reference to \`internal'"
However, when I attempt using 'dub dustmite' with
--linker-regex (or --linker-status, even), the initial test
always fails. I've also tried simpli
On Monday, 20 January 2020 at 07:14:24 UTC, FeepingCreature wrote:
dustmite example ../test.sh
Right, that's what I'm already doing now. However, the process is
extremely slow (takes 10+ hours for the current project, when
I've done this in the past) so I am hoping to speed things up a
bit b
owing test script:
cd example
dub 2>&1 | grep -F "ScrollView6__initZ+0xd8): undefined
reference to \`internal'"
However, when I attempt using 'dub dustmite' with
--linker-regex (or --linker-status, even), the initial test
always fails. I've also tried simpli
crollView6__initZ+0xd8): undefined reference
to \`internal'"
However, when I attempt using 'dub dustmite' with --linker-regex
(or --linker-status, even), the initial test always fails. I've
also tried simplifying the regex on the assumption that I'm not
esc
On Tuesday, 23 February 2016 at 11:09:00 UTC, denizzzka wrote:
Hi!
I have a code with segfault. I decided to try to take advantage
with dub dustmite:
$ dub dustmite ~/ssd/pgator_dustmite0 --program-status=139 --
--config=my_pgator.conf --debug=true
Shells process signal exit codes in a
Hi!
I have a code with segfault. I decided to try to take advantage
with dub dustmite:
$ dub dustmite ~/ssd/pgator_dustmite0 --program-status=139 --
--config=my_pgator.conf --debug=true
WARNING: A deprecated branch based version specification is used
for the dependency vibe-d-postgresql
No luck, unfortunately.
On Friday, 12 December 2014 at 04:25:01 UTC, Vlad Levenfeld wrote:
I'm trying to reduce a bug with dub dustmite feature and I must
be doing it wrong somehow, my regular dub output looks like
this:
source/experimental.d(2403): Error: struct
experimental.Product!(int[], int[]).Produ
On 2014-12-12 05:25, Vlad Levenfeld wrote:
I get
Executing dustmite...
None => No
object.Exception@dustmite.d(243): Initial test fails
It seems like a pretty simple case, I'm not sure what's going on.
I get the same error as well every time I use dustmite. At lease via Dub.
--
/Jac
I'm trying to reduce a bug with dub dustmite feature and I must
be doing it wrong somehow, my regular dub output looks like this:
source/experimental.d(2403): Error: struct
experimental.Product!(int[], int[]).Product no size yet for
forward reference
ulong[2]
source/experimental.d
20 matches
Mail list logo
