search

MichaelChirico / r-bugs

A ⚠️read-only⚠️mirror of https://bugs.r-project.org/
20 stars 0 forks source link

[BUGZILLA #17836] New (with respect to 3.6.x) test failure in reg-tests-2 #7010

Open github-actions[bot] opened 4 years ago

github-actions[bot] commented 4 years ago

Hi, I noticed that we have a new failing test in v4.0.2 on Gentoo compared to what fails in v3.6.3. After the test crashes, at the end of reg-tests-2.Rout.fail I see

## summaryRprof() bug PR#15886 :
Rprof(tf <- tempfile("Rprof.out"), memory.profiling=TRUE,
line.profiling=FALSE)

Error in Rprof(tf <- tempfile("Rprof.out"), memory.profiling = TRUE, line.profiling = FALSE) : R profiling is not available on this system Execution halted

and presumably that's the cause of the failure? If not, this is reproducible on my machine and more information is available.

METADATA

github-actions[bot] commented 4 years ago

That test does pass if I enable profiling in the build. Maybe just skip it if profiling isn't there?

METADATA

github-actions[bot] commented 4 years ago

(In reply to Michael Orlitzky from comment #1)

That test does pass if I enable profiling in the build.

How?

Maybe just skip it if profiling isn't there?

Be careful, there are (at least) two kinds of memory profiling in (base) R. The one that one typically enables as a compile option which is also what

capabilities()["profmem"]

profmem 
  FALSE

gives, is NOT the one used by Rprof() as you can get from reading the help page ?Rprof

So, this is really strange. Note that I only rarely use an R versions with "profiling enabled", but the Rprof check that you report failing has been working for me all the times.

METADATA

github-actions[bot] commented 4 years ago

In Gentoo, both types of profiling are enabled by the same flag, so they're either both on or both off. If that's dumb... well, that's how I found it.

So more specifically, my report is:

METADATA

github-actions[bot] commented 4 years ago

(In reply to Michael Orlitzky from comment #3)

In Gentoo, both types of profiling are enabled by the same flag, so they're
either both on or both off. If that's dumb... well, that's how I found it.

Good, thank you for digging. Yes, that (Gentoo's default) is "dumb" indeed, as the default from the R sources correspond to

--enable-R-profiling --disable-memory-profiling

which is clearly "visible" from ../R/configure --help

Indeed, this test should ideally be script when Rprof()iling is disabled. ==> I'm about to add a new capabilities() entry for this to R-devel, which I then will use for this test.

METADATA