RE: [Possible Breakage] t1308 - Bad return value from test-tool

2019-02-09 Thread Randall S. Becker
On February 9, 2019 18:33, Jeff King wrote: > On Sat, Feb 09, 2019 at 01:08:01PM -0500, Randall S. Becker wrote: > > > > It sounds like you might need to set FREAD_READS_DIRECTORIES in your > > > config.mak. > > > > Setting FREAD_READS_DIRECTORIES = UnfortunatelyYes > > Silly question, but you di

Re: [Possible Breakage] t1308 - Bad return value from test-tool

2019-02-09 Thread Jeff King
On Sat, Feb 09, 2019 at 01:08:01PM -0500, Randall S. Becker wrote: > > It sounds like you might need to set FREAD_READS_DIRECTORIES in your > > config.mak. > > Setting FREAD_READS_DIRECTORIES = UnfortunatelyYes Silly question, but you did rebuild after setting that, not just re-run the tests, ri

RE: [Possible Breakage] t1308 - Bad return value from test-tool

2019-02-09 Thread Randall S. Becker
On February 8, 2019 23:24, Jeff King wrote: > On Fri, Feb 08, 2019 at 04:42:19PM -0500, Randall S. Becker wrote: > > > t1308 has me perplexed - this is an old breakage on the NonStop > > platform, that I have just gotten around to checking with the new bash > > version we have. When running sub-te

Re: [Possible Breakage] t1308 - Bad return value from test-tool

2019-02-08 Thread Jeff King
On Fri, Feb 08, 2019 at 04:42:19PM -0500, Randall S. Becker wrote: > t1308 has me perplexed - this is an old breakage on the NonStop platform, > that I have just gotten around to checking with the new bash version we > have. When running sub-test 23, the following was reported: > > Value not foun

[Possible Breakage] t1308 - Bad return value from test-tool

2019-02-08 Thread Randall S. Becker
t1308 has me perplexed - this is an old breakage on the NonStop platform, that I have just gotten around to checking with the new bash version we have. When running sub-test 23, the following was reported: Value not found for "foo.bar" test_expect_code: command exited with 1, we wanted 2 test-tool