Hi Bruno,
On 3/31/24 4:11 PM, Bruno Haible wrote:
> Cool! Now, it makes sense to
> - look at the two remaining failures in info-tests,
Yes, I was going to start looking at those now. If I remember
correctly they should be simple to fix.
> - try more packages from the users.txt list. Is Bison
Hi Collin,
> Thanks for fixing those. Now all of the create-tests/* and
> import-tests/* are working for me.
Cool! Now, it makes sense to
- look at the two remaining failures in info-tests,
- try more packages from the users.txt list. Is Bison passing meanwhile?
Bruno
Hi Bruno,
Thanks for fixing those. Now all of the create-tests/* and
import-tests/* are working for me.
On 3/31/24 2:52 PM, Bruno Haible wrote:
>> The [gperf] 3.2 release commit didn't have a git tag and isn't on GNU's ftp
>> server. Not sure if you forgot or if this was intended, so I figured
>>
Hi Collin,
> Here is what I see for the import tests at the moment:
>
> ./test-oath-toolkit-1.out tmp384427-out differ: byte 561, line 24
> --- ./test-oath-toolkit-1.out 2024-03-30 14:11:44.586946254 -0700
> +++ tmp384427-out 2024-03-30 17:14:43.330203522 -0700
> @@ -21,6 +21,7 @@
>top/GN
Hi Bruno,
On 3/30/24 4:22 PM, Bruno Haible wrote:
> Once the test suite entirely passes, will be the time to revisit this
> 'cleaner'
> function. Your approach with the regex can be part of the solution.
Yes, that sounds like a good idea. It should be easier to validate
changes that way. The tes
