Author Topic: Benchmark Stub Test failures?  (Read 3982 times)

bischofftep

  • New to the forum
  • *
  • Posts: 17
Benchmark Stub Test failures?
« on: April 18, 2014, 05:56:35 PM »
Hello, all:

Got a development environment up and running under VirtualBox and everything compiles fine. Several things aren't working as they do under nightly builds, though, the most noticeable being that the Benchmark->Stub Test reveals a LOT of [FAIL] markers. For example:
Code: [Select]
[Pass] UNCACHEABLE(p) => 0x42000068
       _shoot_free(p)
       m11 = MALLOC_FREE_MEMORY => 0x411b8
       m12 = GetFreeMemForAllocateMemory() => 0x2c865c
[Pass] ABS(m01-m11) => 0x0
[Pass] ABS(m02-m12) => 0x0
[FAIL] ABS(m0-m2) => 0x1518
[FAIL] ABS((m0-m1) - 256*1024) => 0x14f0
[FAIL] ABS(m0-m2) => 0x14fc
[FAIL] ABS((m0-m1) - 256*1024) => 0x14f0
[FAIL] ABS(m0-m2) => 0x14fc

followed by a whole string of [FAIL] just like the ones shown.

My build pattern is:
/magic-lantern/make
/magic-lantern/platform/7D.203/make install

That's it... any ideas what might be causing this?
Douglas E. Bischoff
Audio/Video Production & Scoring

nanomad

  • Administrator
  • Hero Member
  • *****
  • Posts: 2918
  • All your websites are belong to us
Re: Benchmark Stub Test failures?
« Reply #1 on: April 19, 2014, 03:09:05 PM »
What compiler version are you using? (of gcc-arm-none-eabi)
EOS 1100D | EOS 650 (No, I didn't forget the D) | Ye Olde Canon EF Lenses ('87): 50 f/1.8 - 28 f/2.8 - 70-210 f/4 | EF-S 18-55 f/3.5-5.6 | Metz 36 AF-5

bischofftep

  • New to the forum
  • *
  • Posts: 17
Re: Benchmark Stub Test failures?
« Reply #2 on: April 22, 2014, 03:10:09 PM »
gcc-arm-none-eabi-4_8-2014q1
Douglas E. Bischoff
Audio/Video Production & Scoring

a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 12564
Re: Benchmark Stub Test failures?
« Reply #3 on: April 22, 2014, 03:24:55 PM »
Probably the threshold is a bit too tight (it's just an approximation to check if malloc/free seems to reserve the requested memory and give it back). If some other code is using the memory allocators in parallel with the tests, they may fail.

bischofftep

  • New to the forum
  • *
  • Posts: 17
Re: Benchmark Stub Test failures?
« Reply #4 on: April 22, 2014, 04:32:03 PM »
Probably the threshold is a bit too tight (it's just an approximation to check if malloc/free seems to reserve the requested memory and give it back). If some other code is using the memory allocators in parallel with the tests, they may fail.

Interesting... I went ahead and dropped back to the 2013_q4 toolchain just to be sure it wasn't something else going on, same problems.

Nightly builds do NOT have this problem, just my own builds. Frustrating, and makes me worry that my development environment isn't working after all.
Douglas E. Bischoff
Audio/Video Production & Scoring