"Fixed" the problem, put !apt-get -y install cuda-cudart-10-0
before it launches bootstrap.pl

[QUOTE=kracker;530998]"Fixed" the problem, put !apt-get -y install cuda-cudart-10-0 before it launches bootstrap.pl[/QUOTE]

Sweet! Thanks!!!

Just back from buying a new MB, CPU and RAM. Going offline to rebuild the machine now.

I'll be able to apply the change later today (hopefully)...

[QUOTE=kracker;530998]"Fixed" the problem, put !apt-get -y install cuda-cudart-10-0
before it launches bootstrap.pl[/QUOTE]

:fusion:

Any way to reset the uptime?
 

Sometimes my multiple Colab sessions get "out of sync" — that is, the uptime values are not the same.

Is there any way to stop and restart a notebook so the uptime restarts at zero? So far whenever I restart one, the uptime value resumes where it left off.

I could just let them all run out, but that would waste two sessions while the shortest one runs out (24 hours on the paid tier).

[QUOTE=Chuck;538600]Is there any way to stop and restart a notebook so the uptime restarts at zero? So far whenever I restart one, the uptime value resumes where it left off.[/QUOTE]

Under the Colab front end's "Runtime" menu, choose "Restart Runtime".

I /believe/ this gives you a freshly launched runtime, but I could be wrong. If that doesn't help, try the "Factory reset runtime" menu time.

Failing all of that not working, try "Manage Sessions" -> "Terminate" on the pop-up window, assuming that option isn't greyed out.

I'd test this myself, but I don't want to risk losing any of my current seven T4s... :wink:

BTW, thanks for beta testing the P-1'ing CPU side-job thingy. Looks like it's working nominally.

The Colab CPU
 

The Colab CPU doesn't work like I thought it would. I thought I would get a second executing cell with scrolling output like the GPU process. The CPU process seems to run secretly.

Could you give a simplified explanation as to how this works?

[QUOTE=Chuck;538602]Could you give a simplified explanation as to how this works?[/QUOTE]

Under the Notebook concept, only a single "Section" can run at a time. Thus, it would be impossible to have a second scrolling section of the output. This interface concept is more designed for education. We're doing this at the sufferance of (and thanks to) Google -- we work with what we've been given...

Thus, the GPU72_TF Notebook launches a subprocess that runs in the background, fetching, working, and reporting on the CPU "work units".

Now that I'm happy that the code is sane (including with the server interaction, and restarting), the next step is to make the progress lines from the CPU process available to the GPU process, to report in the same window output to the humans.

[QUOTE=chalsall;538601]Under the Colab front end's "Runtime" menu, choose "Restart Runtime".

I /believe/ this gives you a freshly launched runtime, but I could be wrong. If that doesn't help, try the "Factory reset runtime" menu time.

Failing all of that not working, try "Manage Sessions" -> "Terminate" on the pop-up window, assuming that option isn't greyed out.

I'd test this myself, but I don't want to risk losing any of my current seven T4s... :wink:

BTW, thanks for beta testing the P-1'ing CPU side-job thingy. Looks like it's working nominally.[/QUOTE]

Restart runtime started with the old uptime.
Factory reset runtime started over at zero.

Selftest loop
 

I can't say I've ever seen this before but somehow I'm stuck in a self test loop and can't get out of it. Any suggestions? I've done interrupt execution and then did run all and it just picked right back up with the test.

20200415_143255 ( 0:28): running a simple selftest... 20200415_143301 ( 0:28): Selftest statistics 20200415_143301 ( 0:28): number of tests 107 20200415_143301 ( 0:28): successfull tests 107 20200415_143301 ( 0:28): selftest PASSED! 20200415_143301 ( 0:28): Fetching initial work... 20200415_143302 ( 0:28): Running GPU type [B]Tesla P100-PCIE-16GB[/B]


Edit: If I stop execution I get...

Exiting...
20200415_143808 INFO: Comms spider starting... 20200415_143808 INFO: Gracefull shutdown... Use of uninitialized value $AID in concatenation (.) or string at ./comms.pl line 309. Done.

[QUOTE=mrk74;542765]I can't say I've ever seen this before but somehow I'm stuck in a self test loop and can't get out of it. Any suggestions?[/QUOTE]

Yeah... Swear in my general direction...

I made a mistake in a change to the assignment code-path just now, moving LG72D down to 99M for a while. If you just rerun your Notebook things should be sane again.

[QUOTE=chalsall;542766]Yeah... Swear in my general direction...[/QUOTE]


Nah I won't go THAT far. Did another "run all" and it's back to normal. :smile: